1、 ETSI TS 125 324 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); Broadcast/Multicast Control (BMC) (3GPP TS 25.324 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 125 324 V14.0.0 (2017-04)13GPP TS 25.324 version 14.0.0 Release 14Reference RTS/TSGR-0225324ve00 Key
2、words 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 download
3、ed 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 existing o
4、r 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 subject t
5、o 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/People
6、/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 wri
7、tten 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. 3GPP
8、TM 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 324 V14.0.0 (2017-04)23GPP TS 25.324 version 14.0.0 Release 14Intellectual Property
9、 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); Essen
10、tial, 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 carried o
11、ut 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 Generatio
12、n 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 and
13、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 Ru
14、les (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 324 V14.0.0 (2017-04)33GPP TS 25.324 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs termi
15、nology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 General . 7g34.1 Model of BMC . 7g35 Functions 8g36 Services provided to Upper Layers 8g37 Services expected from RLC 9g38 Elements for layer-to-layer communication . 9
16、g38.1 Service Primitives between RRC and BMC . 9g38.1.1 Primitives 9g38.1.1.1 CBMC-Measurement-IND 9g38.1.1.2 CBMC-Rx-IND . 9g38.1.1.3 CBMC-Config-REQ . 10g38.1.2 Parameters. 10g38.1.2.1 CB-Traffic-Volume . 10g38.1.2.2 Action 10g38.1.2.3 DRX selection . 10g38.1.2.4 CTCH configuration 10g38.2 Service
17、 Primitives between upper layer (U-plane) and BMC 11g38.2.1 Primitives 11g38.2.1.1 Primitives used in relation to UMTS Core Network . 11g38.2.1.1.1 BMC-Data-REQ 11g38.2.1.1.2 BMC-Data-IND. 12g38.2.1.1.3 BMC-Data-CNF 12g38.2.1.1.4 BMC-Congestion-IND 12g38.2.1.1.5 BMC-Normal-IND 12g38.2.1.1.6 BMC-Acti
18、vation-REQ . 12g38.2.1.1.7 BMC-Deactivation-REQ . 12g38.2.1.1.8 BMC-DRX-REQ . 13g38.2.1.1.9 BMC-Error-IND 13g38.2.1.2 Primitives used for ANSI-41 Core Network . 13g38.2.1.2.1 BMC-Data41-REQ 13g38.2.1.2.2 BMC-Data41-IND . 13g38.2.1.2.3 BMC-Error41-IND 13g38.2.2 Parameters. 14g38.2.2.1 Message-ID . 14
19、g38.2.2.2 Serial Number . 14g38.2.2.3 Data-Coding-Scheme 14g38.2.2.4 CB-Data 14g38.2.2.5 Category 14g38.2.2.6 Repetition-Period 14g38.2.2.7 Number-of-Broadcasts-Requested 14g38.2.2.8 CB-DRX-Schedule-Period 14g38.2.2.9 Reserved-CB-Capacity 15g3ETSI ETSI TS 125 324 V14.0.0 (2017-04)43GPP TS 25.324 ver
20、sion 14.0.0 Release 148.2.2.10 Cause . 15g38.2.2.11 Transport Layer Message 15g38.2.2.12 Broadcast Address . 15g38.2.2.13 Error Type . 15g39 Procedures 15g39.1 BMC Message Broadcast . 15g39.2 Generation of Schedule message 15g39.3 Traffic volume measurement 16g39.4 BMC message reception . 16g310 BMC
21、 Messages 17g310.1 General . 17g310.2 BMC CBS Message 17g310.3 BMC Schedule Message 17g310.4 BMC CBS41 Message 18g311 Information Elements . 19g311.1 Message Type . 19g311.2 Message ID . 19g311.3 Serial Number 19g311.4 Data Coding Scheme 20g311.5 CB Data 20g311.6 Offset to Begin CTCH Block Set Index
22、 . 20g311.7 Length of CBS Schedule Period . 21g311.8 New Message Bitmap . 21g311.9 Message Description 22g311.10 Broadcast Address 23g311.11 CB Data41 23g311.12 CBS Schedule Message Extension . 24g311.13 CBS Message Serial Numbers 24g311.14 Serial Number List Entry . 25g3Annex A (informative): Chang
23、e history . 26g3History 27g3ETSI ETSI TS 125 324 V14.0.0 (2017-04)53GPP TS 25.324 version 14.0.0 Release 14Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG
24、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: 1 presented to TSG for informat
25、ion; 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 editorial only changes have been inco
26、rporated in the document. ETSI ETSI TS 125 324 V14.0.0 (2017-04)63GPP TS 25.324 version 14.0.0 Release 141 Scope The present document provides the description of the Broadcast/Multicast Control Protocol (BMC). This protocol adapts broadcast and multicast services on the radio interface. 2 References
27、 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 reference, subsequent revisions d
28、o 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 document. 1 3GPP TS 25.322: “RLC Proto
29、col Specification“. 2 3GPP TS 25.301: “Radio Interface Protocol Architecture“. 3 3GPP TS 23.041: “Technical realization of Cell Broadcast Service (CBS)“. 4 3GPP TS 23.038: “Alphabets and Language“. 5 3GPP TS 25.419: “UTRAN Iu interface: Service Area Broadcast Protocol SABP“. 6 3GPP TS 25.925: “Radio
30、 Interface for Broadcast/Multicast Services“. 7 TIA/EIA-41-D: “Technical realization of Cell Broadcast Service (CBS)“. 8 TIA/EIA-637-A: “TR45 Short Message Service for Spread Spectrum Systems“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following te
31、rms and definitions apply. CB message: user data as transmitted from Cell Broadcast Centre to UE (BMC SDU) CB repetition period: period after which a CB message should be broadcast again if more than one repetition are requested Number of Broadcast Requested: number of broadcasts requested for a CB
32、message. This number is infinite or finite DRX Schedule Period: schedule period as optionally requested by the CBC (unit: seconds) Reserved CB Capacity: percentage of the capacity reserved for CB messages with category HIGH on the allocated radio resources CTCH, FACH and S-CCPCH. This parameter can
33、be set optionally by the CBC. CTCH Block Set: subset of the transport block set of FACH on which the CTCH used for CBS is mapped uniquely CBS schedule period: finite sequence of CTCH Block Sets of variable length in which scheduled CB messages are broadcast ETSI ETSI TS 125 324 V14.0.0 (2017-04)73GP
34、P TS 25.324 version 14.0.0 Release 143.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AS Access Stratum BMC Broadcast/Multicast Control C-SAP Control Service Access Point CBC Cell Broadcast Centre CBS Cell Broadcast Service CTCH Common Traffic ChannelCTC
35、H-BS CTCH Block Set FACH Forward Access Channel IE Information Elementkbps kilo-bits per second L1 Layer 1 (physical layer) L2 Layer 2 (data link layer) L3 Layer 3 (network layer) MAC Medium Access Control NAS Non Access Stratum NSAPI Network layer Service Access Point PDCP Packet Data Convergence P
36、rotocol RLC Radio Link Control RRC Radio Resource Control UE User Equipment 4 General 4.1 Model of BMC Broadcast/Multicast Control (BMC) is a sublayer of L2 that exists in the User-Plane only. It is located above RLC. The L2/BMC sublayer is assumed as transparent for all services except broadcast/mu
37、lticast. Figure 4.1-1 shows the model of the L2/BMC sublayer within the UTRAN radio interface protocol architecture. At the UTRAN side, the BMC sublayer shall consist of one BMC protocol entity per cell. Each BMC entity requires a single CTCH, which is provided by the MAC sublayer, through the RLC s
38、ublayer. The BMC requests the Unacknowledged Mode service of the RLC. It is assumed that there is a function in the RNC above BMC that resolves the geographical area information of the CB message (or, if applicable, performs evaluation of a cell list) received from the Cell Broadcast Centre (CBC). A
39、 BMC protocol entity serves only those messages at BMC-SAP that are to be broadcast into a specified cell. ETSI ETSI TS 125 324 V14.0.0 (2017-04)83GPP TS 25.324 version 14.0.0 Release 14L2/BMC sublayerRRCBMC-SAPuser-planeL2/RLC sublayerBMCRLCUMCTCH-SAPCBMC-SAPFigure 4.1-1: BMC protocol model 5 Funct
40、ions The functions are specified in 2. They are: - Storage of Cell Broadcast Messages. - Traffic volume monitoring and radio resource request for CBS. - Scheduling of BMC messages. - Transmission of BMC messages to UE. - Delivery of Cell Broadcast messages to upper layer (NAS). 6 Services provided t
41、o Upper Layers The BM-SAP provides a broadcast/multicast transmission service in the user plane on the radio interface for common user data in unacknowledged mode. The BMC sublayer interacts with other entities as illustrated in figure 1 of chapter 4. The interactions with the upper layer/U-plane an
42、d the RRC layer are specified in terms of primitives where the primitives represent the logical exchange of information and control between the BMC sublayer and higher layers. They do not specify or constrain implementations. The (adjacent) layers connect to each other through Service Access Points
43、SAPs). Three types of primitives are used for this document, as follows: - REQUEST: This type is used when a higher layer is requesting a service from a lower layer. ETSI ETSI TS 125 324 V14.0.0 (2017-04)93GPP TS 25.324 version 14.0.0 Release 14- INDICATION: This type is used by a lower layer provi
44、ding a service to notify its higher layer of activities concerning that higher layer. - CONFIRM: This type is used by a lower layer providing the requested service to confirm to the higher layer that the activity has been completed. The primitives defined below are for communications between upper l
45、ayer and BMC, as well as RRC and BMC in the same protocol stack. For the BMC sublayer two sets of primitives are defined. - Primitives between BMC and upper layer (U-plane): BMC - Generic name - Type: Parameters. - Primitives between BMC and the RRC entity: CBMC - Generic name - Type: Parameters. 7
46、Services expected from RLC The BMC uses the unacknowledged mode service of the RLC sublayer. See 1 for details. 8 Elements for layer-to-layer communication 8.1 Service Primitives between RRC and BMC 8.1.1 Primitives The primitives supported at CBMC-SAP between RRC and BMC are shown in Table 8.1.1-1.
47、 Table 8.1.1-1: Primitives between BMC and RRC Generic Name Parameters CBMC-Measurement-IND CB-Traffic-Volume CBMC-Rx-IND Action, DRX selection CBMC-Config-REQ CTCH configuration8.1.1.1 CBMC-Measurement-IND The CBMC-Measurement-IND primitive is used by BMC to indicate the CB traffic volume. Primitiv
48、e Type: indication. Parameters: CB-Traffic-Volume. 8.1.1.2 CBMC-Rx-IND The CBMC-Rx-IND primitive is used by BMC to indicate to RRC whether CB message reception shall start or stop and indicate when CB messages of interest are arriving in the next CBS schedule period. Primitive Type: indication. ETSI
49、 ETSI TS 125 324 V14.0.0 (2017-04)103GPP TS 25.324 version 14.0.0 Release 14Parameters: Action. DRX selection. 8.1.1.3 CBMC-Config-REQ The CBMC-Config-REQ primitive is used by RRC to inform the BMC about the setting of the CTCH configuration. Primitive Type: indication. Parameters: CTCH configuration. 8.1.2 Parameters 8.1.2.1 CB-Traffic-Volume Expected CTCH transmission rate kbps. Value set: 0,1,32. 8.1.2.2 Action Start CBS reception. Stop CBS reception. 8.1.2.3 DRX selection List of absolute CTCH BS indices which are of interest and which shoul
