Top   in Index   Prev   Next

TS 36.445
E-UTRAN – Interfaces supporting MBMS –
M1 Data Transport

V18.0.0 (PDF)2024/03  10 p.
V17.0.0  2022/03  10 p.
V16.0.0  2020/06  10 p.
V15.0.0  2018/09  10 p.
V14.0.0  2017/03  10 p.
V13.0.0  2015/12  10 p.
V12.0.0  2014/09  10 p.
V11.0.0  2012/09  10 p.
V10.1.0  2011/06  10 p.
V9.2.1  2011/04  10 p.
Mr. Ma, Zijiang
ZTE Corporation

Content for  TS 36.445  Word version:  16.0.0

Here   Top

1  ScopeWord‑p. 5

The present document specifies the standards for user data transport protocols over the E-UTRAN M1 interface.

2  ReferencesWord‑p. 5

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 29.281: "General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)".
RFC 768  (1980-08): "User Datagram Protocol".
RFC 2474  (1998-12): "Definition of the Differentiated Services Field (DS Field) in the Ipv4 and Ipv6 Headers".
RFC 2460  (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".
RFC 791  (1981-09): "Internet Protocol".
RFC 3376  (2002-10): "Internet Group Management Protocol, Version 3".
RFC 3810  (2004-06): "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".

3  Definitions, symbols and abbreviationsWord‑p. 5

3.1  DefinitionsWord‑p. 5

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
interface between an eNB and an EPC for MBMS data delivery, providing an interconnection point between the EUTRAN and the EPC. M1 is a user plane interface between E-UTRAN and EPC. It is also considered as a reference point.

3.2  SymbolsWord‑p. 5

For the purposes of the present document, the following symbols apply:
Symbol format (EW)

3.3  AbbreviationsWord‑p. 6

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
Differentiated Service
Evolved Packet Core
Evolved UTRA
Evolved UTRAN
GPRS Tunnelling Protocol
Internet Protocol
Multimedia Broadcast Multicast Service
Transmission Control Protocol
Tunnel Endpoint Identifier
User Datagram Protocol

4  Data Link LayerWord‑p. 6

The support of any suitable data link Layer technique - like Ethernet, etc. - techniques shall not be prevented.

5  M1 interface user plane protocolWord‑p. 6

5.1  GeneralWord‑p. 6

The transport layer for MBMS data streams over M1 is an IP based Transport. The following Figure shows the transport protocol stacks over M1.
Copy of original 3GPP image for 3GPP TS 36.445, Fig. 5.1-1: Transport network layer for MBMS data streams over M1
The GTP-U (TS 29.281) protocol over UDP over IP shall be supported as the transport for MBMS data streams on the M1 interface. The data link layer is as specified in clause 4.
On IP multicast mode, the transport bearer is identified by the GTP-U TEID (TS 29.281) and the IP multicast address (source TEID, IP address of multicast source, IP multicast address).

5.2  GTP-UWord‑p. 6

The GTP-U (TS 29.281) protocol shall be used over the M1 interface toward the EPC.

5.3  UDP/IPWord‑p. 7

The path protocol used shall be UDP (RFC 768).
The UDP port number for GTP-U shall be as defined in TS 29.281.
eNB and EPC shall support fragmentation and assembly of GTP packets at the IP layer.
The eNB and EPC shall support IPv6 (RFC 2460) and/or IPv4 (RFC 791).
IP multicast (RFC 3376, RFC 3810) shall be supported for point-to-multipoint delivery of MBMS data streams for multi-cell transmission.
The packet processing function in the EPC shall send MBMS data of a given MBMS bearer to the TNL IP multicast address associated to that particular MBMS bearer.

5.4  Diffserv code point markingWord‑p. 7

IP Differentiated Services code point marking (RFC 2474) shall be supported. The mapping between traffic categories and Diffserv code points shall be configurable by O&M based on QoS Class Identifier (QCI) Characteristics and other E-UTRAN traffic parameters. Traffic categories are implementation-specific and may be determined from the application parameters.

$  Change HistoryWord‑p. 8

Up   Top