<?xml version="1.0" encoding="utf-8" standalone="yes"?><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Cell Broadcast</title>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
<meta content="text/css" http-equiv="Content-Style-Type" />
<script src="NED?action=retrieve&amp;identifier=dn00188761&amp;edition=1&amp;language=none&amp;coverage=global&amp;encoding=javascript&amp;component=data&amp;item=data" type="text/javascript" xml:space="preserve">
</script>
<?conversion name="Pub2XHTML" version="2.0" source="urn:mars:dn0449737:1:en:global:publishing_online_1_0:data:data:*:*:*" date="2005-02-28T16:18:52Z"?>
<link href="NED?action=retrieve&amp;identifier=dn01158124&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=css&amp;component=data&amp;item=data" rel="stylesheet" title="Nokia Networks default online style" type="text/css" />
<meta content="draft" name="status" />
<?conversion name="SplitHTML" version="1.9" source="urn:mars:dn0449737:1:en:global:publishing_online_1_0:data:data:35:*:*" date="2005-02-28T16:18:52Z"?>
</head>
<body lang="en" xml:lang="en">
<p><a name="ned_top" shape="rect"></a>
<a name="ned_1" shape="rect"></a></p>

<a name="jan1851430852" shape="rect"></a>
<a name="p2xhtm-repid-1" shape="rect"></a>
<table width="100%">
<tr>
<td align="center" colspan="1" rowspan="1" width="20%"><?NED5 annotation?>
<br clear="none" /><?NED5 printview?>
</td>
<td align="center" colspan="1" rowspan="1" width="20%"></td>
<td align="center" colspan="1" rowspan="1" width="20%"></td>
<td align="center" colspan="1" rowspan="1" width="20%"></td>
<td align="center" colspan="1" rowspan="1" width="20%"><a href="NED?action=retrieve&amp;identifier=dn0449737_about&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_top#ned_top" onclick="openSmallPopup(event,'NED?action=retrieve&amp;identifier=dn0449737_about&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=xhtml_1_0&amp;component=data&amp;item=data&amp;pointer=ned_top#ned_top');return false" shape="rect" target="_blank"><img alt="Document information" border="0" class="Metainfo" src="NED?action=retrieve&amp;identifier=dn01158003&amp;edition=1&amp;language=en&amp;coverage=global&amp;encoding=gif&amp;component=data&amp;item=data" /></a></td>
</tr>
</table>


<div class="div">
<h1>Cell Broadcast</h1>

<p>Short textual messages can be broadcasted to all GSM mobile
stations in a specified area.</p>


<p>These messages can be used for informing of PLMN news,
emergencies, traffic reports, road accidents, delayed trains, weather reports,
theatre programmes, telephone numbers such as the number of Information Bureau
or tariffs.</p>


<p>The cell broadcast service is characterised by the following
aspects:</p>


<ul>
<li><p>No acknowledgement is sent from the
MS.</p>
</li>
<li><p>The cell broadcast message is sent
on control channels in a limited area, defined by the originator of the message,
by agreement with the PLMN.</p>
</li>
<li><p>Reception is possible only when the
MS is in the idle mode.</p>
</li>
<li><p>Cell broadcast messages will be sent
continuously so that all such messages are sent in turn and then repeated.
The cycle time will need to be short enough for important messages to be received
by travellers moving through a group of cells.</p>
</li>
<li><p>Cell broadcast messages are Mobile
Terminated only.</p>
</li>
<li><p>The maximum length of each cell broadcast
message will be 93 characters. The concatenation mechanism allows up to 15
of these 93-character messages to be treated as segments of a longer message.
These segments are then referred to as "pages".</p>
</li>
<li><p>A given message is likely to be received
repeatedly, yet the user will want to see only new messages. A given message
is therefore given an update number by the network. If a message with the
same geographical scope, message identifier, message code, and update number
is received earlier, it will be clear that this is not new and will be ignored
by the MS. If the message information is updated, it will have a new update
number so that it will be recognised and received.</p>
</li>
</ul>


<p>Currently, the management of CB messages is done either
locally or remotely through the BSC MMI, 7-bit characters are supported for
the CB messages and different messages are identified by the serial number.</p>


<p>The new enhancements in Cell Broadcast Service provides
both phase 2 and phase 2+ improvements. Phase 2 offers an 8-bit data whereas
phase 2+ (Universal Character Coding2 ) allows a 16 bit representation of
user characters. CB messages could be delivered in most of the alphabets or
languages around the globe. Phase 2+ Data coding Scheme also indicates whether
text compression is used or not. 41 UCS2 coded characters are included in
one CB message page without compression.</p>


<p>User characters can also be input in hexadecimal format
in order to support characters, which are not reachable by keyboard.</p>


<p>CB messages are stored in BSC in the Cell Broadcast Message
File. Once they are entered in the BSC and activated, they are broadcasted
cyclically by the BSC and conveyed transparently through the BTS to the MS.</p>


<a name="mar184124159" shape="rect"></a>
<div class="topic">
<h2>Capacity</h2>

<p>The broadcast area may be as large as a whole PLMN or as
small as a single cell. Typically, a message may take 2 seconds to be transmitted,
permitting 60 messages to be sent in a period of 2 minutes to that specified
broadcast area.</p>


<p>60 different active CB messages per cell can be defined
at the most. The maximum storage capacity is 1280 CB message pages. Multi-page
messages up to 15 pages are possible.</p>
</div>
</div>
</body>
</html>