1、 ETSI TS 1Evolved Universal TerresSignalling Transport Broadcast Multicas(3GPP TS 36.4TECHNICAL SPECIFICATION136 442 V13.0.0 (2016LTE; restrial Radio Access Network (rt for interfaces supporting Mulast Service (MBMS) within E-UT6.442 version 13.0.0 Release 1316-01) k (E-UTRAN); ultimedia UTRAN ) ETS
2、I ETSI TS 136 442 V13.0.0 (2016-01)13GPP TS 36.442 version 13.0.0 Release 13Reference RTS/TSGR-0336442vd00 Keywords LTE ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucrati
3、f enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the pres
4、ent document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network dr
5、ive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present
6、 document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized
7、by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTS
8、TM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. E
9、TSI ETSI TS 136 442 V13.0.0 (2016-01)23GPP TS 36.442 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI member
10、s and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.o
11、rg/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the p
12、resent document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being
13、references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “wil
14、l not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 136 442 V13.0.0 (2016-01)33GPP TS 36.44
15、2 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 M2 Interface . 6g34.1 M2 signalling bearer . 6g34.1.1 Functions and p
16、rotocol stack 6g34.2 Data link layer 6g34.3 IP layer . 6g34.4 Transport layer . 6g35 M3 Interface . 7g35.1 M3 signalling bearer . 7g35.1.1 Functions and protocol stack 7g35.2 Data link layer 7g35.3 IP layer . 7g35.4 Transport layer . 8g3Annex A (informative): Change history . 9g3History 10g3ETSI ETS
17、I TS 136 442 V13.0.0 (2016-01)43GPP TS 36.442 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG appro
18、val. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 o
19、r greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 13
20、6 442 V13.0.0 (2016-01)53GPP TS 36.442 version 13.0.0 Release 131 Scope 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 a
21、nd 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 The following documents contain provisions which, through reference in this text, constitute provisions of the present doc
22、ument. 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 (inclu
23、ding 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 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 IETF RFC 2460 (1998-12): “Internet Protocol, Version 6 (IPv6) Specification“. 3 IETF RFC 791
24、(1981-09): “Internet Protocol“. 4 IETF RFC 2474 (1998-12): “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers“. 5 IETF RFC 4960 (2007-09): “Stream Control Transmission Protocol“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present doc
25、ument, the terms and definitions given in TR 21.905 1 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 1. M2: E-UTRAN internal control plane interface between an eNB and an MCE, It is also considered as a refe
26、rence point. M3: Control plane interface between an E-UTRAN (MCE) and MME. It is also considered as a reference point. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes pre
27、cedence over the definition of the same abbreviation, if any, in TR 21.905 1. eNB E-UTRAN Node B DiffServ Differentiated ServiceIP Internet Protocol MME Mobility Management Entity PPP Point to Point Protocol SCTP Stream Control Transmission Protocol ETSI ETSI TS 136 442 V13.0.0 (2016-01)63GPP TS 36.
28、442 version 13.0.0 Release 134 M2 Interface 4.1 M2 signalling bearer 4.1.1 Functions and protocol stack 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
29、 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. SCTP IP Data link layer M2-AP Physical layer Radio Network Layer TransportNetworkLayer Figure 4.1.1: M2 signalling bearer protocol stac
30、k The transport network layer is based on IP transport, comprising SCTP on top of IP. 4.2 Data link layer The support of any suitable data link layer protocol, e.g. PPP, Ethernet, etc., shall not be prevented. 4.3 IP layer The eNB and MCE shall support IPv6 (IETF RFC 2460 2) and/or IPv4 (IETF RFC 79
31、1 3). 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 IETF RFC 2474 4. 4.4 Transport layer SCTP (IETF RFC 4960 5) shall be supported as the transport layer of M2 signalling beare
32、r. 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 netwo
33、rk. There shall be only one SCTP association established between one MCE and eNB pair. ETSI ETSI TS 136 442 V13.0.0 (2016-01)73GPP TS 36.442 version 13.0.0 Release 13The eNB shall establish the SCTP association. The SCTP Destination Port number value assigned by IANA to be used for M2-AP is 36443. W
34、ithin 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 mul
35、tiple 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 IETF RFC 4960 5 in 5.2. 5 M3 Interface 5.1 M3 signall
36、ing 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 signa
37、lling bearer is shown in figure 5.1.1 and details on each protocol are described in the following clauses. SCTP IP Data link layer M3-AP Physical layer Radio Network Layer TransportNetworkLayer Figure 5.1.1: M3 signalling bearer protocol stack The transport network layer is based on IP transport, co
38、mprising 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
39、transmission for delivering M3-AP messages. ETSI ETSI TS 136 442 V13.0.0 (2016-01)83GPP TS 36.442 version 13.0.0 Release 13The 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 lay
40、er 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 signallin
41、g 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
42、 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 mu
43、lti-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. ETSI ETSI TS 136 442 V13.0.0 (2016-01)93GPP TS 36.442 version 13.0.0 Release 13Anne
44、x 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.
45、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 ETSI ETSI TS 136 442 V13.0.0 (2016-01)103GPP TS 36.442 version 13.0.0 Release 13History Document history V13.0.0 January 2016 Publication
