ETSI TS 136 443-2016 LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) M2 Application Protocol (M2AP) (V13 3 0 3GPP TS 36 443 version 13 3 0 Release 13)《长期演进技术(LTE) .pdf

《ETSI TS 136 443-2016 LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) M2 Application Protocol (M2AP) (V13 3 0 3GPP TS 36 443 version 13 3 0 Release 13)《长期演进技术(LTE) .pdf》由会员分享，可在线阅读，更多相关《ETSI TS 136 443-2016 LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) M2 Application Protocol (M2AP) (V13 3 0 3GPP TS 36 443 version 13 3 0 Release 13)《长期演进技术(LTE) .pdf（141页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1EvolvedRadio AccM2 Appli3GPP TS 36.4TECHNICAL SPECIFICATION136 443 V13.2.0 (2016LTE; ed Universal Terrestrial ccess Network (E-UTRAN); plication Protocol (M2AP) .443 version 13.2.0 Release 1316-01) 13 ETSI ETSI TS 136 443 V13.2.0 (2016-01)13GPP TS 36.443 version 13.2.0 Release 13 Reference

2、 RTS/TSGR-0336443vd20 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present

3、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 document shall not be modified without the prior written authorization of ETSI. I

4、n 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 ETSI Secretariat. Users of the present document should be aware that the d

5、ocument 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 document, please send your comment to one of the following services: https:/portal.e

6、tsi.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 by written permission of ETSI. The content of the PDF version shall not be modified w

7、ithout 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, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its

8、 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. ETSI ETSI TS 136 443 V13.2.0 (2016-01)23GPP TS 36.443 version 13.2.0 Release 13 Intell

9、ectual 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 members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Right

10、s (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.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has

11、 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 present document. Foreword This Technical Specification (TS) has been produced by ETS

12、I 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 references to the corresponding ETSI deliverables. The cross reference between GSM,

13、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“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the E

14、TSI 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 443 V13.2.0 (2016-01)33GPP TS 36.443 version 13.2.0 Release 13 Contents Intellectual Property Rights 2g3Foreword . 2g3M

15、odal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions, symbols and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 9g34 General . 9g34.1 Procedure Specification Principles . 9g34.2 Forwards and Backwards Compatibility 9g34.3 Specification Notations 9g35 M2AP Serv

16、ices . 11g35.1 M2AP procedure modules 11g35.2 Parallel transactions 11g36 Services Expected from Signalling Transport 12g37 Functions of M2AP 13g38 M2AP Procedures 14g38.1 List of M2AP Elementary procedures 14g38.2 MBMS Session Start 14g38.2.1 General 14g38.2.2 Successful Operation 15g38.2.3 Unsucce

17、ssful Operation 16g38.2.4 Abnormal Conditions 16g38.3 MBMS Session Stop 16g38.3.1 General 16g38.3.2 Successful Operation 16g38.3.3 Abnormal Conditions 17g38.4 MBMS Scheduling Information . 17g38.4.1 General 17g38.4.2 Successful Operation 17g38.4.3 Abnormal Conditions 17g38.5 Reset . 17g38.5.1 Genera

18、l 17g38.5.2 Successful Operation 18g38.5.2.1 Reset Procedure Initiated from the MCE 18g38.5.2.2 Reset Procedure Initiated from the eNB 19g38.5.3 Abnormal Conditions 19g38.5.3.1 Abnormal Condition at the MCE 19g38.5.3.2 Abnormal Condition at the eNB 20g38.5.3.3 Crossing of Reset Messages 20g38.6 M2 S

19、etup 20g38.6.1 General 20g38.6.2 Successful Operation 20g38.6.3 Unsuccessful Operation 21g38.6.4 Abnormal Conditions 21g38.7 eNB Configuration Update . 21g38.7.1 General 21g38.7.2 Successful Operation 22g3ETSI ETSI TS 136 443 V13.2.0 (2016-01)43GPP TS 36.443 version 13.2.0 Release 13 8.7.3 Unsuccess

20、ful Operation 23g38.7.4 Abnormal Conditions 23g38.8 MCE Configuration Update . 23g38.8.1 General 23g38.8.2 Successful Operation 24g38.8.3 Unsuccessful Operation 25g38.8.4 Abnormal Conditions 25g38.9 Error Indication 25g38.9.1 General 25g38.9.2 Successful Operation 26g38.9.3 Abnormal Conditions 26g38

21、.10 MBMS Session Update 26g38.10.1 General 26g38.10.2 Successful Operation 27g38.10.3 Unsuccessful Operation 27g38.10.4 Abnormal Conditions 27g38.11 MBMS Service Counting . 28g38.11.1 General 28g38.11.2 Successful Operation 28g38.11.3 Unsuccessful Operation 28g38.11.4 Abnormal Conditions 28g38.12 MB

22、MS Service Counting Results Report . 29g38.12.1 General 29g38.12.2 Successful Operation 29g38.12.3 Abnormal Conditions 29g38.13 MBMS Overload Notification 29g38.13.1 General 29g38.13.2 Successful Operation 30g38.13.3 Abnormal Conditions 30g39 Elements for M2AP Communication . 31g39.1 Message Functio

23、nal Definition and Content 31g39.1.1 General 31g39.1.1 Message Contents . 31g39.1.1.1 Presence 31g39.1.1.2 Criticality 31g39.1.1.3 Range 31g39.1.1.4 Assigned Criticality . 31g39.1.2 MBMS SESSION START REQUEST . 32g39.1.3 MBMS SESSION START RESPONSE . 32g39.1.4 MBMS SESSION START FAILURE 32g39.1.5 MB

24、MS SESSION STOP REQUEST 33g39.1.6 MBMS SESSION STOP RESPONSE 33g39.1.7 MBMS SCHEDULING INFORMATION . 33g39.1.8 MBMS SCHEDULING INFORMATION RESPONSE 35g39.1.9 RESET 35g39.1.10 RESET ACKNOWLEDGE 35g39.1.11 M2 SETUP REQUEST . 36g39.1.12 M2 SETUP RESPONSE . 36g39.1.13 M2 SETUP FAILURE 37g39.1.14 ENB CON

25、FIGURATION UPDATE 37g39.1.15 ENB CONFIGURATION UPDATE ACKNOWLEDGE 38g39.1.16 ENB CONFIGURATION UPDATE FAILURE 38g39.1.17 MCE CONFIGURATION UPDATE . 39g39.1.18 MCE CONFIGURATION UPDATE ACKNOWLEDGE . 39g39.1.19 MCE CONFIGURATION UPDATE FAILURE 39g39.1.20 ERROR INDICATION . 40g39.1.21 MBMS SESSION UPDA

26、TE REQUEST 40g39.1.22 MBMS SESSION UPDATE RESPONSE 40g39.1.23 MBMS SESSION UPDATE FAILURE . 40g39.1.24 MBMS SERVICE COUNTING REQUEST 41g39.1.25 MBMS SERVICE COUNTING RESPONSE 41g3ETSI ETSI TS 136 443 V13.2.0 (2016-01)53GPP TS 36.443 version 13.2.0 Release 13 9.1.26 MBMS SERVICE COUNTING FAILURE . 41

27、g39.1.27 MBMS SERVICE COUNTING RESULTS REPORT . 42g39.1.28 MBMS OVERLOAD NOTIFICATION 42g39.2 Information Element Definitions 43g39.2.1 Radio Network Layer Related IEs 43g39.2.1.1 Message Type . 43g39.2.1.2 Cause. 43g39.2.1.3 Void. 45g39.2.1.4 Void. 45g39.2.1.5 Void. 46g39.2.1.6 Void. 46g39.2.1.7 Cr

28、iticality Diagnostics . 46g39.2.1.8 PMCH Configuration 47g39.2.1.9 MBMS Session List per PMCH 47g39.2.1.10 Global eNB ID 48g39.2.1.11 E-UTRAN CGI . 48g39.2.1.12 eNB MBMS Configuration data Item . 48g39.2.1.13 MCCH related BCCH Configuration Item 49g39.2.1.14 MBSFN Area Id 49g39.2.1.15 Time to Wait .

29、 50g39.2.1.16 Global MCE ID . 50g39.2.1.17 MBSFN Subframe Configuration . 50g39.2.1.18 Common Subframe Allocation Period 50g39.2.1.19 MCCH Update Time . 51g39.2.1.20 MBSFN Synchronisation Area Id . 51g39.2.1.21 Counting Result . 51g39.2.1.22 SC-PTM information 51g39.2.1.23 MBMS E-RAB QoS parameters

30、. 51g39.2.1.24 GBR QoS Information 52g39.2.1.25 Bit Rate . 52g39.2.1.26 Allocation and Retention Priority . 52g39.2.2 Transport Network Layer Related IEs 53g39.2.2.1 IP Address . 53g39.2.2.2 GTP-TEID . 53g39.2.3 NAS Related IEs . 53g39.2.3.1 MCE MBMS M2AP ID 53g39.2.3.2 eNB MBMS M2AP ID 54g39.2.3.3

31、TMGI 54g39.2.3.4 MBMS Session Identity 54g39.2.3.5 Void. 54g39.2.3.6 MBMS Service Area . 54g39.2.3.7 PLMN Identity 54g39.3 Message and Information Element Abstract Syntax (with ASN.1) 56g39.3.1 General 56g39.3.2 Usage of Private Message Mechanism for Non-standard Use 56g39.3.3 Elementary Procedure D

32、efinitions 56g39.3.4 PDU Definitions . 67g39.3.5 Information Element definitions . 102g39.3.6 Common definitions . 121g39.3.7 Constant definitions 123g39.3.8 Container definitions. 128g39.4 Message Transfer Syntax . 137g39.5 Timers 137g310 Handling of Unknown, Unforeseen and Erroneous Protocol Data

33、138g3Annex A (informative): Change history . 139g3History 140g3ETSI ETSI TS 136 443 V13.2.0 (2016-01)63GPP TS 36.443 version 13.2.0 Release 13 Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to

34、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:

35、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 editor

36、ial only changes have been incorporated in the document. ETSI ETSI TS 136 443 V13.2.0 (2016-01)73GPP TS 36.443 version 13.2.0 Release 13 1 Scope The present document specifies the E-UTRAN radio network layer signalling protocol for the M2 interface. The M2 Application Protocol (M2AP) supports the fu

37、nctions of the M2 interface by signalling procedures defined in this document. M2AP is developed in accordance to the general principles stated in TS 36.401 2 and TS 36.300 3. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the

38、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 3GP

39、P 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 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 36.401: “E-UTRAN Architecture Description“. 3 3GPP TS 36.300: “Evolv

40、ed Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2“. 4 3GPP TS 36.413: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)“. 5 ITU-T Recommendation X.691 (07/2002): “I

41、nformation technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER) “. 6 ITU-T Recommendation X.680 (07/2002): “Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation“. 7 Void 8 3GPP TS 23.246: “Multimedia Broadcast/Multicast Service (M

42、BMS); Architecture and functional description“. 9 3GPP TS 29.061 “Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)“. 10 Void 11 3GPP TS 36.331: “Evolved Universal Terrestrial Radio Access (E-UTRAN); Radio Resource Control (RRC

43、) Protocol Specification“. 12 3GPP TS 36.211: “Evolved Universal Terrestrial Radio Access (E-UTRAN); Physical Channels and Modulation“. 13 3GPP TS 36.445: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); M1 Data Transport“. 14 3GPP TS 29.281: “General Packet Radio Service (GPRS); Tunne

44、lling Protocol User Plane (GTPv1-U)“. ETSI ETSI TS 136 443 V13.2.0 (2016-01)83GPP TS 36.443 version 13.2.0 Release 13 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 defi

45、ned in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. Elementary Procedure: M2AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between eNBs and the MCE. These Elementary Procedures are defined separately

46、 and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as standalone proce

47、dures, which can be active in parallel. The usage of several M2AP EPs together or together with EPs from other interfaces is specified in stage 2 specifications (e.g. TS 36.300 3 and TS 23.246 8). An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: - C

48、lass 1: Elementary Procedures with response (success and/or failure). - Class 2: Elementary Procedures without response. For Class 1 EPs, the types of responses can be as follows: Successful: - A signalling message explicitly indicates that the elementary procedure successfully completed with the re

49、ceipt of the response. Unsuccessful: - A signalling message explicitly indicates that the EP failed. - On time supervision expiry (i.e. absence of expected response). Successful and Unsuccessful: - One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome. Class 2 EPs are considered always successful. eNB MBMS M2AP ID: Unique identity, referencing the MBMS-service-associated logical M2-connection within an eNB. MCE MBMS