1、 ETSI TR 1Digital cellular telecoUniversal Mobile TelMultimedia BroadUTRAN(3GPP TR 25.9TECHNICAL REPORT 125 992 V13.0.0 (2016communications system (Phaelecommunications System (adcast/Multicast Service (MBMN/GERAN requirements .992 version 13.0.0 Release 13GLOBAL SYSTEMOBILE COMMUN16-01) hase 2+); (
2、UMTS); BMS); 13) TEM FOR ICATIONSRETSI ETSI TR 125 992 V13.0.0 (2016-01)13GPP TR 25.992 version 13.0.0 Release 13Reference RTR/TSGR-0025992vd00 Keywords GSM,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 000
3、17 - NAF 742 C Association but non lucratif enregistre 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 el
4、ectronic and/or print versions of the present document 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 (
5、PDF) version kept on a specific network drive within 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 http:/portal.etsi.org/tb/status/st
6、atus.asp If you find errors in the present 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 photoc
7、opying and microfilm except as authorized 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 20
8、16. All rights reserved. DECTTM, PLUGTESTSTM, 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. GSM and the GSM logo are Trade Marks regi
9、stered and owned by the GSM Association. ETSI ETSI TR 125 992 V13.0.0 (2016-01)23GPP TR 25.992 version 13.0.0 Release 13Intellectual 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
10、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 are available
11、 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) which are, or
12、 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 or GSM identit
13、ies. 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“, “should“, “sh
14、ould 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 citation. ETSI ETSI
15、TR 125 992 V13.0.0 (2016-01)33GPP TR 25.992 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Definitions, symbols and abbreviations . 5g33.1 Definitions 5g33.2 Symbols 6g33.1 Abbreviations . 6g34 Bac
16、kground and introduction . 6g35 RAN MBMS requirements . 6g35.1 MBMS Notification Requirements . 7g36 RAN MBMS functions . 8g36.1 Functions list 8g36.2 Function descriptions . 8g36.2.1 Admission control . 8g36.2.2 Identification of the number of UEs with activated MBMS service(s) in a cell . 8g36.2.3
17、 Selection, assignment and establishment and release of radio bearers . 9g36.2.4 Identification of MBMS parameters to UEs . 9g36.2.5 Alerting UEs that MBMS data is to be transmitted 9g36.2.6 Power control 9g36.2.7 Support of cell dhange and minimization of data loss 9g36.2.8 Maintenance of MBMS cont
18、ext 9g36.2.9 Replication of MBMS data streams 9g36.2.10 Transfer of MBMS data 9g36.3 Functional separation . 9g3Annex A: Change History 10g3History 11g3ETSI ETSI TR 125 992 V13.0.0 (2016-01)43GPP TR 25.992 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGen
19、eration 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 identifying change of release dat
20、e 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 substance, i.e. technic
21、al enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 125 992 V13.0.0 (2016-01)53GPP TR 25.992 version 13.0.0 Release 131 Scope This document is part of the RAN WI “Introduction of the Multimedia
22、Broadcast Multicast Service (MBMS) in RAN and it is linked to 3GPP TS 22.146 “Multimedia Broadcast Multicast Service; Stage-1“ 2 and the SA2 WI “Multimedia Broadcast/Multicast Service Architecture“, the work of which is reflected in 3GPP TS 23.246 3. The purpose of the present document is to address
23、 the UTRAN and GERAN MBMS requirements in order to help the TSG RAN and TSG GERAN working groups address the changes needed to existing specifications and also identify new specifications, that are required for the introduction of the WI “Introduction of the Multimedia Broadcast Multicast Service (M
24、BMS) in RAN“. 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. - For a specific ref
25、erence, 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 the present docume
26、nt. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications “. 2 3GPP TS 22.146: “Multimedia Broadcast/Multicast Service; Stage-1“. 3 3GPP TS 23.246: “Multimedia Broadcast Multicast Service; Architecture and Functional Description“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purp
27、oses of the present document, the following terms and definitions given in 1 and the following apply Broadcast mode: The part of MBMS that supports broadcast services. Counting: This is the function that UTRAN performs when it wishes to identify the number of multicast subscribers (all joined subscr
28、ibers, or just above a “threshold“) in a particular cell, that wish to receive a multicast session for a particular service. MBMS (Broadcast/Multicast) Session: A continuous and time-bounded reception of a broadcast/multicast service by the UE. A single broadcast/multicast service can only have one
29、broadcast/multicast session at any time. A broadcast/multicast service may consist of multiple successive broadcast/multicast sessions. Multicast mode: The part of MBMS that supports multicast services. MBMS broadcast activation: The process which enables the data reception from a specific broadcast
30、 mode MBMS on a UE. Thereby the user enables the reception locally on the UE. MBMS multicast activation (Joining):. The explicit point-to-point UE to network signalling, which enables a UE to become a member of a multicast group and thus start receiving data from a specific MBMS multicast service (w
31、hen data become available). MBMS Notification: The mechanism, which informs the UEs about the availability or coming availability of a specific MBMS RAB data in one given cell. ETSI ETSI TR 125 992 V13.0.0 (2016-01)63GPP TR 25.992 version 13.0.0 Release 13Service Announcements/Discovery: The mechani
32、sms should allow users to request or be informed about the range of MBMS services available Operators/service providers may consider several service discovery mechanisms. This could include standard mechanisms such as SMS, or depending on the capability of the terminal, applications that encourage u
33、ser interrogation. Users who have not already subscribed to a MBMS service should also be able to discover MBMS services. NOTE: Some of the above definitions have been taken from TS 22.146 2. Tracking: This is a function that allows UTRAN to follow the mobility of multicast subscribers. Inherently i
34、t can be used as a means of counting multicast subscribers. UE: Unless otherwise stated, UE is used to refer to both the UE and the MS. 3.2 Symbols (void) 3.1 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 21.905 1 and the following apply: MBMS Multimedia
35、Broadcast Multicast Service p-t-p Point-to-point p-t-m Point-to-multipoint 4 Background and introduction Following TSG RAN/SA#15, it was concluded that the service requirements 2 of MBMS are considered stable enough and the work on the architectural aspects have progressed to the extent that the wor
36、k in the RAN groups could be initiated. 5 RAN MBMS requirements Following the clarifications provided during the 3GPP MBMS workshop on stage 1 2 and stage 2 3, the following RAN requirements have been identified and are currently agreed within RAN WG2: 1. MBMS data transfer shall be downlink only. 2
37、. QoS attributes shall be the same for MBMS Multicast and Broadcast modes. 3 During MBMS data transmission it shall be possible to receive paging messages, which also should contain some additional information, such as CLI. 4 Simultaneous reception of MBMS and non-MBMS services shall depend upon UE
38、capabilities. 5 Simultaneous reception of more than one MBMS services shall depend upon UE capabilities. 6 A notification procedure shall be used to indicate the start of MBMS data transmission. This procedure shall contain MBMS RB information. The MBMS notification requirements are listed in subcla
39、use 5.1. 7 A mechanism to enable the Network to move MBMS subscribers between cells is required. 8 MBMS UE multicast activation (Joining) shall be transparent to UTRAN. 9 A mechanism is required that enables the non-transmission of MBMS multicast mode in a cell which does not contain any MBMS UEs jo
40、ined to the multicast group. 10 Reception of MBMS shall not be guaranteed at RAN level. MBMS does not support individual retransmissions at the radio link layer, nor does it support retransmissions based on feedback from individual subscribers at the ETSI ETSI TR 125 992 V13.0.0 (2016-01)73GPP TR 25
41、.992 version 13.0.0 Release 13radio level. This does not preclude the periodic repetitions of the MBMS content based on operator or content provider scheduling or retransmissions based on feedback at the application level. 11 MBMS shall not prevent the capability for SRNS/SBSS relocation. 12 A mecha
42、nism to provide UTRAN the received QoS per UE is not required as part of MBMS. 13 UE controlled service based cell selection/reselection shall not be permitted. 14 Handover and SGSN relocation shall not be affected by an active MBMS session. 15 In the case of UTRAN only, guaranteed “QoS“ linked to a
43、 certain initial downlink power setting is not required; however, the purpose and possibility of some reporting mechanism could be identified to measure the delivered QoS. NOTE: The above requirement is not applicable in GERAN, as a p-t-m type connection will use a similar power control mechanism to
44、 a broadcast channel. 16 MBMS Multicast mode transmissions should use dedicated resources (p-t-p) or common resources (p-t-m). The selection of the connection type (p-t-p or p-t-m) is operator dependent, typically based on downlink radio resource environment such as radio resource efficiency. A “thr
45、eshold“ related to the number of users may be utilised, resulting in the need for a mechanism to identify the number of subscribers in a given “area“. 17 MBMS solutions to be adopted should minimise the impact on the RAN physical layer and maximise reuse of existing physical layer and other RAN func
46、tionality. 18 MBMS charging should be transparent to the RAN. 19 MBMS should allow for low UE power consumption. 20 Header compression should be used. 21 MBMS should not prevent support for SGSN in pool. 22 Data loss during cell change should be minimal. 5.1 MBMS Notification Requirements The follow
47、ing requirements for MBMS notification mechanism(s) have been identified and currently agreed: 1 MBMS notification shall be transmitted within the MBMS service area. NOTE: If MBMS notification is transmitted in all cells of a corresponding MBMS service area or only in those cells where MBMS subscrib
48、ers are actually located, is FFS. 2 MBMS notification shall be sent so it could be received by all UEs with an activated MBMS service, regardless of their RRC state or the lack of an RRC connection. 3 MBMS notification should maximise the reuse of existing channels. 4 MBMS notification should allow
49、terminals to minimise their power consumption, meaning that UEs with an activated MBMS service should not listen permanently, but at regular intervals to MBMS notification. 5 Reception of MBMS notification cannot be guaranteed. 6 UEs may receive MBMS notification and simultaneously monitor other occasions, e.g. UE dedicated paging and CBS messages. The avoidance of collisions cannot be guaranteed. If collisions occur, the UE dedicated Paging has higher priority (UE requirement). ETSI ETSI TR 125 992 V13.0.0 (2016-01)83GPP TR 25.992 version 13.0.0 R
