Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TS 36.442
E-UTRAN – Interfaces supporting MBMS –
Signalling Transport

3GPP‑Page   ETSI‑search   CONTENT↓
V18.0.0 (PDF)  2024/03  11 p.
V17.0.0  2022/03  11 p.
V16.0.0  2020/06  11 p.
V15.0.0  2018/09  11 p.
V14.0.0  2017/03  11 p.
V13.0.0  2015/12  11 p.
V12.0.0  2014/09  11 p.
V11.0.0  2012/09  11 p.
V10.2.0  2011/09  11 p.
V9.1.1  2011/04  11 p.
Rapporteur:
Mrs. Shi, Nianshan
Ericsson LM

Content for  TS 36.442  Word version:  18.0.0

Here   Top
1 Scope  2 References  3 Definitions and abbreviations  4 M2 Interface  5 M3 Interface  $ Change History 

 

1  Scope  p. 5

The present document specifies the standards for signalling transport to be used across M2 and M3 interfaces. M2 interface is a logical interface between the eNB and the MCE. M3 interface is a logical interface between the MCE and the MME. The present document describes how the M2-AP signalling messages are transported over M2, and how the M3-AP signalling messages are transported over M3.

2  References  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.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
RFC 2460  (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".
[3]
RFC 791  (1981-09): "Internet Protocol".
[4]
RFC 2474  (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".
[5]
RFC 4960  (2007-09): "Stream Control Transmission Protocol".
Up

3  Definitions and abbreviations  p. 5

3.1  Definitions  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.
M2:
E-UTRAN internal control plane interface between an eNB and an MCE, It is also considered as a reference point.
M3:
Control plane interface between an E-UTRAN (MCE) and MME. It is also considered as a reference point.
Up

3.2  Abbreviations  p. 5

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.
eNB
E-UTRAN Node B
DiffServ
Differentiated Service
IP
Internet Protocol
MME
Mobility Management Entity
PPP
Point to Point Protocol
SCTP
Stream Control Transmission Protocol

4  M2 Interface  p. 6

4.1  M2 signalling bearer  p. 6

4.1.1  Functions and protocol stack  p. 6

M2 signalling bearer provides the following functions:
  • Provision of reliable transfer of M2-AP message over M2 interface
  • Provision of networking and routeing function
  • Provision of redundancy in the signalling network
The protocol stack for M2 signalling bearer is shown in Figure 4.1.1 and details on each protocol are described in the following clauses.
Copy of original 3GPP image for 3GPP TS 36.442, Fig. 4.1.1: M2 signalling bearer protocol stack
Figure 4.1.1: M2 signalling bearer protocol stack
(⇒ copy of original 3GPP image)
Up
The transport network layer is based on IP transport, comprising SCTP on top of IP.

4.2  Data link layer  p. 6

The support of any suitable data link layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented.

4.3  IP layer  p. 6

The eNB and MCE shall support IPv6 (RFC 2460) and/or IPv4 (RFC 791).
The IP layer of M2 only supports point-to-point transmission for delivering M2-AP messages.
The eNB and MCE shall support the Diffserv Code Point marking as described in RFC 2474.

4.4  Transport layer  p. 6

SCTP (RFC 4960) shall be supported as the transport layer of M2 signalling bearer. The Payload Protocol Identifier assigned by IANA to be used by SCTP for the application layer protocol M2-AP is 43.
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 eNB pair.
The eNB shall establish the SCTP association. The SCTP Destination Port number value assigned by IANA to be used for M2-AP is 36443.
Within the SCTP association established between one MCE and eNB pair:
  • a single pair of stream identifiers shall be reserved for the use of M2-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 MCE or eNB, at any time for an already established SCTP association, which shall be handled as defined in Section 5.2 of RFC 4960.
Up

5  M3 Interface  p. 7

5.1  M3 signalling bearer  p. 7

5.1.1  Functions and protocol stack  p. 7

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.
Copy of original 3GPP image for 3GPP TS 36.442, Fig. 5.1.1: M3 signalling bearer protocol stack
Figure 5.1.1: M3 signalling bearer protocol stack
(⇒ copy of original 3GPP image)
Up
The transport network layer is based on IP transport, comprising SCTP on top of IP.

5.2  Data link layer  p. 7

The support of any suitable data link layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented.

5.3  IP layer  p. 7

The E-UTRAN and MME shall support IPv6 (RFC 2460) and/or IPv4 (RFC 791).
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 RFC 2474.

5.4  Transport layer  p. 8

SCTP (RFC 4960) 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 Section 5.2 of RFC 4960.
Up

$  Change History  p. 9

Up   Top