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:  Interfaces / Reference Points

   #      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

 

|  M1  |  M2  |  M3  |  Ma  |  Mb  |  MB2  |  Mc  |  MCData‑DS‑1  |  MCData‑DS‑2  |  MCData‑DS‑3  |  MCData‑FD‑1  |  MCData‑FD‑2  |  MCData‑FD‑3  |  MCData‑FD‑4  |  MCData‑SDS‑1  |  MCData‑SDS‑2  |  MCData‑SDS‑3  |  MCPTT‑1  |  MCPTT‑2  |  MCPTT‑3  |  MCPTT‑4  |  MCPTT‑5  |  MCPTT‑6  |  MCPTT‑7  |  MCPTT‑8  |  MCPTT‑9  |  MCVideo‑1  |  MCVideo‑2  |  MCVideo‑3  |  MCVideo‑4  |  MCVideo‑5  |  MCVideo‑6  |  MCVideo‑7  |  MCVideo‑8  |  MCVideo‑9  |  Mg  |  Mi  |  Mj  |  Mk  |  Ml  |  Mm  |  MM10  |  Mn  |  Mp  |  Mr  |  Mr'  |  Mx  |  Mw  |  Mz  |

 

M1   (GTPv1-U)

Up       Top

between  MBMS-GW
and  E-UTRAN / UTRAN

see it   here

specified from  Rel-9  in
TS 23.246, clause 4.3.3
TS 29.281
TS 36.300, clause 15.7a
TS 36.445 

This reference point is used between MBMS-GW and E-UTRAN/UTRAN for MBMS data delivery using IP Multicast.


M2   (M2AP)

Up       Top

between  MCE
and  eNodeB

specified from  Rel-9  in
TS 23.246, clause 4.3.3
TS 36.300, clause 15.8
TS 36.443 

This reference point is used to exchange signalling between MCE and eNodeB for MBMS Session Control.


M3   (M3AP)

Up       Top

between  MME
and  MCE

see it   here

specified from  Rel-9  in
TS 23.246, clause 4.3.3
TS 36.300, clause 15.9
TS 36.444 

This reference point is used to exchange signalling between MME and MCE for MBMS Session Control.


Ma   (SIP)

Up       Top

between  I-CSCF
and  AS

specified from  Rel-8  in
TS 23.228, clause 4.2.4c 

The Interrogating-CSCF to AS reference point is used to:
  • forward SIP requests destined to a Public Service Identity hosted by an Application Server directly to the Application Server;
  • originate a session on behalf of a user or Public Service Identity, if the AS has no knowledge of a S‑CSCF assigned to that user or Public Service Identity.


Mb   (user data)

Up       Top

between  IMS
and  IPv6 networks

specified from  Rel-5
Source:   TS 23.002, clause 6a.7.14 

Via the Mb reference point IPv6 network services are accessed. These IPv6 network services are used for user data transport. Note, that GPRS provides IPv6 network services to the UE, i.e. the GPRS Gi reference point and the IMS Mb reference point may be the same.


MB2   (Diameter)

Up       Top

between  GCS AS
and  BM-SC

specified from  Rel-12
in  TS 23.468  and  TS 29.468 

The MB2 reference point provides the ability for the application to:
  • Request the allocation/deallocation of a set of TMGIs,
  • Request to activate, deactivate, and modify an MBMS bearer.
The MB2 reference point provides the ability for the BM-SC to:
  • Notify the application of the status of an MBMS bearer.
Commands:
  • GAR/GAA:  GCS-Action-Request/Answer
  • GNR/GNA:  GCS-Notification-Request/Answer
See also  RFC 6733  for Diameter Base Protocol, and  TS 29.230  for 3GPP-specific Diameter codes and identifiers.


Mc

Up       Top

between  (G)MSC Server
and  CS-MGW

see it   here

specified from  Rel-4
Source:   TS 23.002, clause 6.4.1.7 

The Mc reference point describes the interfaces between the MSC Server and CS-MGW, and between the GMSC Server and CS-MGW. It has the following properties:
  • Full compliance with the H.248 standard, baseline work of which is currently carried out in ITU-T Study Group 16, in conjunction with IETF MEGACO WG.
  • Flexible connection handling which allows support of different call models and different media processing purposes not restricted to H.323 usage.
  • Open architecture where extensions/Packages definition work on the interface may be carried out.
  • Dynamic sharing of MGW physical node resources. A physical MGW can be partitioned into logically separate virtual MGWs/domains consisting of a set of statically allocated Terminations.
  • Dynamic sharing of transmission resources between the domains as the MGW controls bearers and manage resources according to the H.248 protocols.
The functionality across the Mc reference point will need to support mobile specific functions such as SRNS relocation/handover and anchoring. It is expected that current H.248/IETF Megaco standard mechanisms can be applied to enable this.



Up       Top