ETSI TS 144 012-2016 Digital cellular telecommunications system (Phase 2+) Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface (V13 0 0 3GPP TS 44 01.pdf

《ETSI TS 144 012-2016 Digital cellular telecommunications system (Phase 2+) Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface (V13 0 0 3GPP TS 44 01.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 144 012-2016 Digital cellular telecommunications system (Phase 2+) Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface (V13 0 0 3GPP TS 44 01.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1Digital cellular telecoShort Message Ssupport on (3GPP TS 44.0TECHNICAL SPECIFICATION144 012 V13.0.0 (2016communications system (Phaervice Cell Broadcast (SMSn the mobile radio interface .012 version 13.0.0 Release 13GLOBAL SYSTEMOBILE COMMUN16-01) hase 2+); SCB) 13) TEM FOR ICATIONSRETSI

2、ETSI TS 144 012 V13.0.0 (2016-01)13GPP TS 44.012 version 13.0.0 Release 13Reference RTS/TSGG-0244012vd00 Keywords GSM 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

3、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 electronic and/or print versions of the presen

4、t 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 (PDF) version kept on a specific network driv

5、e 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/status.asp If you find errors in the present d

6、ocument, 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 photocopying and microfilm except as authorized by

7、 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 2016. All rights reserved. DECTTM, PLUGTESTSTM

8、, 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 registered and owned by the GSM Association. ETS

9、I ETSI TS 144 012 V13.0.0 (2016-01)23GPP TS 44.012 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 any, is publicly available for ETSI members

10、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 on the ETSI Web server (https:/ipr.etsi.org

11、/). 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 may be, or may become, essential to the pre

12、sent 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 identities. These should be interpreted as being re

13、ferences 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“, “should not“, “may“, “need not“, “will“, “will

14、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 TS 144 012 V13.0.0 (2016-01)33GPP TS 44.012

15、version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g31.1 References 5g31.2 Abbreviations . 5g32 General description. 5g32.1 Scheduling Information 6g33 Message format on BTS-MS Interface . 6g33.1 General . 6g33.2 Format c

16、onvention 7g33.2.1 Numbering convention . 7g33.2.2 Order of bit transmission 7g33.3 Block content 7g33.3.1 Block Type 7g33.4 SMSCB Message 8g33.5 Schedule Message 8g33.5.1 Header . 9g33.5.2 New CBSMS Message Bitmap . 9g33.5.3 New CBSMS Message Description 9g33.5.4 Other Message Descriptions . 10g33.

17、5.5 Message description encoding 10g33.5.5.1 First transmission of an SMSCB within the Schedule Period . 10g33.5.5.2 Retransmission indication . 11g33.5.5.3 Free Message Slot, optional reading . 11g33.5.5.4 Free Message Slot, reading advised 11g33.5.5.5 Reserved Codepoints . 11g3Annex A (informative

18、): Sample Implementation of SMSCB DRX Mode . 12g3Annex B (informative): Change History 14g3History 15g3ETSI ETSI TS 144 012 V13.0.0 (2016-01)43GPP TS 44.012 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents

19、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 date and an increase in version number as follows: V

20、ersion 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. technical enhancements, corrections, updates, etc. z the

21、 third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 144 012 V13.0.0 (2016-01)53GPP TS 44.012 version 13.0.0 Release 131 Scope 1.1 References The following documents contain provisions which, through reference in this text, constitute provision

22、s 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 reference to a

23、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 TR 21.905: “Vocabulary for 3GPP Specifications“. 2 Void. 3 3GPP TS 23.041: “Technical realization of Cell Broadcast Service

24、(CBS)“. 4 3GPP TS 44.004: “Layer 1; General requirements“. 5 3GPP TS 44.006: “Mobile Station - Base Station System (MS - BSS) interface Data Link (DL) layer specification“. 6 3GPP TS 45.002: “Multiplexing and multiple access on the radio path“. 1.2 Abbreviations For the purposes of the present docum

25、ent, the abbreviations given in 3GPP TR 21.905 apply. 2 General description SMSCB is a service in which short messages may be broadcast from a PLMN to Mobile Stations (MS)s. SMSCB messages come from different sources (e.g. traffic reports, weather reports). The source and subject of the SMSCB messag

26、e is identified by a message identifier in the SMSCB message header. A sequence number in the SMSCB message header enables the MS to determine when a new message from a given source is available. SMSCB messages are not acknowledged by the MS. Reception of SMSCB messages by the MS is only possible in

27、 idle mode. The geographical area over which each SMSCB message is transmitted is selected by the PLMN operator, by agreement with the provider of the information. A SMSCB message is an end-to-end message that is formatted by/for the SMSCB application, and which is intended for customer viewing. Its

28、 format is described in detail in 3GPP TS 23.041. A CB message is any message sent on the basic or extended CBCH (see 3GPP TS 45.002). It can be an occurrence of a SMSCB message, or a schedule message. ETSI ETSI TS 144 012 V13.0.0 (2016-01)63GPP TS 44.012 version 13.0.0 Release 13The SMS Cell Broadc

29、ast service is designed to minimize the battery usage requirements for a MS. A MS can read the first part of a CB message and then decide whether or not to read the rest of the message. In addition, the network may broadcast Schedule Messages, providing information in advance about the CB messages t

30、hat will be sent immediately afterwards. The MS may use this scheduling information to restrict reception to those messages the customer is interested in receiving. This SMSCB DRX feature is optional in the network and the MS. 2.1 Scheduling Information The network supporting the SMSCB DRX feature t

31、ransmits Schedule Messages. A Schedule Message includes information about a number of immediately following consecutive CB messages, planned for that cell. The length of time covered by the CB messages referred to in a Schedule Message is called the Schedule Period of that message. For optimum DRX,

32、a new Schedule Message should follow the last message of a Schedule Period. When no information is known about a CB message, e.g. because no Schedule Message has been received referring to that CB message, a MS shall read (at least) the first part of the CB message. Schedule Messages shall be sent o

33、n the basic and extended CBCH independently. The network may override the published schedule to transmit new high-priority SMSCB messages. However, after any schedule deviation, the network shall resume the schedule, by transmitting the scheduled CB messages at the scheduled times listed in the Sche

34、dule Message. The Schedule Message contains a Message Description for each CB message to be broadcast during the scheduling period, in order of transmission. The position of a CB message is called the “message slot number“ of the CB message, and it indicates the position of the CB message within the

35、 schedule period. Each Message Description includes various information, including for SMSCB messages directly or indirectly all or part of their message identifier, and whether an occurrence is a repetition or not. Each Schedule Message includes a Begin Slot Number field and an End Slot Number fiel

36、d. The End Slot Number field indicates the length of the schedule period (i.e. specifically the number of CB message slots about which information is provided). In the case where the network uses Schedule Messages to describe all message slots in advance, the first Schedule Message of the next sched

37、ule period will be transmitted in the message slot pointed by End Slot Number plus 1. The Begin Slot Number is defined to allow the network to broadcast several Schedule Messages referring to the same schedule period. The Begin Slot Number field indicates the message slot number of the CB message fo

38、llowing the received Schedule Message. The networks may send unscheduled Schedule Messages during empty message slots. The network need only update the Begin Slot Number in an unscheduled Schedule Message to reflect the current offset within the Schedule Message of the next message to be transmitted

39、. 3 Message format on BTS-MS Interface 3.1 General A CB message consists of a 88 octets of information. The 88 octet block is segmented into four 22 octet blocks. A 1 octet Block type is added as a header to each 22 octet block. The overall blocks are thus 23 octets in length. The message blocks are

40、 sent on the channel allocated as CBCH by 3GPP TS 45.002. The timing of the messages is defined in 3GPP TS 45.002. If the network has no cell broadcast information to transmit, then it may choose to transmit a null message. ETSI ETSI TS 144 012 V13.0.0 (2016-01)73GPP TS 44.012 version 13.0.0 Release

41、 133.2 Format convention 3.2.1 Numbering convention The basic convention used in this technical specification is illustrated in figure 1. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered

42、from 1 to 23. 8 7 6 5 4 3 2 1 Octet: 1 223Figure 1: Format convention 3.2.2 Order of bit transmission The message blocks are sent on the CBCH as defined in 3GPP TS 45.002 using the coding defined for that channel. The order of bit transmission is defined in 3GPP TS 44.004. 3.3 Block content The 23 o

43、ctet blocks are coded as follows. 8 7 6 5 4 3 2 1 Octet: Block type 1 2 Information 23 Figure 2: Block content 3.3.1 Block Type The purpose of the Block Type is to identify the function of the block and message being sent. The block type is coded as shown in figure 3. 8 7 6 5 4 3 2 1 Octet: Spare LP

44、D LB Sequence Number 1 0 0 1 Figure 3: Block type content Bits 8 is spare and set to zero by the sender. In order to allow compatibility with future modifications to this protocol, bits 8 shall be ignored by the receiver and messages shall not be rejected because it is set to one. The Link Protocol

45、Discriminator (LPD) takes the value “0 1“. Other values of LPD indicate other protocols which are outside the scope of the present document, and shall cause the message to be ignored when the Cell Broadcast LPD is expected instead. NOTE: LPD = “0 0“ corresponds to the data link protocol used by LAPD

46、m (see 3GPP TS 44.006). In an SMSCB message the last block containing SMSCB information is signalled by the Last Block (LB) bit. When the LB bit is set to “0“, the next block may contain SMSCB information. When the LB bit is set to “1“, the remaining block(s) do(es) not contain SMSCB information. ET

47、SI ETSI TS 144 012 V13.0.0 (2016-01)83GPP TS 44.012 version 13.0.0 Release 13Table 1: Sequence number coding Bit No 4 3 2 1 0 0 0 0 First block 0 0 0 1 Second block 0 0 1 0 Third block 0 0 1 1 Fourth block 1 0 0 0 First schedule block: Message contains SMSCB scheduling information 1 1 1 1 Null messa

48、ge (does not contain valid SMSCB information) All other values of bits 4 to 1 are reserved for future use. The use of a reserved code point shall cause the message to be ignored. 3.4 SMSCB Message The SMSCB message is a message with four consecutive blocks, with Block Types “first block“, “second bl

49、ock“, “third block“ and “fourth block“. A null message (which is indicated by the Sequence Number 1111 (binary) shall have octets 2 to 23, inclusive, filled with the value 2B (hex). The SMSCB message coding is defined in 3GPP TS 23.041. 3.5 Schedule Message The text of the Schedule Message provides information pertaining to the CB messages sent afterward. A Schedule Message consists of 4 consecutive blocks with Block Types “first schedule block“, “second block“, “third block“ and “fourth block“. A Schedule Message containing scheduling data which