tech-invite   World Map
3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       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

 

|  PCEF  |  PCF  |  PCRF  |  P‑CSCF  |  PDF  |  PDG  |  PFDF  |  PDN‑GW  |  PLMN  |  PMD  |  PNA  |  PPR  |  Presence List Server  |  Presence Watcher  |  Presentity Presence Proxy  |  ProSe Application Server  |  ProSe Function  |  ProSe‑enabled UE  |  PS  |  PS Domain  |  PUA  |

 

Up       Top

see it   here

specified from  Rel-7  in
TS 23.203, clause 6.2.2 

The PCEF encompasses service data flow detection, policy enforcement and flow based charging functionalities. This functional entity is located at the Gateway (e.g. GGSN in the GPRS case, and PDG in the WLAN case). It provides service data flow detection, user plane traffic handling, triggering control plane session management (where the IP-CAN permits), QoS handling, and service data flow measurement as well as online and offline charging interactions.


Up       Top

see it   here

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

This network function exposes the Npcf service.


Up       Top

see it   here

specified from  Rel-7  in
TS 23.203, clause 6.2.1 

The PCRF encompasses policy control decision and flow based charging control functionalities. It provides network control regarding the service data flow detection, gating, QoS and flow based charging (except credit management) towards the PCEF and/or TDF. It provides network control regarding the application detection, gating, QoS and application based charging (except credit management) towards the TDF and the PCEF enhanced with ADC. It applies the security procedures, as required by the operator, before accepting service information from the AF.


Up       Top

defined from  Rel-5
Source:   TS 23.228, clause 4.6.1 

The P-CSCF is the first contact point within the IM Core Network subsystem. Its address is discovered by UEs using procedures based on DNS/DHCP. As defined in RFC 3261, the P-CSCF behaves like a Proxy, i.e. it accepts requests and services them internally or forwards them on.


Up       Top

defined for  Rel-6
Source:   TS 23.009, Rel-6 

The PDF acts as a Policy Decision Point for service based local policy control. The PDF makes the policy decisions based on the session and media related information obtained from the AF via the Gq interface. The PDF shall exchange the decision information with the GGSN via the Go interface.


Up       Top

defined from  Rel-6
Source:   TS 23.002, clause 4a.13.5 

The PDG provides access to PS based services for a WLAN UE. It resides either in the home (for access to home services) or in the visited 3GPP network (for access to local services).


Up       Top

see it   here

specified from  Rel-14  in
TS 23.203, clause 6.2.13
TS 29.251 

The PFDF (Packet Flow Description Function) is a functional element which stores PFDs associated with application identifier (s) and transfers them to the PCEF via Gw interface to enable the PCEF to perform accurate application detection when the PFDs are managed by a 3rd party service provider.


Up       Top

defined from  Rel-8
Source:   TS 23.002, clause 4.1.4.2.2 

The PDN GW is the gateway which terminates the SGi interface towards the PDN.

If a UE is accessing multiple PDNs, there may be more than one PDN GW for that UE, however a mix of S5/S8 connectivity and Gn/Gp connectivity is not supported for that UE simultaneously.

The PDN GW provides PDN connectivity to both GERAN/UTRAN only UEs and E-UTRAN capable UEs using any of E-UTRAN, GERAN or UTRAN. The PDN GW provides PDN connectivity to E-UTRAN capable UEs using E-UTRAN only over the S5/S8 interface. The PDN GW may also provide PDN connectivity to UEs using non-3GPP access networks with the procedures defined in TS 23.402.

For detailed PDN GW functions, see TS 23.401 and TS 23.402.


Up       Top

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

A PLMN is established and operated by an administration or Recognized Private Operating Agency (RPOA) for the specific purpose of providing land mobile telecommunications services to the public.

A PLMN may be regarded as an extension of networks (e.g. ISDN, corporate and public PDNs, etc.); it is a collection of MSCs areas in CS domain and SGSN areas for GPRS and SGSN or MME areas for EPC in PS domain within a common numbering plan (e.g. same National Destination Code) and a common routing plan. The MSCs are the functional interfaces between the fixed networks and a PLMN for call set-up in CS domain. The GGSN and the SGSN are the functional interfaces between the fixed networks and a PLMN for packet transmission in GPRS PS domain. In case of EPC PS Domain, the PDN GW, Serving-GW and the SGSN and the MME are the functional interfaces between the fixed networks and a PLMN for packet transmission.

Functionally the PLMNs may be regarded as independent telecommunications entities even though different PLMNs may be interconnected through the ISDN/PSTN and PDNs for forwarding of calls or network information. A similar type of interconnection may exist for the interaction between the MSCs/SGSNs/MMEs of one PLMN.

The PLMN infrastructure is logically divided into a Core Network (CN) and an Access Network (AN) infrastructures.


Up       Top

see it   here

specified from  Rel-6  in
TS 23.271, clause 6.3.12 

The pseudonym mediation device (PMD) functionality maps or decrypts the pseudonym into the corresponding verinym (i.e. IMSI or MSISDN). PMD functionality may be a standalone network entity or the PMD functionality may be integrated in PPR, GMLC or other network entity. If PMD functionality is not part of GMLC it may be accessed using the Lid interface.


Up       Top

defined from  Rel-6
Source:   TS 24.141, clause 5.3.5 

The PNA collects presence information about the presentity from a number of core network entities. The PNA can combine information from various core network entities to form more complete presence information.


Up       Top

see it   here

specified from  Rel-6  in
TS 23.271, clause 6.3.11 

Privacy check may be done in the privacy profile register. The HLR or HSS contains the address to the PPR. The PPR is accessible from the H-GMLC via the Lpp interface. PPR may be a standalone network entity or the PPR functionality may be integrated in H-GMLC.


Up       Top

defined from  Rel-6
Source:   TS 23.141, clause 5.5 

The Presence List Server stores grouped lists of watched presentities and enables a Watcher Application to subscribe to the presence of multiple presentities using a single SUBSCRIBE transaction. Presence List Server also stores and enables the management of filters associated to presentities in the presence list. Presence list server shall attach associated filter to each individual SUBSCRIBE transaction. The Presence List Server is implemented as a SIP Application Server function as defined in TS 23.228. For the case where the Watcher Application resides in an IMS UE, the Presence List Server may support the Ut reference point to allow the user to manage his presence lists.


Up       Top

defined from  Rel-6
Source:   TS 23.141, clause 5.4 



Up       Top

defined from  Rel-6
Source:   TS 23.141, clause 5.3.3 

In order to support a presence service, in particular across PLMN borders, generic network functions are needed, e.g. routing and security. The presence proxies provide these functions. Presence proxies constitute the entry and exit point for presence requests between PLMNs.

The Presentity Presence Proxy shall provide the following functionality:
  • Determination of the identity of the presence server associated with a particular presentity;
  • Authentication of Watcher Presence Proxy;
  • Authentication of the Presence user Agent;
  • Generation of accounting information for updates to presence information.


Up       Top

see it   here

specified from  Rel-12  in
TS 23.303, clause 4.4.4 

The ProSe Application Server supports the following capability:
  • Storage of EPC ProSe User IDs and ProSe Function IDs;
  • Mapping of Application Layer User IDs and EPC ProSe User IDs.


Up       Top

see it   here

specified from  Rel-12  in
TS 23.303, clause 4.4.1 

The ProSe Function is the logical function that is used for network related actions required for ProSe. The ProSe Function plays different roles for each of the features of ProSe. In this version of the specification it is assumed that there is only one logical ProSe Function in each PLMN that supports Proximity Services.


Up       Top

see it   here

specified from  Rel-12  in
TS 23.303, clause 4.4.2 

Any ProSe-enabled UE may support the following functions:
  • Exchange of ProSe control information between ProSe-enabled UE and the ProSe Function over PC3 reference point.
  • Procedures for open ProSe Direct Discovery of other ProSe-enabled UEs over PC5 reference point.


Up       Top

defined from  Rel-6
Source:   TS 24.141, clause 5.3.3 

A PS is an entity that accepts, stores, and distributes presence information.


Up       Top

defined from  GSM Rel-98
Source:   TS 23.002, clause 3.3.2 

The PS domain refers to the set of all the CN entities offering "PS type of connection" for user traffic as well as all the entities supporting the related signalling. A "PS type of connection" transports the user information using autonomous concatenation of bits called packets: each packet can be routed independently from the previous one.


Up       Top

defined from  Rel-6
Source:   TS 24.141, clause 5.3.1 

A PUA is an entity that provides presence information to a Presence Server.



Up       Top