1、 ETSI TS 125 446 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); MBMS synchronisation protocol (SYNC) (3GPP TS 25.446 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 125 446 V14.0.0 (2017-04)13GPP TS 25.446 version 14.0.0 Release 14Reference RTS/TSGR-0325446ve00
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. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3
8、GPPTM 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 125 446 V14.0.0 (2017-04)23GPP TS 25.446 version 14.0.0 Release 14Intellectual Prope
9、rty 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 Rights (IPRs); Es
10、sential, 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 been carrie
11、d 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 ETSI 3rd Genera
12、tion 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, UMTS, 3GPP a
13、nd 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 ETSI Drafting
14、 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 125 446 V14.0.0 (2017-04)33GPP TS 25.446 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs te
15、rminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 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 pr
16、otocol for E-UTRAN . 8g34.2.1 General aspects . 8g35 SYNC protocol version 1 . 9g35.1 General . 9g35.1.1 Applicablity of SYNC protocol version 1. 9g35.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 t
17、he UP Data Transport layer 9g35.4 Elementary procedures . 10g35.4.1 Transfer of User Data for MBMS procedure 10g35.4.1.1 Successful operation 10g35.4.1.2 Unsuccessful operation . 10g35.4.2 Transfer of Synchronisation Information for MBMS procedure (without user data) . 11g35.4.2.1 Successful operati
18、on 11g35.4.2.2 Unsuccessful operation . 11g35.5 Elements for the SYNC protocol 12g35.5.1 General 12g35.5.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 (S
19、YNC PDU Type 1) . 13g35.5.2.3 Transfer of User Data for MBMS with compressed header (SYNC PDU Type 2) . 14g35.5.2.4 Transfer of Synchronisation Information with Length of Packets (SYNC PDU Type 3) . 15g35.5.3 Coding of information elements in frames . 17g35.5.3.1 PDU Type . 17g35.5.3.2 Timestamp. 18
20、g35.5.3.3 Packet Number 18g35.5.3.4 Elapsed Octet Counter . 18g35.5.3.5 Total Number Of Packet . 18g35.5.3.6 Total Number Of Octet . 18g35.5.3.7 PDCP Information . 19g35.5.3.8 IPv6 Indicator 19g35.5.3.9 Uncompressed Payload IP header . 19g35.5.3.10 Header CRC 19g35.5.3.11 Payload CRC . 19g35.5.3.12
21、Padding . 19g35.5.3.13 Spare . 19g35.5.3.14 Spare extension . 20g35.5.3.15 Payload fields 20g35.5.3.16 Length of the Nth Packet 20g3ETSI ETSI TS 125 446 V14.0.0 (2017-04)43GPP TS 25.446 version 14.0.0 Release 145.5.4 Timers . 20g35.6 Handling of unknown, unforeseen and erroneous protocol data 20g35.
22、6.1 General 20g35.6.2 CRC Calculation . 20g35.6.3 Relation between input and output of the Cyclic Redundancy Check 21g3Annex A (informative): Change history . 22g3History 23g3ETSI ETSI TS 125 446 V14.0.0 (2017-04)53GPP TS 25.446 version 14.0.0 Release 14Foreword This Technical Specification has been
23、 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 approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifyin
24、g 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 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of
25、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 125 446 V14.0.0 (2017-04)63GPP TS 25.446 version 14.0.0 Release 141 Scope The present document specifies the MBMS Synch
26、ronisation Protocol. For the release of this specification it is used on Iu towards UTRAN and M1 towards E-UTRAN. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. uni25CF References are either specific (iden
27、tified by date of publication, edition number, version number, etc.) or non-specific. uni25CF For a specific reference, subsequent revisions do not apply. uni25CF 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
28、-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 25.410: “UTRAN Iu interface: General Aspects and Principles“. 3 3GPP TS 25.323: “Packet Data Convergence Protoco
29、l (PDCP) specification“. 4 3GPP TS 25.346: “Introduction of the Multimedia Broadcast Multicast Service (MBMS) in 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 Multime
30、dia Broadcast Multicast Service (MBMS) within E-UTRAN“. 6 3GPP TS 36.300: “Evolved Universal Terrestrial Radio Access 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
31、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. 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 Radi
32、o Access Network. MBMS RAB: denotes the Radio Access data bearer together with the RAN Access Interface data bearer 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 def
33、ined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 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 V14.0.0 (2017-04)73GPP TS 25.446 versi
34、on 14.0.0 Release 143.4 Specification notations For the purposes of the present document, the following notations 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 “proce
35、dure“, e.g. Iu Rate Control procedure. Frame When referring to a control or data frame in the specification, the 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 informa
36、tion element (IE) in the specification the Information Element Name is written with the first letters in each word 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
37、) in the specification the “Value“ is written as it is specified in subclause 5.6.3 enclosed by quotation marks, 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 N
38、etwork layer over the Iu interface: the Iu UP protocol layer. The SYNC protocol for UTRAN is used to convey user 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, th
39、en these MBMS RABs make use of several SYNC protocol instances. SYNC protocol instances exist at Iu access point 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. Thes
40、e Iu UP protocol instances are established and released together with the associated MBMS 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. ETSI ETSI TS 125 446 V14.0.0 (2017-04)83GPP TS
41、 25.446 version 14.0.0 Release 14UTRAN UE CN Access Stratum Non-Access StratumRadio (Uu) Iu SYNC Radio proto- colsSYNC TNL ProtocolTransport Layer NAS Data Streams NAS DataStreams Radio proto- cols TNL ProtocolFigure 4.1.1-1: SYNC protocol layer occurrence in UTRAN overall architecture (User Plane V
42、iew) 4.2 General aspects for the SYNC protocol for E-UTRAN 4.2.1 General aspects The MBMS Synchronisation protocol (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 M
43、BMS Radio Access Bearers. One SYNC protocol instance is associated to one MBMS E-RAB and one MBMS E-RAB only. SYNC 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 insta
44、nce exists at each M1 interface access points. These M1 UP protocol instances are established and released together 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 St
45、ratum. E-UTRAN UE CN Access Stratum Non-Access StratumRadio (Uu) M1 SYNC Radioproto-colsSYNC TNL ProtocolTransport 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) ETSI ETSI TS 125 44
46、6 V14.0.0 (2017-04)93GPP TS 25.446 version 14.0.0 Release 145 SYNC protocol version 1 5.1 General 5.1.1 Applicablity of SYNC protocol version 1 This version of the specification specifies the 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
47、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 specification, the interface between the Core Network and the Radio Access Network is denoted as the “RAN Access Interfa
48、ce”, 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
49、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. For the application of the SYNC protocol to E-UTRAN, the RAN Access Interface is the M1 interface, the RAN Access Node is the eNB. 5.1.1 Operation of the SYNC protocol The SYNC protocol layer is present for data streams that originate in the CN and carry additional information within a specific userplane-frame. The two strata communicate through a Service Access Point for Non Access Stratum (NAS) Data Stre
