ETSI TS 129 468-2016 Universal Mobile Telecommunications System (UMTS) LTE Group Communication System Enablers for LTE (GCSE LTE) MB2 reference point Stage 3 (V13 1 0 3GPP TS 29 46.pdf

《ETSI TS 129 468-2016 Universal Mobile Telecommunications System (UMTS) LTE Group Communication System Enablers for LTE (GCSE LTE) MB2 reference point Stage 3 (V13 1 0 3GPP TS 29 46.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 129 468-2016 Universal Mobile Telecommunications System (UMTS) LTE Group Communication System Enablers for LTE (GCSE LTE) MB2 reference point Stage 3 (V13 1 0 3GPP TS 29 46.pdf（35页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1Universal Mobile TelGroup Communication SMB(3GPP TS 29.4TECHNICAL SPECIFICATION129 468 V12.4.0 (2016elecommunications System (LTE; n System Enablers for LTE (GB2 reference point; Stage 3 .468 version 12.4.0 Release 1216-01) (UMTS); (GCSE_LTE); 12) ETSI ETSI TS 129 468 V12.4.0 (2016-01)13GP

2、P TS 29.468 version 12.4.0 Release 12Reference RTS/TSGC-0329468vc40 Keywords LTE,UMTS 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

3、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 document shall not be modified

4、 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 ETSI Secretariat. Users

5、 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 document, please send your commen

6、t 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 by written permission of ETSI. The

7、 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, PLUGTESTSTM, UMTSTMand the ETSI logo are Tr

8、ade 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. ETSI ETSI TS 129 468 V12.4.0 (2016-

9、01)23GPP TS 29.468 version 12.4.0 Release 12Intellectual 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 foun

10、d 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.org/). Pursuant to the ETSI IPR Pol

11、icy, 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 present document. Foreword This Tec

12、hnical 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 references to the corresponding ET

13、SI 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“, “will not“, “can“ and “cannot“ are to

14、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 129 468 V12.4.0 (2016-01)33GPP TS 29.468 version 12.4.0 Release 12Content

15、s Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Architectural Overview 7g34.1 Reference Model 7g34.2 Functional Elements . 8g34.2.1 Group Comm

16、unication Service Application Server (GCS AS) 8g34.2.2 Broadcast-Multicast Service Centre (BM-SC) 8g35 Procedures over the MB2 Reference Point 9g35.1 TMGI and Flow ID handling 9g35.2 TMGI Management 9g35.2.1 TMGI Allocation Procedure . 9g35.2.2 TMGI Deallocation Procedure 10g35.2.3 TMGI Expiry Notif

17、ication Procedure . 10g35.3 MBMS Bearer Control Procedures 10g35.3.1 General 10g35.3.2 Activate MBMS Bearer Procedure . 10g35.3.3 Deactivate MBMS Bearer Procedure 11g35.3.4 Modify MBMS Bearer Procedure . 11g35.3.5 MBMS Bearer Status Indication Procedure 12g35.4 BM-SC selection 12g35.5 BM-SC overload

18、 control 12g35.6 Restoration Procedures . 12g35.6.1 General 12g35.6.2 Restart Counter . 13g35.6.3 GCS AS initiated Heartbeat Procedure . 13g35.6.4 BM-SC initiated Heartbeat Procedure 13g35.6.5 GCS AS procedures after detection of BM-SC Restart 13g35.6.6 BM-SC procedures after detection of GCS AS Res

19、tart 13g35.6.7 GCS AS procedures upon detection of MB2-C path failure . 13g35.6.8 BM-SC procedures upon detection of MB2-C path failure 14g36 MB2-C Protocol . 14g36.1 Protocol support . 14g36.1.1 Use of Diameter base protocol 14g36.1.2 Transport protocol 14g36.1.3 Advertising Application Support 14g

20、36.2 Initialization and maintenance of connection and session 15g36.3 Security on the MB2-C interface 15g36.4 MB2-C specific AVPs 15g36.4.1 General 15g36.4.2 BMSC-Address AVP 15g36.4.3 BMSC-Port AVP 16g36.4.4 MBMS- Bearer-Event AVP 16g36.4.5 MBMS-Bearer-Event-Notification AVP 16g36.4.6 MBMS-Bearer-R

21、equest AVP . 16g3ETSI ETSI TS 129 468 V12.4.0 (2016-01)43GPP TS 29.468 version 12.4.0 Release 126.4.7 MBMS-Bearer-Response AVP . 17g36.4.8 MBMS-Bearer-Result AVP 17g36.4.9 MBMS-Start-Time AVP . 18g36.4.10 Radio-Frequency AVP 18g36.4.11 TMGI-Allocation-Request AVP . 18g36.4.12 TMGI-Allocation-Respons

22、e AVP 18g36.4.13 TMGI-Allocation-Result AVP 18g36.4.14 TMGI-Deallocation-Request AVP . 19g36.4.15 TMGI-Deallocation-Response AVP . 19g36.4.16 TMGI-Deallocation-Result AVP 19g36.4.17 TMGI-Expiry AVP . 19g36.4.18 TMGI-Number AVP . 20g36.4.19 MB2U-Security AVP 20g36.5 MB2-C re-used AVPs 20g36.5.1 Gener

23、al 20g36.5.2 Supported-Feature-List AVP 21g36.5.2.1 Use of the Supported-Features AVP . 21g36.5.2.2 Supported-Feature-List AVP for the MB2-C application . 22g36.6 MB2-C Messages . 22g36.6.1 Command-Code Values 22g36.6.2 GCS-Action-Request (GAR) command 22g36.6.3 GCS-Action-Answer (GAA) command 23g36

24、.6.4 GCS-Notification-Request (GNR) command . 23g36.6.5 GCS-Notification-Answer (GNA) command . 24g37 MB2-U Protocol . 24g37.1 Protocol Stack 24g37.2 Procedures 26g3Annex A (informative): Call Flows . 27g3A.1 TMGI Management 27g3A.1.1 TMGI Allocation Procedure . 27g3A.1.2 TMGI Deallocation Procedure

25、 . 27g3A.1.3 TMGI Expiry Notification 28g3A.2 MBMS Bearer Control Procedures 29g3A.2.1 Activate MBMS Bearer Procedure . 29g3A.2.2 Deactivate MBMS Bearer Procedure . 29g3A.2.3 Modify MBMS Bearer Procedure 30g3A.2.4 MBMS Bearer Status Indication Procedure . 31g3A.3 Restoration Procedures . 32g3A.3.1 G

26、CS AS initiated Heartbeat Procedure 32g3A.3.2 BM-SC initiated Heartbeat Procedure 32g3Annex B (informative): Change history . 33g3History 34g3ETSI ETSI TS 129 468 V12.4.0 (2016-01)53GPP TS 29.468 version 12.4.0 Release 12Foreword This Technical Specification has been produced by the 3rd Generation P

27、artnership Project (3GPP). The contents of the present document are subject to 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

28、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 or greater indicates TSG approved document under change control. Y the second digit is incremented for all changes of substance, i.e. technical enhanc

29、ements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 468 V12.4.0 (2016-01)63GPP TS 29.468 version 12.4.0 Release 121 Scope This document defines the protocol for the MB2 reference point between the Gr

30、oup Communication Service Application Server (GCS AS) and the Broadcast-Multicast Service Centre (BM-SC). The MB2 reference point and related stage 2 procedures are defined in TS 23.468 4 as part of the Group Communication System Enablers for LTE. The stage 1 requirements for Group Communication Sys

31、tem Enablers for LTE are specified in TS 22.468 2. 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.)

32、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 t

33、he same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.468: “Group Communication System Enablers for LTE (GCSE_LTE)“. 3 3GPP TS 23.246: “Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description“. 4 3GPP TS 23.468: “

34、Group Communication System Enablers for LTE (GCSE_LTE); stage 2“. 5 3GPP TS 26.346: “Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs“. 6 3GPP TS 29.061: “Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)“. 7

35、 3GPP TS 29.212: “Policy and Charging Control (PCC); Reference points“. 8 3GPP TS 29.274: “3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3“. 9 3GPP TS 29.281: “General Packet Radio System (GPRS) Tunnelling Protoco

36、l User Plane (GTPv1-U)“. 10 3GPP TS 33.246: “Security of Multimedia Broadcast/Multicast Service (MBMS)“. 11 IETF RFC 791: “Transmission Control Protocol“. 12 IETF RFC 768: “User Datagram Protocol“. 13 IETF RFC 2234: “Augmented BNF for syntax specifications“. 14 IETF RFC 3588: “Diameter Base Protocol

37、“. 15 IETF RFC 4960: “Stream Control Transmission Protocol“. 16 IETF RFC 5719: “Updated IANA Considerations for Diameter Command Code Allocations“. 17 IETF RFC 5996: “The Internet Key Exchange (IKE)“. 18 IETF RFC 3947: “Negotiation of NAT-Traversal in the IKE“. 19 IETF RFC 3948: “UDP Encapsulation o

38、f IPsec ESP Packets“. ETSI ETSI TS 129 468 V12.4.0 (2016-01)73GPP TS 29.468 version 12.4.0 Release 1220 IETF RFC 4303: “IP Encapsulating Security Payload (ESP)“. 21 IETF RFC 6347: “Datagram Transport Layer Security Version 1.2“.# 22 3GPP TS 23.007: “Restoration procedures“. 23 3GPP TS 29.229: “Cx an

39、d Dx interfaces based on the Diameter protocol“. 24 3GPP TS 36.300: “E-UTRA and E-UTRAN overall description; Stage 2“. 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: MBMS beare

40、r: The service provided by the EPS to deliver the same IP datagrams to multiple receivers in a designated location. 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 preced

41、ence over the definition of the same abbreviation, if any, in TR 21.905 1. ARP Allocation and Retention Priority AVP Attribute-Value Pair BM-SC Broadcast-Multicast Service Centre DTLS Datagram Transport Layer Security ESP Encapsulating Security Payload GAA GCS-Action-Answer GAR GCS-Action-RequestGCS

42、 Group Communication Service GCSE Group Communication System Enablers GCS AS Group Communication Service Application Server GNA GCS-Notification-Answer GNR GCS-Notification-RequestMBMS-GW MBMS Gateway PCRF Policy and Charging Rules Function P-GW PDN Gateway TMGI Temporary Mobile Group Identity UDP U

43、ser Datagram Protocol 4 Architectural Overview 4.1 Reference Model Figure 4.1-1 shows a high level reference model of the architectural elements relevant to understand the MB2 reference point. More complete reference models for GCSE are contained in TS 23.468 4. ETSI ETSI TS 129 468 V12.4.0 (2016-01

44、)83GPP TS 29.468 version 12.4.0 Release 12UEGCS ASBM-SCP-GWMBMS-GWSGmbSGi-mbPCRFGxGC1SGiMB2-CApplicationdomainRxPLMNMB2-UScope of this specification Figure 4.1-1: Reference Model NOTE: The GC1 reference point between the UE and the GCS AS is unspecified in the present release. Data related to the GC

45、1 reference point are transported via the Sgi reference point between GCS AS and P-GW. 4.2 Functional Elements 4.2.1 Group Communication Service Application Server (GCS AS) The GCS AS is defined in TS 23.468 4 and supports the following functionality: - Exchanging GC1 signalling with the UE. - Recei

46、ving unicast uplink data from the UE via the SGi reference point. - Delivery of data to all the UEs belonging to a group using unicast delivery over the SGi reference point and/or MBMS delivery over the MB2 reference point. - Support for service continuity procedures for a UE to switch between unica

47、st delivery and MBMS delivery. - For MBMS delivery: - MB2-C procedures defined in TS 23.468 4, for requesting the BM-SC to activate, deactivate, modify an MBMS bearer, allocate/deallocate TMGI. - Forwarding of data to be delivered via an MBMS bearer to the BM-SC via the MB2-U reference point. 4.2.2

48、Broadcast-Multicast Service Centre (BM-SC) The BM-SC is defined in TS 23.246 3, with additions related to the MB2 reference point in TS 23.468 4, and supports the following functionality: - MBMS Broadcast Mode procedures defined in TS 23.246 3 (stage 2) and in TS 29.061 6 (stage 3). - MB2-C procedur

49、es defined in TS 23.468 4, for activating, deactivating, modifying an MBMS bearer, allocating/deallocating TMGI and notifying the TMGI expiry or the MBMS Bearer condition to GCS AS. - SGmb procedures for controlling MBMS broadcast bearers defined in TS 29.061 6. ETSI ETSI TS 129 468 V12.4.0 (2016-01)93GPP TS 29.468 version 12.4.0 Release 12- Reception of user data from the GCS AS via the MB2-U reference point and forwarding those data via the SGi-mb reference point as described in TS 29.061 6. 5 Pro