Tech-invite   World Map
3GPPspecs     Glossaries     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

 

|  SAS  |  SCC AS  |  SCEF  |  S‑CSCF  |  SEG  |  SEPP  |  SGSN  |  S4‑SGSN  |  SGW  |  S‑GW  |  SIM  |  SIWFC  |  SIWFS  |  SLF  |  SMF  |  SMLC  |  SMSF  |  SMS‑GMSC  |  SMS‑IWMSC  |  SMS‑SC  |  SPR  |

 

Up       Top

See it   here

specified from  Rel-5  in
TS 25.305, clause 5.2.5 

The SAS communicates with the RNC over the Iupc interface enabling it to forward UE Positioning assistance data to UEs and to receive UE Positioning measurement data from the RNC.


Up       Top

See it   here

specified from  Rel-8  in
TS 23.292, clause 5.3.1 

The SCC AS is a home network based IMS Application that provides functionality required to enable IMS Centralized Services. The SCC AS is inserted in the session path using originating and terminating iFCs; it is configured as the first AS in the originating iFC and as the last AS in the terminating iFC chain. The SCC AS may also be invoked through the use of PSI termination procedures when using CS access.


Up       Top

See it   here

specified from  Rel-13  in
TS 23.682, clause 4.4.8 

The Service Capability Exposure Function (SCEF) provides a means to securely expose the services and capabilities provided by 3GPP network interfaces. The SCEF provides a means for the discovery of the exposed service capabilities. The SCEF provides access to network capabilities through homogenous network application programming interfaces (e.g. Network API) defined by OMA, GSMA, and possibly other standardisation bodies. The SCEF abstracts the services from the underlying 3GPP network interfaces and protocols.


Up       Top

See it   here

specified from  Rel-5  in
TS 23.228, clause 4.6.3 

The Serving-CSCF (S-CSCF) performs the session control services for the UE. It maintains a session state as needed by the network operator for support of the services. Within an operator's network, different S-CSCFs may have different functionalities.

See Subscriber Data in the S-CSCF   here.


Up       Top

See it   here

specified from  Rel-5  in
TS 33.210, clause 4.5 

The interface between different security domains is protected by 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.


Up       Top

specified from  Rel-15  in
TS 23.501, clause 6.2.17 

The SEPP is a non-transparent proxy and supports message filtering and policing on inter-PLMN control plane interfaces, as well as topology hiding.


Up       Top

See it   here

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

The SGSN is the node that is serving the MS. The SGSN supports GPRS for A/Gb mode and/or Iu-mode. At PS attach, the SGSN establishes a mobility management context containing information pertaining to e.g. mobility and security for the MS. At PDP Context Activation, the SGSN establishes a PDP context, to be used for routeing purposes, with the GGSN that the subscriber will be using.

In Gn/Gp mode and when the SGSN and the GGSN are in different PLMNs, they are interconnected via the Gp interface. The SGSN may send location information to the MSC/VLR and the SGSN may receive paging requests from the MSC/VLR via the Gs interface.

See Subscriber Data in the SGSN   here.


Up       Top

See it   here

specified from  Rel-8  in
TS 25.401, clause 4.4.4 

The S4-SGSN is the evolution of the Gn/Gp SGSN for EPS and includes signalling for mobility between 2G/3G and E‑UTRAN 3GPP access networks.

See Subscriber Data in the S4‑SGSN   here.


Up       Top

specified from  Rel-4  in
TS 23.002, clause 4a.8
TS 29.163, clause 6.1.2.1 

The SGW performs the signalling conversion (both ways) at transport level between the SS7 based transport of signalling used in pre-Rel-4 networks, and the IP based transport of signalling possibly used in post-R3 networks (i.e. between Sigtran SCTP/IP and SS7 MTP). The SGW does not interpret the application layer (e.g. MAP, CAP, BICC, ISUP) messages but may have to interpret the underlying SCCP or SCTP layer to ensure proper routing of the signalling.

For the interworking between IMS and CS Networks, this component performs the call related signalling conversion to or from BICC/ISUP based MTP transport networks to BICC/ISUP based SCTP/IP transport networks, and forwards the converted signalling to or from the MGCF.


Up       Top

See it   here

specified from  Rel-8  in
TS 23.401, clause 4.4.3.2 

The Serving GW is the gateway which terminates the interface towards E-UTRAN. The functions of the Serving GW include:
  • inter-eNodeB handover (except when user data is transported using the Control Plane CIoT EPS Optimisation);
  • inter-3GPP mobility (terminating S4 and relaying the traffic between 2G/3G system and PDN GW);
  • Packet routeing and forwarding;
  • Transport level packet marking in the uplink and the downlink, e.g. setting the DiffServ Code Point, based on the QCI, and optionally the ARP priority level, of the associated EPS bearer;
  • ...
See Subscriber Data in the S-GW   here.


Up       Top

defined from  GSM Rel-96
Source:   TS 42.017, Rel-4 

A GSM MS comprises an ME and a SIM. The SIM is a removable module. The SIM contains the International Mobile Subscriber Identity (IMSI) which unambiguously identifies a subscriber. Without a valid IMSI, GSM service is not accessible (except emergency calls, as defined in TS 02.03). The user interface (MMI) of the ME related to SIM operations is defined in TS 02.30. TS 02.09 specifies a security function for authenticating the SIM. This function, which is mandatory for any MS, is based on a cryptographic algorithm, A3, and a secret subscriber authentication key, Ki, both of which are located in the SIM. The SIM provides storage of subscriber related information. This data is of three types:
  • data fixed during administrative phase; e.g. IMSI, subscriber authentication key, access control class;
  • temporary network data; e.g. TMSI, LAI, Kc, Forbidden PLMNs;
  • service related data; e.g. Language Preference, Advice of Charge.
The SIM contains Card Holder Verification information (CHV1 - see clause 5) to provide protection against unauthorized use. For some optional features, the use of a second CHV (CHV2) is required. CHV(s) shall be stored and verified within the SIM.

The SIM may also contain applications which use the features defined in the SIM Application Toolkit specification TS 11.14.


Up       Top

defined from  GSM Rel-96
Source:   TS 03.54 

The visited MSC is responsible for allocation of an IWF or a SIWFS. In the case the visited MSC has the additional functions required to provide a SIWF, this additional functionality in the visited MSC is called SIWFC. SIWFC is a logical part of the MSC.


Up       Top

defined from  GSM Rel-96
Source:   TS 03.54 

The logical entity that contains the IWU is called SIWF Server (SIWFS). It offers IWU to remotely located MSCs. The IWU provides the traffic channel related functions. SIWFS contains also the DRM which is needed for the additional signalling between entities involved i.e. the visited MSC and the SIWFS.


Up       Top

defined from  Rel-5
Source:   TS 23.002, clause 4.1.1.7 

The SLF:
  • 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.
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.


Up       Top

See it   here

specified from  Rel-15  in
TS 23.501, clause 6.2.2 

This network function exposes the Nsmf service.


Up       Top

specified from  Rel-15  in
TS 23.501, clause 6.2.13 

This network function exposes the Nsmsf service.


Up       Top

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

The SMLC node is responsible for managing the overall co-ordination and scheduling of resources required to perform positioning of a mobile, and calculating the final location estimate and accuracy. There may be more than one SMLC in a PLMN.


Up       Top

See it   here

specified from  GSM Phase 2  in
TS 09.02, clause 4.1.6 

The SMS GMSC is the interface between the Mobile Network and the network which provides access to the Short Message Service Centre, for short messages to be delivered to MSs.


Up       Top

See it   here

specified from  GSM Phase 2  in
TS 09.02, clause 4.1.7 

The SMS IWMSC is the interface between the Mobile Network and the network which provides access to the Short Message Service Centre, for short messages submitted by MSs.


Up       Top

See it   here

defined from  GSM Phase 1  in
TS 03.40, clause 6 

Function responsible for the relaying and store-and-forwarding of a short message between an SME (Short Message Entity) and an MS.


Up       Top

See it   here

specified from  Rel-7  in
TS 23.203, clause 6.2.4 

The SPR logical entity contains all subscriber/subscription related information needed for subscription-based policies and IP-CAN bearer level PCC rules by the PCRF. The SPR may be combined with or distributed across other databases in the operator's network.



Up       Top