ETSI TS 125 446-2018 Universal Mobile Telecommunications System (UMTS) MBMS synchronisation protocol (SYNC) (V15 0 0 3GPP TS 25 446 version 15 0 0 Release 15).pdf

《ETSI TS 125 446-2018 Universal Mobile Telecommunications System (UMTS) MBMS synchronisation protocol (SYNC) (V15 0 0 3GPP TS 25 446 version 15 0 0 Release 15).pdf》由会员分享，可在线阅读，更多相关《ETSI TS 125 446-2018 Universal Mobile Telecommunications System (UMTS) MBMS synchronisation protocol (SYNC) (V15 0 0 3GPP TS 25 446 version 15 0 0 Release 15).pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 125 446 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); MBMS synchronisation protocol (SYNC) (3GPP TS 25.446 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 125 446 V15.0.0 (2018-07)13GPP TS 25.446 version 15.0.0 Release 15Reference RTS/TSGR-0325446vf00

2、Keywords 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 Grasse (06) N 7803/88 Important notice The present document can be downl

3、oaded 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. In case of any existin

4、g 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 document may be subjec

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

6、ple/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 without the

7、written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI regist

8、ered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registered and owned by the GSM Association. ETSI ETSI TS 125 446 V15.0.0 (2018-07)23GPP TS 25.446 version 15.0.0 Release 15Intelle

9、ctual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables 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: “Intellec

10、tual 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 Policy, no investigation, includin

11、g 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. Trademarks The present document may include trad

12、emarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present docum

13、ent does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or report

14、s 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, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminolog

15、y 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 ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI

16、 deliverables except when used in direct citation. ETSI ETSI TS 125 446 V15.0.0 (2018-07)33GPP TS 25.446 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Defini

17、tions 6g33.2 Abbreviations . 6g33.4 Specification notations . 7g34 General . 7g34.1 General aspects for the SYNC protocol for UTRAN . 7g34.1.1 General aspects . 7g34.2 General aspects for the SYNC protocol for E-UTRAN . 8g34.2.1 General aspects . 8g35 SYNC protocol version 1 . 8g35.1 General . 8g35.

18、1.1 Applicablity of SYNC protocol version 1. 8g35.1.1 Operation of the SYNC protocol 9g35.1.2 Interfaces of the SYNC protocol layer 9g35.2 SYNC protocol layer services 9g35.3 Services Expected from the UP Data Transport layer 9g35.4 Elementary procedures . 9g35.4.1 Transfer of User Data for MBMS pro

19、cedure 9g35.4.1.1 Successful operation 9g35.4.1.2 Unsuccessful operation . 10g35.4.2 Transfer of Synchronisation Information for MBMS procedure (without user data) . 10g35.4.2.1 Successful operation 10g35.4.2.2 Unsuccessful operation . 11g35.5 Elements for the SYNC protocol 11g35.5.1 General 11g35.5

20、.2 Frame format for the SYNC protocol . 12g35.5.2.1 Transfer of Synchronisation Information without payload (SYNC PDU Type 0) 12g35.5.2.2 Transfer of User Data for MBMS with uncompressed header (SYNC PDU Type 1) . 12g35.5.2.3 Transfer of User Data for MBMS with compressed header (SYNC PDU Type 2) .

21、13g35.5.2.4 Transfer of Synchronisation Information with Length of Packets (SYNC PDU Type 3) . 14g35.5.3 Coding of information elements in frames . 16g35.5.3.1 PDU Type . 16g35.5.3.2 Timestamp. 17g35.5.3.3 Packet Number 17g35.5.3.4 Elapsed Octet Counter . 17g35.5.3.5 Total Number Of Packet . 17g35.5

22、.3.6 Total Number Of Octet . 17g35.5.3.7 PDCP Information . 17g35.5.3.8 IPv6 Indicator 18g35.5.3.9 Uncompressed Payload IP header . 18g35.5.3.10 Header CRC 18g35.5.3.11 Payload CRC . 18g35.5.3.12 Padding . 18g35.5.3.13 Spare . 18g35.5.3.14 Spare extension . 18g35.5.3.15 Payload fields 19g35.5.3.16 L

23、ength of the Nth Packet 19g35.5.4 Timers . 19g3ETSI ETSI TS 125 446 V15.0.0 (2018-07)43GPP TS 25.446 version 15.0.0 Release 155.6 Handling of unknown, unforeseen and erroneous protocol data 19g35.6.1 General 19g35.6.2 CRC Calculation . 19g35.6.3 Relation between input and output of the Cyclic Redund

24、ancy Check 19g3Annex A (informative): Change history . 20g3History 21g3ETSI ETSI TS 125 446 V15.0.0 (2018-07)53GPP TS 25.446 version 15.0.0 Release 15Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subj

25、ect 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 increase in version number as follows: Version x.y.z where: x the first

26、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 enhancements, corrections, updates, etc. z the third digit is incremented when

27、 editorial only changes have been incorporated in the document. ETSI ETSI TS 125 446 V15.0.0 (2018-07)63GPP TS 25.446 version 15.0.0 Release 151 Scope The present document specifies the MBMS Synchronisation Protocol. For the release of this specification it is used on Iu towards UTRAN and M1 towards

28、 E-UTRAN. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. g404 References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. g404 For a specific r

29、eference, subsequent revisions do not apply. g404 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 d

30、ocument. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 25.410: “UTRAN Iu interface: General Aspects and Principles“. 3 3GPP TS 25.323: “Packet Data Convergence Protocol (PDCP) specification“. 4 3GPP TS 25.346: “Introduction of the Multimedia Broadcast Multicast Service (MBMS) in

31、the Radio Access Network (RAN); Stage 2“. 5 3GPP TS 36.440: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN“. 6 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Ac

32、cess Network (E-UTRAN); Overall description“. 3 Definitions 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 the same term

33、, if any, in TR 21.905 1. RAN Access interface: interface between the Core Network and the Radio Access Network. RAN Access node: termination point of the RAN Access interface at the Radio Access Network. MBMS RAB: denotes the Radio Access data bearer together with the RAN Access Interface data bear

34、er for MBMS service user data transmission. 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 precedence over the definition of the same abbreviation, if any, in TR 21.905

35、1. MRNC MBMS Master RNC (as specified in TS 25.346 4) SC-PTM Single Cell Point To Multipoint SYNC MBMS synchronisation protocol ETSI ETSI TS 125 446 V15.0.0 (2018-07)73GPP TS 25.446 version 15.0.0 Release 153.4 Specification notations For the purposes of the present document, the following notations

36、 apply: Procedure When referring to a procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word “procedure“, e.g. Iu Rate Control procedure. Frame When referring to a control or data frame in the specification, the

37、CONTROL/DATA FRAME NAME is written with all letters in upper case characters followed by the words “control/data frame“, e.g. TIME ALIGNMENT control frame. IE When referring to an information element (IE) in the specification the Information Element Name is written with the first letters in each wor

38、d in upper case characters and all letters in Italic font followed by the abbreviation “IE“, e.g. Frame Number IE. Value of an IE When referring to the value of an information element (IE) in the specification the “Value“ is written as it is specified in subclause 5.6.3 enclosed by quotation marks,

39、e.g. “0“ or “255“. 4 General 4.1 General aspects for the SYNC protocol for UTRAN 4.1.1 General aspects The MBMS Synchronisation protocol (SYNC) is located in the User plane of the Radio Network layer over the Iu interface: the Iu UP protocol layer. The SYNC protocol for UTRAN is used to convey user

40、data associated to MBMS Radio Access Bearers. One SYNC protocol instance is associated to one MBMS RAB and one MBMS RAB only. If several MBMS RABs are established towards one given UE, then these MBMS RABs make use of several SYNC protocol instances. SYNC protocol instances exist at Iu access point

41、as defined (TS 25.410 2) i.e. at CN and UTRAN. Whenever an MBMS RAB requires transfer of user data in the Iu UP, an Iu UP protocol instance exists at each Iu interface access points. These Iu UP protocol instances are established and released together with the associated MBMS RAB. The following figu

42、re illustrates the logical placement of the SYNC protocol layer and the placement of the Data Streams sources outside of the Access Stratum. UTRAN UE CN Access Stratum Non-Access StratumRadio (Uu) Iu SYNC Radio proto- colsSYNC TNL ProtocolTransport Layer NAS Data Streams NAS DataStreams Radio proto-

43、 cols TNL ProtocolFigure 4.1.1-1: SYNC protocol layer occurrence in UTRAN overall architecture (User Plane View) ETSI ETSI TS 125 446 V15.0.0 (2018-07)83GPP TS 25.446 version 15.0.0 Release 154.2 General aspects for the SYNC protocol for E-UTRAN 4.2.1 General aspects The MBMS Synchronisation protoco

44、l (SYNC) is located in the User plane of the Radio Network layer over the M1 interface: the M1 UP protocol layer. The SYNC protocol for E-UTRAN is used to convey user data associated to MBMS Radio Access Bearers. One SYNC protocol instance is associated to one MBMS E-RAB and one MBMS E-RAB only. SYN

45、C protocol instances exist at M1 access point as defined (TS 36.440 5) i.e. at EPC and E-UTRAN. Whenever an MBMS E-RAB requires transfer of user data in the M1 UP, an M1 UP protocol instance exists at each M1 interface access points. These M1 UP protocol instances are established and released togeth

46、er with the associated MBMS E-RAB. The following figure illustrates the logical placement of the SYNC protocol layer and the placement of the Data Streams sources outside of the Access Stratum. E-UTRAN UE CN Access Stratum Non-Access StratumRadio (Uu) M1 SYNC Radio proto- colsSYNC TNL ProtocolTransp

47、ort Layer NAS Data Streams NAS DataStreams Radio proto- cols TNL ProtocolFigure 4.2.1-1: SYNC protocol layer occurrence in E-UTRAN overall architecture (User Plane View) 5 SYNC protocol version 1 5.1 General 5.1.1 Applicablity of SYNC protocol version 1 This version of the specification specifies th

48、e SYNC protocol for UTRAN and E-UTRAN. It is on top of TNL in Iu (UTRAN) and M1 (E-UTRAN) user plane, i.e. Iu userplane TNL transports SYNC protocol PDUs over the Iu interface, M1 userplane TNL transports SYNC protocol PDUs over the M1 interface. As a specification convention, within this specificat

49、ion, the interface between the Core Network and the Radio Access Network is denoted as the “RAN Access Interface”, the termination point at the Radio Access Network is denoted as “RAN Access Node”, the termination point at the Core Network is denoted as “Core Network” (CN). Further, “MBMS RAB” denotes the Radio Access data bearer together with the RAN Access Interface data bearer for MBMS service user data transmission. For the application of the SYNC protocol to UTRAN, the RAN Access Interface is the Iu interface, the RAN Access Node is the RNC.