tech-invite   World Map
3GPP     Specs     Glossaries     UICC       IETF     RFCs     Groups     SIP     ABNFs       T+       Search     Home

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

 

|  AAA Proxy  |  AAA Server  |  ABMF  |  ACC IF  |  AF  |  AFE  |  AMF  |  ANDSF  |  AS  |  ATCF  |  ATGW  |  AuC  |  AUSF  |

 

Up       Top

See it   here

specified from  Rel-6  (for I‑WLAN)  in
TS 23.234, clause 6.2.2 

re-used from  Rel-8  as defined  in
TS 23.002, clause 4.1.4.7 

The 3GPP AAA Proxy provides support for roaming non-3GPP Access users in the VPLMN necessary the Authentication, Authorisation and location management services in order to get access to EPS.


Up       Top

See it   here

specified from  Rel-6  (for I‑WLAN)  in
TS 23.234, clause 6.2.3 

re-used from  Rel-8  as defined  in
TS 23.002, clause 4.1.4.6 

The 3GPP AAA Server is located at the HPLMN and provides support for non-3GPP Access users with services like Authentication, Authorisation and location management services in order to get access to EPS. It also contains necessary user related information in order to grant access to non‑3GPP access. It also coordinates the information needed to support mobility between 3GPP and non-3GPP accesses such as coordination of PDN GW information. It interacts with HSS to maintain consistent information for users supporting mobility and service continuity between 3GPP and non‑3GPP access. For details, see TS 23.402.

See Subscriber Data in the AAA Server   here.


Up       Top

See it   here

specified from  Rel-6  in
TS 32.240, clause 4.3.2.2.4 

The ABMF is the location of the subscriber's account balance within the OCS. The ABMF is put into functional context within TS 32.296.


Up       Top

specified from  Rel-12  in
TS 23.203, clause S.8.7 

The Accounting Interworking Function that performs translation of the accounting signalling and parameters that are understood by the IP-Edge into the credit management signalling and parameters that are understood by the OCS and the OFCS is defined in BBF WT-300.


Up       Top

See it   here

specified from  Rel-7  in
TS 23.203, clause 6.2.3 

The AF is an element offering applications that require dynamic policy and/or charging control over the IP-CAN user plane behaviour. The AF shall communicate with the PCRF to transfer dynamic session information, required for PCRF decisions as well as to receive IP-CAN specific information and notifications about IP-CAN bearer level events. One example of an AF is the P-CSCF of the IM CN subsystem.


Up       Top

defined from  Rel-9
Source:   TS 23.002, clause 4a.26 

When the User Data Convergence (UDC) architecture is applied, certain functional entities keep the application logic, but do not locally store user data permanently. Examples of such functional entities are HLR/HSS/AuC and Application Servers. These data-less functional entities are known in the UDC architecture as Application Front Ends. The application that is handled by an AFE determines the type of AFE, e.g. HLR-FE or HSS-FE.

The reference points between the Front Ends and the core and service layers are not affected by the UDC architecture. More information on Application Front Ends can be found in TS 23.335.


Up       Top

See it   here

specified from  Rel-15  in
draft-TS 23.501, clause 6.2.1 

This network function exposes the Namf service.


Up       Top

See it   here

specified from  Rel-8  in
TS 23.402
as defined  in
TS 23.002, clause 4.1.4.8 

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


Up       Top

See it   here

defined from  Rel-5
Source:   TS 23.002, clause 4a.7.7 

An AS i.e., SIP Application Server, OSA Application Server, or CAMEL IM-SSF, offers value added IM services and resides either in the user's home network or in a third party location. The third party could be a network or simply a stand-alone AS.

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.

See Subscriber Data in the IMS AS   here.


Up       Top

See it   here

specified from  Rel-10  in
TS 23.237, clause 5.3.4 

The Access Transfer Control Function (ATCF) is a function in the serving (visited if roaming) network. When (v)SRVCC enhanced with ATCF is used, the ATCF is included in the session control plane for the duration of the call before and after Access Transfer. The ATCF may be co-located with one of the existing functional entities within the serving network (i.e. P-CSCF or IBCF).


Up       Top

See it   here

specified from  Rel-10  in
TS 23.237, clause 5.3.5 

The Access Transfer Gateway (ATGW) is controlled by the ATCF and, if SRVCC enhanced with ATCF is used, stays in the session media path for the duration of the call and after Access Transfer, based on the local policy of the serving network. It supports transcoding after SRVCC handover in case the media that was used prior to the handover is not supported by the MSC server. Depending on placement of the ATCF, different physical nodes may be considered for the ATGW, i.e. IMS-AGW or TrGW.


Up       Top

defined from  GSM Rel-96
Source:   TS 23.002, clause 4.1.1.1.2 

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 IMSI and the network;
    • 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, stores them and delivers them to the VLR and SGSN and MME which need them to perform the security functions for a mobile station.


Up       Top

See it   here

specified from  Rel-15  in
draft-TS 23.501, clause 6.2.8 

This network function exposes the Nausf service.



Up       Top