5 M3 Interface
36.4423GPPEvolved Universal Terrestrial Radio Access Network (E-UTRAN)Release 17Signalling Transport for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRANTS
5.1 M3 signalling bearer
5.1.1 Functions and protocol stack
M3 signalling bearer provides the following functions:
– Provision of reliable transfer of M3-AP message over M3 interface
– Provision of networking and routeing function
– Provision of redundancy in the signalling network
The protocol stack for M3 signalling bearer is shown in figure 5.1.1 and details on each protocol are described in the following clauses.
Figure 5.1.1: M3 signalling bearer protocol stack
The transport network layer is based on IP transport, comprising SCTP on top of IP.
5.2 Data link layer
The support of any suitable data link layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented.
5.3 IP layer
The E-UTRAN and MME shall support IPv6 (IETF RFC 2460 [2]) and/or IPv4 (IETF RFC 791 [3]).
The IP layer of M3 only supports point-to-point transmission for delivering M3-AP messages.
The MCE and MME shall support the Diffserv Code Point marking as described in IETF RFC 2474 [4].
5.4 Transport layer
SCTP (IETF RFC 4960 [5]) shall be supported as the transport layer of M3 signalling bearer. The Payload Protocol Identifier assigned by IANA to be used by SCTP for the application layer protocol M3-AP is 44.
SCTP refers to the Stream Control Transmission Protocol developed by the Sigtran working group of the IETF for the purpose of transporting various signalling protocols over IP network.
There shall be only one SCTP association established between one MCE and MME pair.
The MCE shall establish the SCTP association. The SCTP Destination Port number value assigned by IANA to be used for M3-AP is 36444.
Within the SCTP association established between one MCE and MME pair:
– a single pair of stream identifiers shall be reserved for the use of M3-AP elementary procedures.
Transport network redundancy may be achieved by SCTP multi-homing between two end-points, of which one or both is assigned with multiple IP addresses. SCTP end-points shall support a multi-homed remote SCTP end-point. For SCTP endpoint redundancy an INIT may be sent from MME or MCE, at any time for an already established SCTP association, which shall be handled as defined in IETF RFC 4960 [5] in § 5.2.
Annex A (informative):
Change history
|
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
New |
|
2009-10 |
Update to take into account comments raised at RAN3 #65bis |
0.0.2 |
|||
|
2009-12 |
Stepping the version to 2.0.0 for approval at RAN#46 |
2.0.0 |
|||
|
46 |
RP-091210 |
Approved at RAN#46 |
9.0.0 |
||
|
47 |
RP-100226 |
0001 |
2 |
Editorial corrections |
9.1.0 |
|
2010-12 |
Created Rel-10 version based on v. 9.1.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 |
0002 |
Reference review outcome in TS 36.442 |
10.1.0 |
|
|
53 |
RP-111195 |
0003 |
Introduction of SCTP PPI and Destination Port number for MBMS |
10.2.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 |
||||