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

|   MBMS‑GW   |   MCE   |   MGCF   |   MME   |   MMS Relay/Server   |   MRB   |   MRFC   |   MRFP   |   MS   |   MSC   |   MSCF   |   MSC‑S   |   MSC‑VLR   |   MTC‑AAA   |   MTC‑IWF   |

 

defined from  Rel-10
Source:   TS 23.002, clause 4a.14.3 

The MBMS-GW provides functions in the EPS for controlling MBMS session initiation / modification / termination by the MBMS User Service and for providing delivery of IP Multicast datagrams from the SGi-mb reference point to downstream nodes in the MBMS Service Area with a specified quality of service.

Up       Top

defined from  Rel-10
Source:   TS 23.002, clause 4a.14.4 

The MCE is a functional entity providing functions for admission control and allocation of radio resources by E-UTRAN and for MBMS session control.

Up       Top

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

The MGCF:
  • Controls the parts of the call state that pertain to connection control for media channels in an IMS-MGW.
  • Communicates with CSCF, BGCF, and circuit switched network entities.
  • Determines the next hop depending on the routing number for incoming calls from legacy networks.
  • Performs protocol conversion between ISUP/TCAP/SIP-I and the IM subsystem call control protocols.
  • Out of band information received in MGCF may be forwarded to CSCF/IMS-MGW.

Up       Top

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

MME is the control plane entity within EPS supporting Mobility Management functions as listed below. For detailed functional role of MME, see specifications TS 23.401, TS 23.402 and TS 36.300.
  • NAS signalling and security;
  • Inter CN node signalling for mobility between 3GPP access networks;
  • Tracking Area list management;
  • PDN GW and Serving GW selection;
  • SGSN selection for handovers to 2G or 3G 3GPP access networks;
  • Roaming;
  • Authentication;
  • Bearer management functions including dedicated bearer establishment.
  • Lawful Interception of signalling traffic.
The procedures for information transfer between the SGSN, the MME and the HSS are defined in TS 23.401 and TS 23.060.

Up       Top

defined from  Rel-6
Source:   TS 23.140, clause 5.2 

The MMS Relay/Server is responsible for storage and notification, reports, and general handling of messages. The MMS Relay/Server may also provide convergence functionality between External Servers and MMS User Agents and thus enable the integration of different server types across different networks.

Up       Top

defined from  Rel-8
Source:   TS 23.002, clause 4a.7.4b 

The MRB supports the sharing of a pool of heterogeneous MRF resources by multiple heterogeneous applications. MRB assigns (and later releases) specific suitable MRF resources to calls as requested by the consuming applications, based on MRF attributes specified by the applications as well as other criteria.

The MRB may take the following kinds of information into account when assigning MRF resources to an application:
  • the specific characteristics of the media resources required for the call or calls;
  • the identity of the application;
  • rules for allocating MRF resources across different applications;
  • per-application or per-subscriber SLA or QoS criteria; and
  • capacity models of particular MRF resources.

Up       Top

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

The MRFC:
  • Controls the media stream resources in the MRFP.
  • Interprets information coming from an AS and S-CSCF (e.g. session identifier) and control MRFP accordingly.
  • Generates CDRs.

Up       Top

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

The MRFP:
  • Controls bearers on the Mb reference point.
  • Provides resources to be controlled by the MRFC.
  • Mixes incoming media streams (e.g. for multiple parties).
  • Sources media streams (for multimedia announcements).
  • Processes media streams (e.g. audio transcoding, media analysis).
  • Floor Control (i.e. manage access rights to shared resources in a conferencing environment).

Up       Top

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

The MS consists of the physical equipment used by a PLMN subscriber; it comprises the Mobile Equipment (ME) and the Subscriber Identity Module (SIM), called UMTS Subscriber Identity Module (USIM) for Release 99 and following. The ME comprises the Mobile Termination (MT) which, depending on the application and services, may support various combinations of Terminal Adapter (TA) and Terminal Equipment (TE) functional groups. These functional groups are described in TS 24.002.

Up       Top

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

The Mobile-services Switching Centre (MSC) constitutes the interface between the radio system and the fixed networks. The MSC performs all necessary functions in order to handle the circuit switched services to and from the mobile stations.

In order to obtain radio coverage of a given geographical area, a number of BSS and/or RNS are normally required; i.e. each MSC would thus have to interface to one or more BSS(s) and/or RNS(s). In addition several MSCs may be required to cover a country.

When Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied, all the MSCs serving a pool-area share the responsibility to serve the MSs located in the pool-area. All these MSCs interface to all the BSS(s) and/or RNS(s) forming the pool-area.

The Mobile-services Switching Centre is an exchange, which performs all the switching and signalling functions for mobile stations located in a geographical area designated as the MSC area. When Intra Domain Connection of RAN Nodes to Multiple CN Nodes is applied, one or more MSCs serve a pool-area, but each individual MS is served by only one out of these MSCs, as described in TS 23.236. The main difference between a MSC and an exchange in a fixed network is that the MSC has to take into account the impact of the allocation of radio resources and the mobile nature of the subscribers and has to perform in addition, at least the following procedures:
  • procedures required for the location registration (see TS 23.012);
  • procedures required for handover (see TS 23.009).
When needed, the MSC can be implemented in two different entities: the MSC Server, handling only signalling, and the CS-MGW, handling user's data. A MSC Server and a CS-MGW make up the full functionality of a MSC.

Up       Top

defined from  Rel-4
Source:   TS 23.002, clause 4.1.2.1.1 

The MSC Server mainly comprises the call control (CC) and mobility control parts of a MSC.

The MSC Server is responsible for the control of mobile originated and mobile terminated CC CS Domain calls. It terminates the user-network signalling and translates it into the relevant network - network signalling. The MSC Server also contains a VLR to hold the mobile subscriber's service data and CAMEL related data.

The MSC Server controls the parts of the call state that pertain to connection control for media channels in a CS-MGW.

Up       Top

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

The MSCF is a functional entity which may be connected to the MMS Relay/Server to execute messaging related service logic. It may influence addressing, routeing and charging for multimedia messages. Furthermore it may control access rights of the user.

Up       Top

defined from  GSM Rel-96
Source:   –

see VLR

Up       Top

defined from  Rel-11
Source:   TS 23.682, clause 4.4.7 

To support translation of the IMSI to External Identifier(s) at the network egress, an AAA function (MTC AAA) is used in the HPLMN. The MTC AAA may be deployed to return the External Identifier(s) based on IMSI. Alternatively the MTC AAA may be deployed as a RADIUS/Diameter proxy between the GGSN/PGW and the AAA server in the external PDN.

Up       Top

defined from  Rel-11
Source:   TS 23.682, clause 4.4.2 

To support the Indirect and Hybrid models of MTC, one or more instances of an MTC InterWorking Function (MTC-IWF) reside in the HPLMN. A MTC-IWF may be a standalone entity or a functional entity of another network element. The MTC-IWF hides the internal PLMN topology and relays or translates signaling protocols used over Tsp to invoke specific functionality in the PLMN.

Up       Top