5 M1 interface user plane protocol
36.4453GPPEvolved Universal Terrestrial Radio Access Network (E-UTRAN)M1 data transportRelease 17TS
5.1 General
The transport layer for MBMS data streams over M1 is an IP based Transport. The following figure shows the transport protocol stacks over M1.
Figure 5.1-1: Transport network layer for MBMS data streams over M1
The GTP-U (TS 29.281 [2]) 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 [2]) and the IP multicast address (source TEID, IP address of multicast source, IP multicast address).
5.2 GTP-U
The GTP-U (TS 29.281 [2]) protocol shall be used over the M1 interface toward the EPC.
5.3 UDP/IP
The path protocol used shall be UDP (IETF RFC 768 [3]).
The UDP port number for GTP-U shall be as defined in TS 29.281 [2].
eNB and EPC shall support fragmentation and assembly of GTP packets at the IP layer.
The eNB and EPC shall support IPv6 (IETF RFC 2460 [5]) and/or IPv4 (IETF RFC 791 [6]).
IP multicast (IETF RFC 3376 [7], IETF RFC3810 [8]) 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 marking
IP Differentiated Services code point marking (IETF RFC 2474 [4]) 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.
Annex A (informative):
Change history
|
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
New |
|
2009-10 |
First draft |
0.0.0 |
|||
|
2009-11 |
Capture the agreements in RAN3#66 |
1.0.0 |
|||
|
2009-12 |
Presented for approval at RAN#46 |
2.0.0 |
|||
|
46 |
RP-091255 |
Approved at RAN#46 |
9.0.0 |
||
|
47 |
RP-100226 |
0001 |
2 |
Clean up of unicast related text |
9.1.0 |
|
48 |
RP-100597 |
0002 |
Correction and Completion of M1 |
9.2.0 |
|
|
2010-12 |
Created Rel-10 version based on v. 9.2.0 |
10.0.0 |
|||
|
SP-49 |
SP-100629 |
Clarification on the use of References (TS 21.801 CR#0030) |
10.0.1 |
||
|
52 |
RP-110685 |
0003 |
2 |
Correction of references |
10.1.0 |
|
2012-09 |
Update to Rel-11 version (MCC) |
11.0.0 |
|||
|
2014-09 |
Update to Rel-12 version (MCC) |
12.0.0 |
|||
|
2015-12 |
Update to Rel-13 version (MCC) |
13.0.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
SA#75 |
Promotion to Release 14 without technical change |
14.0.0 |
||||
|
2018-09 |
RP#81 |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
2020-07 |
SA#88-e |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2022-03 |
SA#95-e |
Promotion to Release 17 without technical change |
17.0.0 |
||||