1、 ETSI TS 125 324 V15.0.0 (2018-07) Universal Mobile Telecommunications System (UMTS); Broadcast/Multicast Control (BMC) (3GPP TS 25.324 version 15.0.0 Release 15) TECHNICAL SPECIFICATION ETSI ETSI TS 125 324 V15.0.0 (2018-07)13GPP TS 25.324 version 15.0.0 Release 15Reference RTS/TSGR-0625324vf00 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. 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 registere
8、d 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 324 V15.0.0 (2018-07)23GPP TS 25.324 version 15.0.0 Release 15Intellectu
9、al 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: “Intellectua
10、l 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, including I
11、PR 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 tradema
12、rks 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 document
13、 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 reports u
14、sing 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 terminology I
15、n 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 de
16、liverables except when used in direct citation. ETSI ETSI TS 125 324 V15.0.0 (2018-07)33GPP TS 25.324 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitio
17、ns 6g33.2 Abbreviations . 6g34 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 . 9g38.1 Service Primitives between RRC and BMC . 9g38.1.1 Primitives 9g38.1.1.1 CBMC-Measurement-IND 9g
18、38.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 Primitives between upper layer (U-plane) and BMC 11g38.2.1 Primitives 11g38.2.1.1 Primitives used in
19、 relation to UMTS Core Network . 11g38.2.1.1.1 BMC-Data-REQ 11g38.2.1.1.2 BMC-Data-IND. 11g38.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-Activation-REQ . 12g38.2.1.1.7 BMC-Deactivation-REQ . 12g38.2.1.1.8 BMC-DRX-REQ . 12g38.2.1.1.9 BMC-Error
20、-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. 13g38.2.2.1 Message-ID . 13g38.2.2.2 Serial Number . 14g38.2.2.3 Data-Coding-Scheme 14g38.2.2.4 CB-Data 14g38.2.2.5 Category 14g
21、38.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 14g38.2.2.10 Cause . 14g3ETSI ETSI TS 125 324 V15.0.0 (2018-07)43GPP TS 25.324 version 15.0.0 Release 158.2.2.11 Transport Layer Message 14g38.2.2.12 Broadcast Ad
22、dress . 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 Messages 16g310.1 General . 16g310.2 BMC CBS Message 17g310.3 BMC Schedule Message 17g310.4 BMC CBS4
23、1 Message 18g311 Information Elements . 18g311.1 Message Type . 18g311.2 Message ID . 19g311.3 Serial Number 19g311.4 Data Coding Scheme 19g311.5 CB Data 19g311.6 Offset to Begin CTCH Block Set Index . 20g311.7 Length of CBS Schedule Period . 20g311.8 New Message Bitmap . 20g311.9 Message Descriptio
24、n 21g311.10 Broadcast Address 22g311.11 CB Data41 22g311.12 CBS Schedule Message Extension . 23g311.13 CBS Message Serial Numbers 23g311.14 Serial Number List Entry . 24g3Annex A (informative): Change history . 25g3History 26g3ETSI ETSI TS 125 324 V15.0.0 (2018-07)53GPP TS 25.324 version 15.0.0 Rele
25、ase 15Foreword 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 and may change following formal TSG approval. Should the TSG modify the contents of the present docum
26、ent, 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 information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change contr
27、ol. 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 incorporated in the document. ETSI ETSI TS 125 324 V15.0.0 (2018-07)63GPP TS 25.324 version 15.0.0 Releas
28、e 151 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 The following documents contain provisions which, through reference in this text, constitute provisi
29、ons 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 do not apply. - For a non-specific reference, the latest version applies. In the case of a referen
30、ce 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 Protocol Specification“. 2 3GPP TS 25.301: “Radio Interface Protocol Architecture“. 3 3GPP TS 23.041
31、: “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 Interface for Broadcast/Multicast Services“. 7 TIA/EIA-41-D: “Technical realization of Cell Br
32、oadcast 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 terms and definitions apply. CB message: user data as transmitted from Cell Broadcast Centre to U
33、E (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 message. This number is infinite or finite DRX Schedule Period: schedule period as optionally r
34、equested 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 be set optionally by the CBC. CTCH Block Set: subset of the transport block set of FACH on whic
35、h 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 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AS Access Stratum BMC Broadcast/Multicast
36、Control ETSI ETSI TS 125 324 V15.0.0 (2018-07)73GPP TS 25.324 version 15.0.0 Release 15C-SAP Control Service Access Point CBC Cell Broadcast Centre CBS Cell Broadcast Service CTCH Common Traffic ChannelCTCH-BS CTCH Block Set FACH Forward Access Channel IE Information Elementkbps kilo-bits per second
37、 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 Protocol RLC Radio Link Control RRC Radio Resource Control UE User Equipment 4 General 4.1 Model
38、 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/multicast. Figure 4.1-1 shows the model of the L2/BMC sublayer within the UTRAN radio interface p
39、rotocol 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 sublayer. The BMC requests the Unacknowledged Mode service of the RLC. It is assumed that there
40、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 BMC protocol entity serves only those messages at BMC-SAP that are to be broadcast into a spec
41、ified cell. ETSI ETSI TS 125 324 V15.0.0 (2018-07)83GPP TS 25.324 version 15.0.0 Release 15L2/BMC sublayerRRCBMC-SAPuser-planeL2/RLC sublayerBMCRLCUMCTCH-SAPCBMC-SAPFigure 4.1-1: BMC protocol model 5 Functions The functions are specified in 2. They are: - Storage of Cell Broadcast Messages. - Traffi
42、c 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 to Upper Layers The BM-SAP provides a broadcast/multicast transmission service in the user plane
43、 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 and the RRC layer are specified in terms of primitives where the primitives represent the logical
44、 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 (SAPs). Three types of primitives are used for this document, as follows: - REQUEST: This type
45、is used when a higher layer is requesting a service from a lower layer. - INDICATION: This type is used by a lower layer providing a service to notify its higher layer of activities concerning that higher layer. ETSI ETSI TS 125 324 V15.0.0 (2018-07)93GPP TS 25.324 version 15.0.0 Release 15- CONFIRM
46、: 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 layer and BMC, as well as RRC and BMC in the same protocol stack. For the BMC sublayer two sets
47、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 Services expected from RLC The BMC uses the unacknowledged mode service of the RLC sublayer. Se
48、e 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. Table 8.1.1-1: Primitives between BMC and RRC Generic Name Parameters CBMC-Measurement-IND CB-
49、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. Primitive 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. Parameters: Action. DRX selection. ETSI ETSI TS 125 324 V15.
