tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Glossaries     Architecture     IMS     UICC    |    search     info

3GPP Glossaries

|   Features_Services   |   Network_Entities   |   Reference_Points   |   SIM_UICC_Dir_Files   |   Identifiers   |

 

Network entities

D

F

J

K

X

Y

Z

 

 

 

Here          Top

|   EATF   |   E‑CSCF   |   EIR   |   eNB   |   ePDG   |   E‑SMLC   |   E‑UTRAN   |

 

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

The EATF provides IMS-based mechanisms for enabling service continuity of IMS emergency sessions. It is a function in the serving (visited if roaming) IMS network, providing the procedures for IMS emergency session anchoring and PS to CS access transfer as defined in TS 23.237.

Up       Top

defined from  Rel-7
Source:   TS 23.167, clause 6.2.2 

The functionality of the E-CSCF includes the following:
  • Receive an emergency session establishment request from a P-CSCF or an S-CSCF.
  • If the UE does not have credentials, a non-dialable callback number shall be derived where required by local regulation.
  • If location information is not included in the emergency request or additional location information is required, the E-CSCF may request the LRF to retrieve location information.
  • If required, the E-CSCF requests the LRF to validate the location information if included by the UE.
  • Determines or queries the LRF for the proper routing information/PSAP destination.
  • Route emergency session establishment requests to an appropriate destination including anonymous session establishment requests.
  • Subject to local regulation, the E-CSCF may send the contents of the P-asserted ID or UE identification to the LRF.
  • Based on operator policy, the E-CSCF may route the emergency IMS call to ECS for further call process.
  • For supporting SRVCC, the E CSCF forwards the session establishment request to the EATF in the serving IMS network for anchoring.
  • Generation of CDRs.

Up       Top

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

The Equipment Identity Register (EIR) in the GSM system is the logical entity which is responsible for storing in the network the International Mobile Equipment Identities (IMEIs), used in the GERAN/UTRAN/E-UTRAN system.

The equipment is classified as "white listed", "grey listed", "black listed" or it may be unknown as specified in TS 22.016 and TS 29.002.

Up       Top

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

An eNB is a logical network component which serves one or more E-UTRAN cells.

Up       Top

defined from  Rel-8
Source:   TS 23.402, clause 4.3.4 

The functionality of ePDG includes the following:
  • Functionality defined for the PDG in TS 23.234 for the allocation of a remote IP address as an IP address local to the ePDG which is used as CoA when S2c is used;
  • Functionality for transportation of a remote IP address as an IP address specific to a PDN when S2b is used;
  • Routing of packets from/to PDN GW (and from/to Serving GW if it is used as local anchor in VPLMN) to/from UE; if GTP based S2b is used, this includes routing of uplink packets based on the uplink packet filters in the TFTs assigned to the S2b bearers of the PDN connection;
  • Routing of downlink packets towards the SWu instance associated to the PDN connection;
  • De-capsulation/Encapsulation of packets for IPSec and, if network based mobility (S2b) is used, for GTP or PMIPv6 tunnels;
  • Mobile Access Gateway (MAG) according to the PMIPv6 specification, RFC 5213, if PMIP based S2b is used;
  • Tunnel authentication and authorization (termination of IKEv2 signalling and relay via AAA messages);
  • Local mobility anchor within untrusted non-3GPP access networks using MOBIKE (if needed);
  • Transport level packet marking in the uplink;
  • Enforcement of QoS policies based on information received via AAA infrastructure;
  • Lawful Interception.
  • Allocation of downlink GRE key for each PDN connection within the ePDG, which is used to encapsulate downlink traffic to the ePDG on the PMIPv6-based S2b interface.
  • Accounting for inter-operator charging according to charging principles specified in TS 32.240.
  • Interfacing OFCS through reference points TS 32.251 for EPC nodes.

Up       Top

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

For E-UTRAN, the Evolved Serving Mobile Location Centre (E-SMLC) is a server in the core network.

The E-SMLC manages the support of different location services for target UEs, including positioning of UEs and delivery of assistance data to UEs. The E-SMLC may interact with the serving eNodeB for a target UE in order to obtain position measurements for the UE, including uplink measurements made by the eNodeB and downlink measurements made by the UE that were provided to the eNodeB as part of other functions such as for support of handover.

Up       Top

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

The E-UTRAN consists of eNBs, providing the E-UTRA user plane (PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations towards the UE. The eNBs can be interconnected with each other by means of the X2 interface. The eNBs are connected by means of the S1 interface to the EPC (Evolved Packet Core), more specifically to the MME (Mobility Management Entity) by means of the S1-MME and to the Serving Gateway (S-GW) by means of the S1-U interface. The S1 interface supports a many-to-many relation between MMEs / Serving Gateways and eNBs.

The split of functions between eNB and EPC is described in the specifications TS 23.401, TS 36.300 and TS 36.401.

Up       Top