1、 ETSI TS 136 440 V14.0.0 (2017-04) LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN (3GPP TS 36.440 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS
2、136 440 V14.0.0 (2017-04)13GPP TS 36.440 version 14.0.0 Release 14Reference RTS/TSGR-0336440ve00 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 lucratif enregist
3、re 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 present docume
4、nt 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 drive within
5、 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 https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx 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 2017. 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. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Tr
9、ade Marks registered and owned by the GSM Association. ETSI ETSI TS 136 440 V14.0.0 (2017-04)23GPP TS 36.440 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essen
10、tial IPRs, if any, is publicly available for ETSI members 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
11、 are available on the ETSI Web server (https:/ipr.etsi.org/). 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)
12、 which are, or may be, or may become, essential to the present 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
13、or GSM identities. These should be interpreted as being 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“,
14、 “should“, “should not“, “may“, “need not“, “will“, “will 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 citati
15、on. ETSI ETSI TS 136 440 V14.0.0 (2017-04)33GPP TS 36.440 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope. . 6g32 References 6g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Symbols 7g33.3 Abbrevi
16、ations . 7g34 General Architecture for EUTRAN MBMS. 7g35 Functions of M1 interface for MBMS 8g35.1 General . 8g35.2 Multicast group management function . 8g35.3 Content synchronization function . 8g36 Functions of M2 interface for MBMS 8g36.1 General . 8g36.2 M2 interface setup and configuration upd
17、ate functions 8g36.3 MBMS Session management function . 8g36.3.1 M2 service context management function 9g36.3.2 MBMS E-RAB management functions 9g36.3.3 M2 link management function 9g36.3.4 MBMS Service Suspension and Resumption function . 9g36.4 MBMS Scheduling Information transfer function 9g36.5
18、 MBMS signalling synchronization over M2 9g36.6 M2 interface reset and error processing function . 9g36.6.1 Error indication . 9g36.6.2 Reset . 9g36.7 MBMS Counting Function . 10g37 Functions of M3 interface for MBMS 10g37.1 General . 10g37.2 MBMS Session management function . 10g37.2.1 M3 service c
19、ontext management function 10g37.2.2 MBMS E-RAB management functions 10g37.3 M3 interface reset and error processing function . 10g37.3.1 Error indication . 10g37.3.2 Reset . 10g37.4 M3 interface setup and configuration update functions 10g38 Protocol structure for MBMS related interface in E-UTRAN
20、. 11g38.1 General . 11g38.2 M1 11g38.3 M2 11g38.4 M3 11g39 Other MBMS E-UTRAN Interface Specifications . 11g39.1 Layer 1 for interfaces supporting MBMS within E-UTRAN (3GPP TS 36.441) . 11g39.2 Signalling Transport for interfaces supporting MBMS within E-UTRAN (3GPP TS 36.442) 11g39.3 E-UTRAN M2 App
21、lication Protocol (M2AP) (3GPP TS 36.443) . 11g39.4 E-UTRAN M3 Application Protocol (M3AP) (3GPP TS 36.444) . 12g39.5 E-UTRAN M1 Data Transport (3GPP TS 36.445) 12g39.6 E-UTRAN MBMS synchronisation protocol (3GPP TS 25.446) . 12g3ETSI ETSI TS 136 440 V14.0.0 (2017-04)43GPP TS 36.440 version 14.0.0 R
22、elease 14Annex A (informative): Change history . 13g3History 14g3ETSI ETSI TS 136 440 V14.0.0 (2017-04)53GPP TS 36.440 version 14.0.0 Release 14Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to
23、 continuing work within the TSG and may change following formal TSG approval. 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:
24、 1 presented to TSG for information; 2 presented to TSG for approval; 3 or 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 edito
25、rial only changes have been incorporated in the document. ETSI ETSI TS 136 440 V14.0.0 (2017-04)63GPP TS 36.440 version 14.0.0 Release 141 Scope. The present document describes the overall architecture of the interface for the provision of MBMS in the E-UTRAN. This includes also a description of the
26、 general aspects, assumptions and principles guiding the architecture and interface. The MBMS functions to be provided within that architecture are summarized. It provides an introduction to the TSG RAN TS 36.44x series of UMTS Technical Specifications that define the different interfaces introduced
27、 for MBMS provision in E-UTRAN. 2 References 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. -
28、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
29、the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 36.441: “Layer 1 for interfaces supporting MBMS within E-UTRAN” 3 3GPP TS 36.442: “Signalling Transport for interfaces supporting MBMS within E-UTRAN” 4 3GPP TS 36.443: “EUTRAN M2 Application Protocol (M2AP)” 5 3
30、GPP TS 36.444: “EUTRAN M3 Application Protocol (M3AP)” 6 3GPP TS 36.445: “E-UTRAN M1 Data Transport” 7 3GPP TS 25.446: “MBMS synchronisation protocol (SYNC)” 8 3GPP TS 23.246: “MBMS Architecture and functional description” 9 3GPP TS 36.300: “E-UTRA and E-UTRAN overall description” 10 IETF RFC 4960 (
31、2007-09): “Stream Control Transmission Protocol“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, 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
32、the same term, if any, in TR 21.905 1. Definition format : . example: text used to clarify abstract rules by applying them literally. ETSI ETSI TS 136 440 V14.0.0 (2017-04)73GPP TS 36.440 version 14.0.0 Release 143.2 Symbols For the purposes of the present document, the following symbols apply: Symb
33、ol format 3.3 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 precedence over the definition of the same abbreviation, if any, in TR 21.905 1. BM-SC Broadcast-Multicast Servi
34、ce Centre EPC Evolved Packet Core MCE Multi-cell/multicast Coordination Entity MME Mobility Management Entity RNL Radio Network Layer TNL Transport Network Layer4 General Architecture for EUTRAN MBMS EUTRAN EPC MBMS GW MME eNodeB MCE M3 M1 M2 Sm Figure 4-1 General Architecture for E-UTRAN MBMS Figur
35、e 4-1 shows a simplified architecture for MBMS in LTE/SAE. It consists of EPC functional entities and E-UTRAN nodes. Functions of MBMS EPC entities are defined in TS 23.246 8. Functions of MBMS E-UTRAN nodes are defined in TS 36.300 9. It should be noted that TS 36.300 9 also allows MCE be deployed
36、inside eNodeB. Interfaces related to E-UTRAN (i.e. M1, M2 and M3) are introduced in this document. For MBMS, control signaling and user plane data packet are distributed from the EPC to E-UTRAN through different interfaces. uni25CF Control plane interfaces M3, M2 interface are pure control plane int
37、erfaces. M3 between MME and MCE mainly carries MBMS session management signaling. A MCE is connected to one or more than one eNBs within the same MBSFN through M2 interface mainly for MBMS session management signaling and radio configuration signaling. uni25CF User plane interface M1 interface is a
38、pure user plane interface. ETSI ETSI TS 136 440 V14.0.0 (2017-04)83GPP TS 36.440 version 14.0.0 Release 14A MBMS GW is connected to multiple eNBs through M1 interface for data distribution. Reference points within EPC are not in the scope of this document. Please refer to TS 23.246 8 for details. 5
39、Functions of M1 interface for MBMS 5.1 General “M1” Interface: MBMS GW eNB The M1 interface is the user plane interface of MBMS between MBMS GW and eNB. IP multicast is used to deliver the downlink packets over the M1 interface and there is no uplink data over M1 radio network layer. SYNC protocol (
40、TS 25.446 7) is used over the M1 interface to keep the content synchronization for MBMS service data transmission. 5.2 Multicast group management function IP multicast is used to deliver the packets over the M1 interface. The M1 interface has the function to manage the IP multicast groups. The MBMS
41、GW maintains the IP multicast groups. The MBMS GW allocates the IP multicast group address when the session arrives, and may release it at session stop. At the eNB side, the eNB joins the IP multicast group to receive the MBMS User Plane data at session start, leaves the IP multicast group when the
42、session stops, may leave the IP multicast group when the session suspends and may rejoin the IP multicast group when the session resumes. 5.3 Content synchronization function The packets delivered over M1 interface will be synchronously transmitted by eNBs. To support the inter-eNB content synchroni
43、zation, SYNC protocol layer is defined between BM-SC to eNB, which is used to carry additional information that enable eNBs to identify the timing for radio frame transmission and detect packet loss. Every packet in M1 contains the SYNC protocol information which is encapsulated at BM-SC. 6 Function
44、s of M2 interface for MBMS 6.1 General “M2” Interface: MCE eNB An Application Part (M2AP) is defined in TS 36.443 4 for this interface, which conveys at least radio configuration data for the multi-cell transmission mode eNBs and Session Control Signaling. SCTP (IETF RFC 4960 10) is used as signalin
45、g transport i.e. Point-to-Point signaling is applied. 6.2 M2 interface setup and configuration update functions The M2 Setup (respectively the eNB and MCE configuration update) function allows to exchange (respectively update) application level data needed for the eNB and MCE to interoperate correct
46、ly on the M2 interface after the TNL association has become operational. 6.3 MBMS Session management function MBMS session management function is responsible for starting, updating, and stopping MBMS sessions. ETSI ETSI TS 136 440 V14.0.0 (2017-04)93GPP TS 36.440 version 14.0.0 Release 146.3.1 M2 se
47、rvice context management function The M2 service context management function supports the establishment of the necessary overall initial service context including MBMS E-RAB context, M2 signalling connection ID(s), etc. The establishment of the overall initial M2 service context is initiated by the
48、MCE. The M2 service context management function also supports the release of the context previously established in the eNB due to service termination. The release of the context is triggered by the MCE. 6.3.2 MBMS E-RAB management functions The MBMS E-RAB service management function is responsible f
49、or establishing and releasing E-UTRAN resources for service data transport. The establishment of E-UTRAN resources is triggered by the MCE. The release of E-UTRAN resources is triggered by the MCE. 6.3.3 M2 link management function The M2 signalling link management function provides a reliable transfer of the radio network signalling between eNBs and MCE. The SCTP is used to support the exchange of M2 Application Protocol (M2AP) signalling messages between eNBs and MCE. 6.3.4 MBMS Service Suspension and Resumption function The
