handset requirements specification

7/29/2019 Handset Requirements specification

1/44

Cell Broadcast Forum

E-mail: [email protected] Internet: http://www.cellbroadcastforum.org/

CBF-PUB(02)2R3.2

Handset Requirements SpecificationMay 2009

Reaching Millionsin a Matter of Seconds

Issued by Cell Broadcast ForumDisclaimer

No part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.

The information in this document is subject to change without notice and should not be construed asa commitment by Cell Broadcast Forum. Cell Broadcast Forum assumes no responsibility for any errors

that may appear in this document.

Products mentioned in this document are identified by the trademarks or service marksof their respective companies or organisations.

2002-2009, Cell Broadcast Forum

All rights reserved


2/44

CBF-PUB(02)2R3.2

Handset Requirements Specification Page 2 13/05/2009

About Cell Broadcast Forum

The Cell Broadcast Forum (CBF) is a non-profit Industry

Association that supports the world standard for cell

broadcast wireless information and telephony services on

digital mobile phones and other wireless terminals. The

primary goal of the Cell Broadcast Forum is to bring

together companies from all segments of the wirelessindustry value chain to ensure product interoperability and

growth of wireless market.

The Forum's mission includes

Promotion of simple and easy-to-use, interoperableCell Broadcast service solutions,

Improving the technology and underlying standards

Maximizing business for the mobile and relatedindustry

Cell Broadcast Forum members represent the global

handset market, carriers that together serve more than 100

million customers, leading infrastructure providers,software developers and other organisations providing

solutions to the wireless industr .


3/44

CBF-PUB(02)2R3.2


ContentContent...................................................................................................................................... 3Foreword .................................................................................................................................... 5Preface ....................................................................................................................................... 71 Requirements ....................................................................................................................11

1.1 General requirements..............................................................................................111.2 Requirements on Display Mode...............................................................................131.3 Requirements on Geographical Scope .....................................................................151.4 Requirements on Message Code..............................................................................161.5 Requirements on Update Number ...........................................................................161.6 Requirements on Message Identifier........................................................................171.7 Requirements on Data Coding Scheme....................................................................181.8 Requirements on Page Parameter............................................................................191.9 Requirements on Storage of Cell Broadcast Messages..............................................191.10 Requirements on Handling of Emergency Messages ................................................20

2 Test Environment..............................................................................................................232.1 Introduction............................................................................................................232.2 Identification ..........................................................................................................232.3 Hardware Preparation.............................................................................................232.4 Software Preparation ..............................................................................................242.5 Other Pre-test Preparation .......................................................................................24

3 Test Cases .........................................................................................................................253.1 MMI .......................................................................................................................253.2

Display...................................................................................................................25

3.3 Alerts......................................................................................................................26


4/44

CBF-PUB(02)2R3.2


3.4 Services...................................................................................................................274 Score sheet........................................................................................................................295 Full Test Set......................................................................................................................35

5.1 General requirements..............................................................................................355.2 Requirements on display mode ...............................................................................375.3 Requirements on geographical scope ......................................................................385.4 Requirements on message code ..............................................................................385.5 Requirements on update number ............................................................................395.6 Requirements on message identifier ........................................................................395.7 Requirements on Data Coding Scheme....................................................................405.8 Requirements on page parameter ...........................................................................415.9 Requirements on Storage of messages.....................................................................415.10 Requirements on Handling of Emergency Messages ................................................42

Revision History........................................................................................................................43


5/44

CBF-PUB(02)2R3.2


ForewordIntensive validation tests of GSM mobile terminals have shown that there is a wide variety of different Cell

Broadcast implementations currently in the market.

This variety is the result of a missing 3GPP Technical Specification of the series 22.xxx. There are only two

specifications available: 3GPP TS 23.041 specifies e.g. how a Cell Broadcast message shall be coded and

3GPP TS 24.012 specifies how it is transferred over the air interface. There is no specification that tells how

a mobile station is to receive, display and store Cell Broadcast messages.

With that background the freedom of Cell Broadcast service creation is strongly limited. Hence the Cell

Broadcast Forum intends to reduce the variety of implementations by defining some basic requirements

with associated test cases, aiming to a homogeneous mobile terminal behaviour in the future.


6/44

CBF-PUB(02)2R3.2


This page is intentionally left blank.


7/44

CBF-PUB(02)2R3.2


PrefaceScope

This document reflects the Cell Broadcast Forums vision of a mobile terminal Cell Broadcast implementa-

tion.

The European Cooperation on Cell Broadcast project[1] has issued a draft Positioning Paper, which can bedownloaded from the project website. This Positioning Paper includes a number of requirements for mobile

terminals an dthese have been included in this document.

In September 2006, the WARN Act passed through the US Congress and the Commercial Mobile Alert

Service (CMAS) resulted from that. ATIS has specified CMAS via CB. Jointly with TIA the Mobile Device

Behaviour Specification was developed [2]. The requirements of this document have been taken into con-

sideration.

The document is divided into two parts. The first part specifies the requirements and the second part speci-

fies the associated test cases for each requirement.

AudienceThe reader is expected to be familiar with the specifications of 3GPP TS 23.038, 3GPP TS 23.041 and

3GPP TS 24.012.

This document intends to assist Mobile Station (MS) manufacturers to establish requirements for behaviour

and handling of Cell Broadcast messages, which can be used in the development of MSs.

References[1] European Cooperation on Cell Broadcast;

https://service.projectplace.com/pub/english.cgi/0/283748154

[2] J-STD-100, Mobile Device Behavior Specification, ATIS and TIA

Definitions and AbbreviationsATIS

BSC

Alliance of Telecommunications Industry Solutions

Base Station Controller

BTS Base Tranceiver Station

CB Cell Broadcast

CBC Cell Broadcast Centre

ICT F O R the E N V I R O N M E N T
https://service.projectplace.com/pub/english.cgi/0/283748154https://service.projectplace.com/pub/english.cgi/0/283748154https://service.projectplace.com/pub/english.cgi/0/283748154


8/44

CBF-PUB(02)2R3.2


CBCH Cell Broadcast CHannel

CBE Cell Broadcast Entity

CBMI Cell Broadcast Message Identifier

CI Cell Identifier

CR Carriage Return

DCS Data Coding Scheme

DRX Discontinous Reception

EF Elementary File

EMS Enhanced Messaging Service

FCC Federal Communications Commission

GPIB General Purpose Interface Bus

GPRS General Packet Radio Service

GS Geoscope

GSM Global System for Mobile communication

ISO International Standards Oranisation

LAC Local Area Code

LTE Long Term Evolution

MC Message Code

MI Message Identifier

MMI Man-Machine Interface

MMS Multi Media Service

MS Mobile Station

OTA Over-The-Air Activation

PLMN Public Land based Mobile Network

SIM Subscriber Identity Module

SMS-PP Short Message Service Point to Point

STD System Test Description


9/44

CBF-PUB(02)2R3.2


TE Terminal Equipment

TIA Telecommunications Industry Association

TS Technical Specification

UCS-2 Universal Character Set2 (bytes)

UMTS Universal Mobile Telecommunications System

UN Update Number

URL Universal Resource Locator

US United States

USSD Unstructured Supplementary Service Data

WAP Wireless Access Protocol

WARN Warning, Alert and Response Network

WML Website Meta Language

3GPP 3rd Generation Partnership Programme


10/44

CBF-PUB(02)2R3.2


This page is intentionally left blank.


11/44

CBF-PUB(02)2R3.2


1 Requirements1.1 General requirement s3GPP TS 23.041 is ambiguous as to the types of display. The way a message shall be displayed can be

controlled by the Geo Code (GS) and by the Data Coding Scheme (DCS). Unclear is which of these two

takes precedence.

The CB Forum proposes the following:

If the GS=0 (cell wide immediate display), then the message is unique in the current cell only and shall be

removed when the terminal is connected to another cell. Such a message shall be displayed in a single line

across the screen without any notification, and, if neccessary, the message shall scroll. It shall not be possi-

ble for the user to remove the message. This behaviour takes precedence over a Class specification through

the DCS.

Requirements (18) and (19) deal with Normal Display and Immediate Display.

1.1.1 Mandatory requirements1. Factory Settings: The factory setting of Cell Broadcast shall be set to "not active", i.e. no CB message

shall be received, neither on MI 0 (Index) nor on MI 50 (District Information), nor on any other Mes-

sage Identifier, even if the status of the Message Identifier is selected.

Refer to section 1.10 for requirements for handling of Emergency Warning Messages.

2. MS Off/On: The actual setting of Cell Broadcast ("active" or "not active") should not be affected by

turning the MS on / off, or if the battery is depleted or replaced.

3. Single CB menu: There shall be only one single CB (main-) menu within the SMS menu to control CellBroadcast at the MS. There shall be no separate menus, e.g. within the phone settings, for special

Message Identifiers, e.g. MI 50. All handsets shall apply a uniform naming of the Cell Broadcast menu.

It shall be possible to (de-)activate Cell Broadcast by a simple and straightforward action. Cell Broad-

cast activation and de-activation should not interfere with Message Identifier selection and de-

selection.

4. Reception tone: Reception of a Cell Broadcast message (with parameters that indicate the message is

to be presented on the display with Display Mode "normal") shall be indicated with a tone. The user

may have the possibility to choose between different tones, and be able to control the volume. The re-

ception tone for incoming point-to-point SMS and other acoustical signals must not be affected by the


12/44

CBF-PUB(02)2R3.2


setting of the reception tone for Cell Broadcast. Cell Broadcast messages with Display Mode "immedi-ate" shall be received and displayed without any tone.

Refer to section 1.10 for requirements for notification of Emergency Warning Messages.

5. Using phone numbers: It shall be possible to dial, and send Short Messages to, telephone numbers

that are contained within a Cell Broadcast message directly out of the message. If multiple numbers

are present in the message, this function shall be available for each of these numbers.

6. Using URLs: It shall be possible to access URLs (referring to e.g. WAP services) that are contained

within a Cell Broadcast message directly out of the message by activating the WAP browser on the

specified URL. If multiple URLs are present in the message, this function shall be available for each ofthese URL. (This feature is mandatory only for WAP terminals)

The Mobile Device Behavior Specification [2] does not allow the use of URLs after reception of a warn-

ing message, since it may lead to network congestion.

7. SIM data download: The MS shall be capable of receiving CB messages in the range of MI 1000 (hex)

- 10FF (hex) automatically (SIM Data Download). This mode of operation is controlled by the Elemen-

tary File CBMID (EFCBMID) on the SIM card. As soon as there is an activated CBMID field on SIM and

there are one or more Message Identifiers stored in this field, the MS shall scan the Cell Broadcast

channel (CBCH) for CB messages with that MI and receive them. Received SIM Data Download mes-

sages are to be passed directly to the SIM card.

8. DRX Scheduling: The MS shall support DRX mode (Scheduling), i.e. be capable of processing both,

scheduled and unscheduled schedule messages. High priority messages (Free message slot, reading

advised) shall be supported.

9. Reception by Terminal Equipment: It shall be possible to select any CB message type (MI) by terminal

equipment (TE) independently from the CB status in the MS. This is to prevent deactivating services

that are configured through the terminal equipment interface. To save battery power due to the scan-

ning of CB channels when not in use after disconnection of the terminal equipment the handsets

might deactivate scanning of the configured cell broadcast channels but storing the configuration and

list of message types. This would imply detection of terminal equipment by handsets.

10. CB and Access Network: Reception of Cell Broadcast messages shall not be affected by the Network

Mode of Operations. Reception shall be made possible regardless of the access network the MS is at-

tached to. This includes not only GSM, but also GPRS and UMTS.

Broadcast capability in LTE is to be included later.


13/44

CBF-PUB(02)2R3.2


1.1.2 Optional requirements11. CB Active: Despite of requirement 1 the possibility of delivering terminals with CB active" upon re-

quest of a network operator should be provided. This may be the case when a public warning service is

to be provided.

12. Special Message Identifiers: It should be possible to deliver terminals with at least five preconfigured

Message Identifiers that are to be defined by the operator. The individual status of each of these five

preconfigured Message Identifiers can be active or not active, as defined by the network operator.

This pre-configuration of Message Identifiers is independent from any settings on the SIM.

13. Submenu for MI 000: A submenu item for Message Identifier 000 ("Index") within the CB (main-)

menu should be provided. It must be possible to activate MIs by selecting items presented in the in-

dex.

14. WAP Push: It shall be possible to launch the WAP Browser of the WAP terminal by sending a CB mes-

sage. The CB message will contain WML content. The WAP Browser will be launched locally, without

establishing any connection, will interpret the WML content and displays it. When a user action is

taken, and a WAP connection has to be made, the WAP browser initiates a new WAP connection. (This

feature is optional only for WAP terminals, and requires standardization by appropriate bodies)

15. Using USSD strings: It shall be possible to open a USSD session directly by selecting a USSD string

contained in a Cell Broadcast message. This feature applies to USSD-enabled phones only.

16. Extended CBCH: The MS shall support the extended Cell Broadcast Channel.

17. EMS Support: The MS shall support EMS content over Cell broadcast in the same way as it supports

EMS content over SMS. The handset shall behave the same as for SMS when displaying the EMS con-

tent of the Cell Broadcast message.

1.2 Requirements on Display ModeThis section deals with the display of Cell Broadcast messages.

1.2.1 Mandatory requirements18. Normal Display: For each Message Identifier, the user specifies, through the menu, how Cell Broadcast

messages with display mode normal (Geographical Scope = 1, 2 or 3) are to be handled. Two set-

tings are supported:

Direct or Flash (class 0): the most recently received Cell Broadcast message for this Message Iden-

tifier is displayed across the entire screen without any user interaction.

Normal (class 1): the most recently received Cell Broadcast message shall be indicated to the user

by displaying an appropriate screen (e.g. "Message received show?"). The content of the mes-


14/44

CBF-PUB(02)2R3.2


sage shall be shown only after user interaction (e.g. by pressing a soft key "yes"). The user shallhave the possibility to reject the display of the message with a designated key (e.g. by pressing a

soft key "no", but not by clicking any key).

In both of the above cases the reception of a message shall be indicated by an alert tone. Refer to sec-

tion 1.10 in case CB is used in a public warning service.

After having read the message the user shall be offered the possibility to store or to delete the mes-

sage. If the user presses a key that it is neither a Yes for showing the message nor a No for deleting

it, the CB message should not be shown or deleted without explicit confirmation by the user (see also

handling of the Message Classes).

19. Immediate Display: Cell Broadcast messages with Display Mode "immediate" ( Geographical Code =

0) shall be displayed immediately in a single line within the idle display. It must be ensured that nei-

ther the operator name nor the idle display elements (signal level, battery status, and clock) will be

overwritten by an "immediate message". "Immediate messages" shall be displayed permanently, i.e.

they cannot be deleted by the user. The display is allowed to be changed only when the message

changes, i.e. a new "immediate message" is received, or when the MS leaves the Geographical Scope of

the message, i.e. reselects another serving cell (immediate display cell wide validity). The only way

to remove an "immediate message" from the display is to deactivate the belonging Message Identifier

or to deactivate CB reception generally.

This requirement is relevant for displaying for instance location information on MI=50.

20. Display Mode and Message Identifier: Evaluation of the Display Mode parameter shall be independent

of the Message Identifier that is coded within the message, i.e. even messages with Message Identifier

50 shall be processed according to the coded Display Mode and not be displayed immediately by de-

fault. "Immediate display" shall be possible on every channel between 001-999 and not be restricted

to Message Identifier 50. "Normal display" shall also be possible on every channel, even on the chan-

nel referenced by Message Identifier 50. It should be left to the operator / information provider

whether to use "immediate display" or "normal display".

21. Immediate Display and Message Identifier: Regarding the Display Mode "immediate" full-length mes-

sages (even multi-page) should be supported. A message that is short enough may be displayed per-

manently. A message that is too long to be permanently displayed should be scrollable, either manu-

ally or automatically. However the user should have the possibility of manual scrolling (e.g. after

automatic scrolling has finished).

22. No Deactivation by Selecting Default Menu Options: On reception of a Cell Broadcast Message, select-

ing the default options under the soft-keys in the Human Machine Interface shall never result in deac-

tivation of Cell Broadcast or any Cell Broadcast Message Identifiers.


15/44

CBF-PUB(02)2R3.2


1.3 Requirements on Geographical ScopeThis section deals with the reception and display of Cell Broadcast messages depending on the Geographi-

cal Scope that is coded within the message.

1.3.1 Mandatory requirements23. Boundary of Geographical Scope: For immediate display messages the following applies: if the MS

crosses the boundary of the Geographical Scope of a message (i.e. reselects another serving cell), the

message shall be cancelled from or replaced on the display.

24. New Message: The Geographical Scope is to be considered carefully when deciding if a received mes-sage is new or not. E.g. a mobile station receives two absolutely identical messages in two different

cells, i.e. the messages have the same parameter coding (Geographical Scope, Message Code, Update

Number, Message Identifier), but not necessarily the same content:

If the Geographical Scope is "cell wide", both messages are absolutely independent and have

presumably different contents. It happened by chance that all parameters are the same. After cell

reselection the MS shall discard the old message and receive the other message as "new".

If the Geographical Scope is "Location Area wide" and both cells belong to the same Location

Area, it is the same "known" message with the same content as received before. The MS shall dis-

card the second message and not give any reception tone.

If the two cells belong to different Location Areas the second message is to be regarded as "new".

If the Geographical Scope is "PLMN wide" and both cells belong to the same PLMN, it is the same

"known" message with the same content as received before. The MS shall discard the second mes-

sage and not give any reception tone.

Summary: it shall be prevented that the MS receives the same message multiple times and indicates each

reception with a tone! This applies at all times: independently from the operation the user had done (show,

store or delete) when the CB message was received for the first time and even if the handset has been

turned off and on again after receiving the message for the first time. The MC of a deleted message shall be

the stored for a reasonable cycle length.

25. No evaluation of Geo Scope for Class 3 messages: In case of CB messages with DCS class 3 (TE spe-

cific), the MS should not evaluate any Geographical Scope, but should pass to TE without exception.

26. Multi-page and Cell Reselection: If cell reselection occurs during reception of a multi-page message

the MS can decide by means of the Geographical Scope (and of course Message Identifier, Message

Code, Update Number, Page Parameter, as described above) whether single received message pages

belong to the same multi-page message or not. It should be possible for the MS to concatenate mes-sage pages received in different cells to one valid multi-page message.


16/44

CBF-PUB(02)2R3.2


1.4 Requirements on Message CodeThis section deals with the parameter Message Code coded within a Cell Broadcast message with Display

mode normal.

1.4.1 Mandatory requirements27. Number of Message Codes: The MS shall be capable of storing at least ten messages with different

Message Codes on the same channel (MI).

28. Handling of Message Codes: If there are further messages to be received (except class 2 or 3 mes-

sages) before the user has quit the currently displayed message, these further messages shall be re-ceived and stored in the background. After the user has quit the currently displayed message the next

one shall be displayed.

It must not happen that messages with the same MI and different Message Codes overwrite them-

selves mutually and are therefore not readable for the user.

29. No evaluation of Message Code For Class 3 Messages: In case of CB messages with DCS class 3 (TE

specific), the MS should not evaluate any Message Code, but should pass to TE without exception.

1.5 Requirements on Update NumberThis section deals with the Update Number coded within a Cell Broadcast message.

1.5.1 Mandatory requirements30. Update Number: An update of a Cell Broadcast message is indicated by a changed Update Number. If

the MS receives two Cell Broadcast messages A and B within the Geographical Scope of the messages

and with exactly identical parameters GS(A)=GS(B), Message_Code(A)=Message_Code(B),

MI(A)=MI(B) except the Update Number Update_Number(A)Update_Number(B), the MS shall inter-

pret message B as an update of message A, indicate reception and display the message as intended

by the Display Mode if Update_Number(A)< Update_Number(B)

31. Missed Messages : With respect to missed messages a message B with Update_Number(B) < Up-

date_Number(A) shall be regarded as a valid update of message A if the difference is more than 7,

just as a message B with Update_Number(B) > Update_Number(A) if the difference is less then 8.

That is because of the cyclic assignment of the 4 bit Update Number 0-15.

32. Equal Update Number: Messages with the same Update Number shall not be received repeatedly

because it is presumably the same message, provided that the parameter conditions mentioned above

are valid. In that case, if the 15 updates in between have been missed, the 16th

update of an older

message will not be received (but the 17

th

will).


17/44

CBF-PUB(02)2R3.2


33. No Evaluation of Update Number for Class 3 messages: In case of CB messages with DCS class 3 (TEspecific), the MS should not evaluate any Update Number, but should pass to TE without exception.

1.6 Requirements on Message IdentifierThis section deals with configuration, activation/deactivation and reception of Message Identifiers.

1.6.1 Mandatory requirements34. Reading Access to CBMI: The MS shall read Message Identifiers stored in the CBMI field on SIM and

present them to the user in the list of active Message Identifiers, i.e. Message Identifiers read from SIM

are by default to be set to status active in the MS. When CB reception is switched on at the MS, CB

messages with Message Identifiers that match the entries in the CBMI field on SIM shall be received

without further action.

35. Writing Access to CBMI: Message Identifiers that are entered to the MS via the keypad shall be stored

in a "MI configuration list in the MS. If a configured Message Identifier is set to "active, it shall also

be stored in CBMI field on SIM, i.e. the CBMI field on SIM represents a "MI activation list". The MS will

refrain from erasing from the SIM card any Message Identifier that were not written previously by the

MS itself, i.e. the MS will not remove any Message Identifier the SIM card was preloaded with, or that

was added later by means of an OTA procedure.

36. Number of Configuration Message Identifiers: It shall be possible to configure at least 10 different

Message Identifiers.

37. Number of Active Message Identifiers: The MS shall be capable of handling at least 5 active Message

Identifiers in parallel, so that reception of 5 different channels must be guaranteed.

38.Textual Description: It shall be possible to assign and modify a textual description to Message Identi-

fiers. The applicable textual description shall be displayed whenever a Cell Broadcast message is

brought to the display. Message identifier numbers above 999 that are present in the SIM card files

shall not be revealed to the user. Instead, an entry indicating a reserved channel is activated will be

displayed in the channel list.

39.Activation Status: It shall be possible to activate/deactivate Message Identifiers that are stored in the

list of configured/activated Message Identifiers. The status of activation/deactivation should be

graphically indicated to the user.

40. MI Range: The range of configurable Message Identifiers should be limited to 001 999. Message

Identifiers in the range of >= 1000 shall not be configurable through the handset Human Machine In-

terface. The handset shall not offer the user an option receive all topics allowing the reception of all

SMS-CB messages on air regardless of the MI they are broadcast on. This is particularly unacceptable if


18/44

CBF-PUB(02)2R3.2


such option implies that the handset will display even message identifiers above 999. MI = 0 is to bereserved for the Index Message and shall not be configurable for reception of regular messages.

41. OTA: It shall be possible to configure Message Identifiers using an OTA procedure, and messages that

are received with these Message Identifiers shall be received and processed immediately.

1.7 Requirements on Data Coding SchemeThis section deals with the Data Coding Scheme coded within a Cell Broadcast message.

1.7.1 Mandatory requirements42. Behaviour without Language Filter: If there is no user-configurable language filter, the MS should

display all Cell Broadcast messages with Data Coding Scheme "Default Alphabet" regardless of the

coded language. (Preferred languages on SIM or actual MMI language do not need to be handled

preferentially).

43. Behaviour with Language Filter: If there is a user-configurable language filter, the MS should display

only Cell Broadcast messages with Data Coding Scheme "Default Alphabet" and the desired language

and messages with language unspecified.

1.7.2 Optional requirements44.All Languages: If there is a user-configurable language filter, the MS should offer the possibility to

configure the filter to "all languages".

45. Class 0 Messages: Cell Broadcast messages with Data Coding Scheme "class 0" shall be treated as if

the message is a class 0 SMS message. For example, the message can be completely shown in the

whole display without user interaction and then the user is offered to show, store or delete it. This al-

lows a useful third Display Mode, specially taking into account that Display Mode immediate use is

restrictive.

46. Class 1 Messages: Cell Broadcast messages with Data Coding Scheme "class1" (0101 0101) shall be

handled by the MS as specified in the Annex.

47. UCS-2: The MS shall correctly display a Cell Broadcast message in UCS-2 format, if the Data Coding

Scheme indicates UCS-2 format and the language indicated in the first two bytes of the UCS-2 mes-

sage body is enabled in the handset.

48. Language encoding: The MS shall support a language filter when the DCS language encoding (0001

0000) is used in combination with a language identifier where the first three characters of the mes-

sage are a two-character representation of the language encoded according to ISO 639, followed by a

CR character.


19/44

CBF-PUB(02)2R3.2


1.8 Requirements on Page ParameterThis section deals with the Page Parameter coded within a Cell Broadcast message.

1.8.1 Mandatory requirements49. Multi-page Messages: The MS shall be capable of receiving multi-page messages. Up to 15 message

pages can be received and, after final reception of the last page, be displayed as one entire multi-page

message with a single notification to the user.

50. Multi-page and Cell Reselection: It should be possible for the MS to concatenate message pages re-

ceived in different cells to one valid multi-page message.

51. Combination of Different Multi-page Messages: It must not happen that pages of equally coded multi-

page messages received in different cells are combined, if the Geographical Scope indicates only cell

wide validity.

52. Interrupted Multi-page Messages: The MS shall receive multi-page messages even though the trans-

mission order is interrupted by other messages, e.g. transmission order:

message 1 page 1/3;

message 1 page 2/3;

message 2 page 1/2;

message 2 page 2/2;

message 1 page 3/3;

1.9 Requirements on Storage of Cell Broadcast MessagesThis section deals with the storage of Cell Broadcast messages within the MS.

1.9.1 Mandatory Requirements53. Number of Pages to Store: The MS shall be able to store at least 100 Cell Broadcast message pages in

volatile memory and at least 50 Cell Broadcast message pages in permanent memory.

54. Memory Allocation: The volatile and permanent memory space shall be dynamically allocated to the

received messages independently of any Message Identifiers and Message Codes (MC).

There shall be no restrictions to the Message Identifier, i.e. it shall be possible to store messages with

different Message Codes received on any active channel (at least 5 different MIs) in volatile as well as

in permanent memory.

There shall be no restrictions to the Message Code, i.e. it shall be possible to store at least as many

messages with as many different Message Codes received on the same channel as allowed by volatile


20/44

CBF-PUB(02)2R3.2


(permanent) memory availability.Below an example for volatile memory:

100 pages = 5 MIs x 10 MCs x 2 pages

100 pages = 2 MIs x 5 MCs x 10 pages

100 pages = 2 MIs x 3 MCs x 5 + 1 MI x 10 MCs x 3 + 2 MI x 5 MCs x 4 pages

55. Overwriting Volatile Memory Case: Messages stored in the volatile memory shall automatically be

overwritten by newly received messages, if the received message is an update of a message stored in

volatile memory. Otherwise a newly received Cell Broadcast message shall not overwrite the volatile

memory. A notification shall be displayed to the user; if not enough volatile memory space is available.

56. Permanent Storage While MS off/on: Messages stored in memory shall not be deleted when power

on/off the MS.

57. Deleting a message: It shall not be possible to accidentally delete a message by clicking any key.

58. Handling of Stored Messages in Permanent Memory: Messages stored in the permanent memory shall

not be overwritten by newly received messages. It shall be left to the user to organise the permanent

memory. As described above, a notification shall be displayed to the user; if not enough permanent

memory space is available.

59. Stored Messages Grouped by MI: Stored Messages shall be grouped by Message Identifier.

1.10Requirements on Handling of Emergency MessagesThis section deals with the handling by the MS when an emergency warning message is received. This

section does not so much provide the Cell Broadcast Forums view on handling of Emergency Warning

Messages, but states the requirements of the European Cooperation on Cell Broadcast project[1], that may

become applicable throughout the EU in due time.

1.10.1Mandatory Requirements60. Factory setting: In a country where a public warning service over Cell Broadcast is operational, the

government, or the operators may require that the default Factory Setting be set to active, i.e. CB mes-

sages can be received and the Message Identifier that has been assigned to the public warning service

be selected.

61. Reception tone: The MS shall indicate the reception of an emergency message by playing a ring tone

that is specific for emergency messages and cannot be allocated to other services on the MS. This ring

tone shall be activated even if the MS setting is set to silent mode, meeting mode, buzzing mode, etc.,

and also regardless of the Display Mode (Normal or Direct).

62. Storage: Emergency messages shall always be stored in volatile memory, so they can be recalled later.


21/44

CBF-PUB(02)2R3.2


63. Priority: Displaying the emergency message shall take priority over other mobile device functionas,with the exception that receiving and displaying emergency messages shall not preempt active data

and voice sessions.

64. Forwarding: MEs shall not support capabilities to forward or reply to emergency messages.

1.10.2CMAS Requirement sThe mobile device Behavior Specification [2] for CMAS provides a number of requirements for CMAS capa-

ble MEs. Some are CMAS (and therefore US) specific arnd are not included here, such as the specification

of the audio attention signal and the vibrator cadence. Others have been included in this document.


22/44


23/44

CBF-PUB(02)2R3.2


2 Test Environment2.1 IntroductionPart II of this document provides test cases to qualify each of the requirements as specified in part I of this

document.

2.2 IdentificationThe test procedure, as described in this document, has been developed by LogicaCMG

1; hence, Logi-

caCMGs Cell Broadcast Centre is used for convenience. The test cases can also be developed on the laptop

(seeFigure 1).

Figure 1 System Overview

2.3 Hardware PreparationThe hardware used in the test environment is

The Racal Instruments 6103 Digital Radio Test Set.

This set is capable of sending SMS-PP and SMS-CB messages over the air interface towards the mo-

bile(s) under test.

1LogicaCMGs Telecom Products division now trades under the name Acision. Acisions Cell Broadcast Centre is theresponsibility of one2many, a spin-off from Acision.


24/44


25/44

CBF-PUB(02)2R3.2


3 Test CasesThis chapter contains the standard set of test cases as suggested by the Cell Broadcast Forum. Phones

should comply with all tests.

3.1 MMI3.1.1 Simple Menu structu reCheck if there is only one menu for Cell broadcast menu within the SMS menu. Go to the SMS or messages

menu and check if the Cell broadcast menu is located there.

Check the naming of the Cell Broadcast option if it includes broadcast, regional or area.

3.1.2 Text ual description of MIsConfigure (and activate) an MI with a textual description. Check if it is possible to select the service from a

list of predefined services.

Send a message to this MI with a PLMN wide geoscope, and verify that upon reception the textual descrip-

tion is shown.

3.1.3 Activ ation/Deactivation of MIsCheck if the Cell Broadcast Menu if this MI can be deactivated without removing the item entirely. In this

(de)activation menu, the textual description of configured MIs is presented, possibly with numerical indica-

tion. The activation status is shown graphically.

3.2 Display3.2.1 Normal DisplayConfigure and activate MI 1 and 50 (if needed). Send an approx 90-character message to both MIs with

GS PLMN Wide. Both messages are indicated as received, but not shown directly. Only after a key press, the

message is shown. The message can be read without scrolling too much, with at least four lines of text

available.


26/44

CBF-PUB(02)2R3.2


3.2.2 Direct DisplayConfigure and activate MI 1 and 50 (if needed). Send a message containing at least 50 characters to both

MIs with GS direct display. Both messages are shown directly without a key press, scrolling in the main

screen. It is possible to restart scrolling by pressing a user key.

3.2.3 Class 0Configure and activate MI 1 (if needed). Send a message containing this MI with DCS 80 (decimal). The

(first part of) the message is shown directly without a key press full screen.

3.2.4 15 pagesConfigure and activate MI 1 (if needed). Send a message containing this MI with 15 pages of text to this

MI. The mobile shows the entire message. No indication is given before the entire message is received.

3.3 Alerts3.3.1 Separate beep from SMSCheck the CB or profile menu. There is a special tone setting for CB separate from the SMS tone. This tone

can also be set to off. Verify both settings by sending a message with a Normal Display ge oscope.

3.3.2 Vibration AlertIf vibration alert is selected, reception of a CB message will cause the telephone to vibrate.

3.3.3 Correct handling of update numbersConfigure and activate (if needed) MI 1 and send a message with GS normal display and update number 1

to this MI. Put the update number in this (and every following) message and keep message code and GS

the same. This message should be indicated as a new message. Now send a new message with update

number 2. This one is received as a new message. Send another message with update number 2. This one

is not indicated. The next message will have update number one. Also this one should not be received. Now

send a message with update number 3, which will be indicated as a new message. The next message is

send with update number 12, which is an increase of more than 8, so the mobile will have to recognise it

as an old message and discard it. The last message has update number 9, the increase (compared to 3, the

last received message) is 6 so the mobile will show it.

3.3.4 Correct handling of geoscopeConfigure and activate (if needed) MI 1 and send a message with GS PLMN Wide to this MI. The message

is received. Now let the handset handover to another BTS with different LAC with a running message with


27/44

CBF-PUB(02)2R3.2


exactly the same parameters, or change the LAC of the BTS and see that the message is not indicated as anew message. Repeat this for a CI change.

Configure and activate (if needed) MI 1 and send a message with GS LAC wide to this MI. The message is

received. Let the handset handover to another BTS with same LAC with a running message with exactly the

same parameters, or change the CI of the BTS and see that the message is not indicated as a new message.

Now let the handset handover to another BTS with different LAC with a running message with exactly the

same parameters, or change the LAC of the BTS and see that the message is now indicated as a new mes-

sage.

Configure and activate (if needed) MI 1 and send a message with GS Cell Wide to this MI. The message is

received. Now let the handset handover to another BTS with a running message with exactly the same

parameters, or change the CI of the BTS and see that the message is again indicated as a new message.

3.3.5 Multiple message codes on the same MIConfigure and activate (if needed) MI 1 and send 2 simultaneous messages with GS normal display and

different message codes containing unique messages to this MI. Display the message on reception of the

first message. The subsequent message does not overwrite the first one. After reception of both, cancel the

first message from the display. Now the second one should be displayed. After reading both messages no

new indications will appear. Now change the first message, with update number +1 and it will be indicatedagain. Repeat this for the second message.

3.4 Services3.4.1 Number of configurable/Activ e MIsTry to configure 10 MIs. At least five must be active.

3.4.2 Index MessageActivate the reception of index messages en send an index message to the phone. The index message is

received and using the cursor (or alike) buttons the topics can be selected. One key press will configure and

activate the topic.

3.4.3 CBMI Field on SIM is r eadInsert a SIM with 5 MIs, 1 to 5, stored in the CBMI field in the phone. These MIs can be written to the SIM

using OTA, a simcard reader/writer or a phone, from which it is known that it stores its active MIs on the

SIM. Now check if Cell broadcast reception is switched to on, and send a message to all five MIs. They all

are received. It is also possible to check the status of the MIs using the CB menu on the phone.


28/44

CBF-PUB(02)2R3.2


3.4.4 MIs>999 not manually configurableTry to configure MI 1000 (decimal) and 60000(decimal). Both entries will not be allowed.

3.4.5 SIM data downloadInsert a SIM with a SIM Toolkit application. Send a Class 2 message on the channel monitored. The appli-

cation receives the data correctly.

3.4.6 Use NumberConfigure and activate (if needed) MI 1 and send a message with GS normal display to this MI containing

one phone number. After showing the message there is a possibility to use the number for calling (sending

an SMS/MMS/E-mail) by using an option menu or selecting the number.

Configure and activate (if needed) MI 1 and send a message with GS normal display to this MI containing

three phone numbers. After showing the message there is a possibility to choose all numbers for calling

(sending an SMS/MMS/E-mail) by using an option menu or selecting the numbers.


29/44

CBF-PUB(02)2R3.2


4 Score sheetThis chapter contains an example score card, where the test results of each handset can be scored. Bottom

line, each handset gets a score between 0 and 5 (fully compliant), which makes comparing handsets easier.

Cell Broadcast Test Sheet

Handset brand and type xxxxx

Software version Vx.x

MMI

Simple menu structure

In SMS or messaging menu: 3 points 0

Broadcast in menu description 2 points

OR Area/regional in menu description 1 point 0

Textual Description of MIs

Freely configurable: 2 points 0

automatically assigned from MoU SE15: 1 point 0

Shown upon reception: 2 points 0

Activation/Deactivation of MIs

Possible: 3 points 0

Graphically shown: 2 points 0


30/44

CBF-PUB(02)2R3.2


Average for MMI 0

Display

Normal Display

Message is shown full screen: 3 points 0

Message is shown after key press: 1

point 0

Hi Res display, at least 4 lines: 1 point 0

Immediate Display

Immediate display on GS: 4 points. (2 for always IM) 0

Manual scroll possible: 1 point 0

Class 0 messages

If possible 5 points, if not 2 points 0

15 pages

If possible: 4 points 0

No early notification: 1 point 0

Avarage for Display 0

New message alerts

Separate beep from SMS

Other tone selectable: 3 points 0

Tone on/off: two points 0


31/44


32/44

CBF-PUB(02)2R3.2


Index message


CBMI Field on SIM is read


MIs >999 not configurable manually

Not possible: 5 points 0

SIM Data Download possible

If possible: 5 points

Use Number

One number: 3 points 0

More numbers: 2 points 0

Average for Services 0

Total 0

Extras

1. Permanent storage of messages (archive)

2. EMS (cannot be tested yet)

3. WAP Push (cannot be tested yet)

4. Language filter

5. Use URL


33/44

CBF-PUB(02)2R3.2


Results MMI Display Alerts

-- -- --

Services Total Extra's

-- -- 0


34/44


35/44

CBF-PUB(02)2R3.2


5 Full Test SetThis chapter contains all test cases to test compliance with the handset requirements, as described in part I

of this document.

All test cases are numbered according to the paragraph numbering used in the handset requirements sec-

tion. Not all requirements are covered with a unique test. Some tests cover several requirements, or parts of

requirements. In case in a test the GS normal display is mentioned, it does not matter whether a Cell-, LAC-

or PLMN-wide message is used.

5.1 General requirement s1. Check on a new phone if the cell broadcast service is set to off, and not to index or 000.

Send an index message and it is not displayed.

Check on a new phone if region info is not enabled.

Send a message on MI 50, it is not displayed.

Check on a new phone that no message at all is received.

To do so, inspect the cell broadcast service menu to make sure that it is set to off.

2. Check if a power cycle does not replace the cell broadcast settings.

Activate MIs 10 and 50 and switch Cell broadcast to on. Switch the phone off and on, and send a

message to both activated MIs. Both messages are received correctly.

Check if a battery replacement does not replace the cell broadcast settings.

Activate MIs 1 and 50 and switch Cell broadcast to on. Remove the battery, put it back on and switch

on the phone, and send a message to both activated MIs. Both messages are received correctly.

3. Check if there is only one menu for Cell broadcast menu within the SMS menu.

Go to the SMS or messages menu and check if the Cell broadcast menu is located there.

Check the other menus like phone settings for Cell broadcast related items.

There is no menu item for region or cell info, or any other cell broadcast related menu item.

Check if the MI settings are affected by switching on and off the Cell Broadcast reception.

Configure and activate MI 1, configure and deactivate MI 2. Set Cell Broadcast reception to on, then

off and on again. MI 1 is still activated and MI 2 is still deactivated. In case it is not possible to con-

figure deactivated topics, only use MI 1.

The naming issue cannot be tested as uniform and simple naming is too subjective.


36/44

CBF-PUB(02)2R3.2


4. Check the CB or profile menu.There is a special tone setting for CB separate from the SMS menu.

Check the CB or profile menu.

The reception tone for CB can be set to off.

Configure the phone to give a tone at reception of a CB message.

Configure and activate (if needed) MI 1 and send a message with GS direct display to this MI. No tone

is heard at reception of the message.

Configure and activate (if needed) MI 1 and send a message with GS normal display to this MI. Op-

tions to show, delete and store are offered. Delete can also be a Clear, Back or Cancel key press.

Configure and activate (if needed) MI 1 and send a message with GS normal display to this MI.

Select show to display the message. Options to delete and store are offered. Delete can also be a

Clear, Cancel, Back or alike key press. Store may also be reached via an o ptions menu.

Configure and activate (if needed) MI 1 and send a message with GS normal display to this MI.

Store the message. Repeat this until the memory is full. A notification is received that the memory is

full.

5. Configure and activate (if needed) MI 1 and send a message with GS normal display to this MI con-

taining one phone number.

After showing the message there is possible to use the number for calling or SMS-ing by using an op-

tion menu or selecting the number.

Configure and activate (if needed) MI 1 and send a message with GS normal display to this MI con-

taining three phone numbers.

After showing the message there is possible to choose all numbers for calling or SMS-ing by using an

option menu or selecting the numbers.


taining one URL.

After showing the message there is possible to start the WAP browser using the URL by using an op-

tion menu or selecting the URL.

Configure and activate (if needed) MI 1 and send a message with GS normal display to this MI con-

taining three URLs.

After showing the message there is possible to start the WAP browser using all URLs by using an op-

tion menu or selecting the URLs.

7. Cannot be tested yet.



37/44

CBF-PUB(02)2R3.2




11. Cannot be tested (if network operator unknown)

12. Cannot be tested (if network operator unknown)

13. Check the CB menu to find a special menu item for the index message.

Activate the reception of index messages en send an index message to the phone.

The index message is received and using the cursor (or alike) buttons the topics can be selected. One

key press will configure and activate the topic.


taining WML content.

This content is displayed correctly. The phone does not make a connection to a WAP gateway.

15. Cannot be tested.



taining EMS content using the correct DCS.

The phone displays the EMS content correctly.

5.2 Requirements on display mode18. Check the topic settings to find that for every MI the foreground or background mode can be set.

Configure and activate MI 1 and 2, using foreground mode for 1 and background for 2. Send a mes-

sage with GS normal display to both MIs and only MI 1 is shown. MI 2 can be read via the CB menu

options.

19. Configure and activate MI 1.

Send a message containing 93 characters to this MI with GS direct display. The entire message is

shown on the display without a key press. If the message is too long it will scroll. It is possible to

manually scroll, or re-scroll. The message does not overwrite the operator name, status indicators like

signal- and battery strength. The message cannot be deleted by the user any other way than by deac-

tivating the topic.

20. Configure and activate MI 1 and 50.

Send a message to both MIs with GS normal display. Both messages are indicated as received, but not

shown directly.


38/44

CBF-PUB(02)2R3.2


21. Configure and activate MI 1 and 50.Send a message to both MIs with GS direct display. Both messages are shown directly without a key

press.

22. Configure and activate (if needed) MI 1 and send a message with GS normal display to this MI.

It is not possible to directly disable CB reception nor deactivating the topic with a single key press.

5.3 Requirements on geographical scope23. Configure and activate (if needed) MI 1 and send a message with GS direct display to this MI.

The message is shown directly. Now let the handset handover to another BTS without a running mes-

sage, or delete the message and change the CI of the BTS and see that the message is cancelled from

the display.

24. Configure and activate (if needed) MI 1 and send a message with GS Cell Wide to this MI.

The message is received. Now let the handset handover to another BTS with a running message with

exactly the same parameters, or change the CI of the BTS and see that the message is again indicated

as a new message.

Configure and activate (if needed) MI 1 and send a message with GS LAC wide to this MI.

The message is received. Let the handset handover to another BTS with same LAC with a running mes-

sage with exactly the same parameters, or change the CI of the BTS and see that the message is not

indicated as a new message.

Now the handset handover to another BTS with different LAC with a running message with exactly the

same parameters, or change the LAC of the BTS and see that the message is again indicated as a new

message.

Configure and activate (if needed) MI 1 and send a message with GS PLMN Wide to this MI.

The message is received. Now let the handset handover to another BTS with different LAC and CI, with

a running message with exactly the same parameters, or change the CI and LAC of the BTS and see

that the message is not indicated as a new message.



5.4 Requirements on message code27. Configure and activate (if needed) MI 1 and send 10 subsequent message with GS normal display and

different message codes containing unique messages to this MI.

Display the message on reception of the first message. No subsequent messages overwrite the first

one. After reception of all 10 messages, cancel the first message from the display. Now the second one


39/44

CBF-PUB(02)2R3.2


should be displayed. Cancel this one to show the next. Repeat this until all messages are shown. Nowresend all 10 messages with exactly the same parameters. No one should be indicated as a new one.

28. Configure and activate (if needed) MI 1 and send 1 message with GS normal display

Display the message on reception of the this message. Send a second message on this MI with a dif-

ferent message code containing a unique message to this MI, while the first message is still being dis-

played.

The second message shall be received in the background and shall not overwrite the first message.


5.5 Requirements on update number30. Configure and activate (if needed) MI 1 and send a message with GS normal display and update

number 1 to this MI.

Put the update number in this (and every following) message and keep message code and GS the

same. This message should be indicated as a new message. Now send a new message with update

number 2. This one is received as a new message. Send another message with update number 2. This

one is not indicated. The next message will have update number one. Also this one should not be re-

ceived. Now send a message with update number 3, which will be indicated as a new message. The

last message is send with update number 12, which is an increase of more than 8, so the mobile will

have recognise it as an old message and discard it.


32.Test performed implicitely in test 30.


5.6 Requirements on message identifier34. Insert a SIM with 5 MIs, 1 to 5, stored in the CBMI field in the phone. These MIs can be written to the

SIM using OTA, a simcard reader/writer or a phone, from which it is known that it stores its active MIs

on the SIM.

Now check if Cell broadcast reception is switched to on, and send a message to all five MIs. They all

are received. It is also possible to check the status of the MIs using the CB menu on the phone.

35. Change the active MIs from the previous test case to 6 10.

Now put the SIM in a SIM card reader to check the CBMI field, or put it in a phone which passed the

previous test case and check if MIs 6 to 10 are active by sending messages to this phone, or by check-

ing the CB Menu.

36. Configure more than10 MIs in the phone, they do not have to be active.


40/44

CBF-PUB(02)2R3.2


37. Configure 10 MIs in the phone, and activate 5 of them.

38. Configure MI 1 in the phone. Give it a descriptive textsuch as test.

Send a message to the phone and see if the name test is added when the message is shown.

39. Configure (and activate) an MI with a textual description.

Check if the Cell Broadcast Menu if this MI can be deactivated without removing the item entirely. In

this (de)activation menu, the textual description of configured MIs is presented, possibly with numeri-

cal indication, the activation status is shown graphically. Modify the textual description afterwards.

40.Try to configure MI 1000 (decimal) and 60000(decimal).

Both entries will not be allowed.


5.7 Requirements on Data Coding Scheme42. If there is a language filter, set it to all languages if possible.

If you can only select a few languages, this test is not applicable. If there is no filter, no action is re-

quired. Send messages with DCS 0, 1, 5 and 15 (language unspecified). All messages are received cor-

rectly.

43. Configure the language filter to receive only messages with DCS 1 (English).

Send messages with DCS 0 (German), 1 (English) and 15(Language unspecified). The message with

DCS 0 will be blocked.

44. If there is a language filter, set it to all languages.

45. Configure (and activate) MI 1. Send a message with DCS 80 (decimal) on MI 1.

The message will be displayed entirely without a key-press.

46. Configure (and activate) MI 1. Send a message with DCS 81 (decimal) on MI 1.

The message will be displayed as a direct display message.

47. Configure (and activate) MI 1. Send an UCS2 message with language indication (DCS 17) and one

without language indication (DCS 72) on MI 1.

Both are to be displayed correctly.

Configure (and activate) MI 1. Configure the mobile to receive messages with a supported UCS2 lan-

guage.

Send an UCS2 message with language indication (DCS 17) specifying the configured language on MI

1. This message is received. Now send another UCS2 message with another language indicated on MI

1. This message is not indicated.


41/44

CBF-PUB(02)2R3.2


48. Configure the language filter to receive only messages with DCS 1 (English).Send 2 messages with DCS 0001000 (bin) and a text that starts with EN in the first message

and DE in the second message.

Only the first message is displayed.

5.8 Requirements on page parameter49. Configure (and activate) MI 1. Send a fifteen-page message on this MI.

The message is indicated once by the mobile and displayed entirely.




5.9 Requirements on Storage of messages53. Configure (and activate) MI 1 to 5. Send on every MI 4 messages containing 10 pages with different

message codes. Do not display any message until all messages have been sent.

Read and store 10 messages and read the remaining 10.

54.Tested implicitely with the previous test

55. Configure (and activate) MI 1. Send 1 message on this MI. After reception of the message, send an

updated message on this MI.

Afdter recalling all messages, the memory only contains the updated message, not the original mes-

sage.

56. Configure (and activate) MI 1. Send 10 messages on this MI. After reception of each message, store

them.

Power the mobile off and on. All messages can be recalled.

57. Configure (and activate) MI 1. Send 1 message on this MI. After reception of the message, click any

key, apart from the soft keys. The message is not deleted.

58. Configure (and activate) MI 1. Send 1 message on this MI. After reception of the message, store it.

Send an updated message, read it, and store it.

Both messages can be recalled from memory.

59. Configure (and activate) MI 1 to 5. Send on every MI 2 messages containing 10 pages with different

message codes. Do not display any message until all messages have been sent.

Read and store all messages and when reading the messages again from memory, they are grouped

by MI.


42/44


43/44

CBF-PUB(02)2R3.2


Revision Histor yThis Document is a joint effort of various individuals active in a Cell Broadcast Forum Working Group. Every

Full Member of the Cell Broadcast Forum can delegate participants to the Working Group and is welcome

to contribute. See the Cell Broadcast Forum Web Sitehttp://www.cellbroadcastforum.orgfor details of

membership and its benefits.

Revision Date Author CommentDraft 1.0 21/01/2000 Mathias Burger First revision

Draft 1.1 08/02/2000 Mathias Burger Comments from Walter Kokert, Head of CBCproject in T-Mobile Germany

Version 1.0 08/02/2000 Mathias Burger Requirements from Reimund Meierl, Head of CBSproject;

Requirements from Klaus Daffner, Head of De-

partment "Product Marketing Mobile Terminals"

Version 1.1 13/07/2000 Mathias Burger Time schedule and priorities adapted

Version 1.2 17/07/2000 Mathias Burger Minor completions made

Version 1.3 21/07/2000 Mathias Burger Minor changes made

Version 1.4 18/09/2000 Mathias Burger Editorial changes

Version 1.5 29/12/2000 Tom Veldman Added comments resulting from discussion in CellBroadcast Forum; Editorial changes

Version 1.6 20/02/2001 Tom Veldman Changes based on ad-hoc expert group meeting

on 13 February.

Version 1.7 02/05/2001 Tom Veldman Enhanced requirements on handling of messagesdirected at TE and on storage requirements, de-pendent on Message Class (Annex A).

Version 1.8 03/10/2001 Chehwan Pierre Editorial changes and presentation

EMS support

Version 1.9 03/10/2001 Chehwan Pierre Using phone numbers in mandatory requirements

Using URLs in mandatory requirements

Replacement of Time schedule and priorities by

only priorities (Mandatory, Optional)
http://www.cellbroadcastforum.org/http://www.cellbroadcastforum.org/http://www.cellbroadcastforum.org/http://www.cellbroadcastforum.org/


44/44

CBF-PUB(02)2R3.2

Revision Date Author CommentVersion 2.0 18/12/2001 Heinz Ochsner Final lay outing and proof reading

Version 2.1 06/02/2002 Heinz Ochsner Resolving Inconsistencies

Version 2.2 28/05/2002 ISWG Resolving Inconsistencies in definitions

Version 2.3 27/04/2005 Peter Sanders Added DCS for emergency use

Versions 2.4-3.0 16/09/2006 Peter Sanders Added section on emergency messages

Version 3.1 1/11/2007 Peter Sanders Merged Test Cases document

Version 3.2 13/05/2009 Peter Sanders Added Public Warning requirements

handset requirements specification

Documents