1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE concept

    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

    12 <concept id="GUID-FE2E8E58-6656-534E-A052-095AF559A482" xml:lang="en"><title>Alarm

    13 Time Formats</title><prolog><metadata><keywords/></metadata></prolog><conbody>

    14 <p>The Alarm Server supports two types of time formats used to express the

    15 expiry time of an alarm: </p>

    16 <ul>

    17 <li id="GUID-90BAC4D4-DD00-51D2-8661-51E2680DA315"><p> <b>Fixed time format</b> -

    18 The alarm expires at the given UTC time and has no associated UTC offset.

    19 The alarm is not rescheduled when an UTC offset or DST change occur. </p> </li>

    20 <li id="GUID-A007966C-84AD-56E2-B692-7CAE4B3A648F"><p> <b>Floating time format</b> -

    21 The alarm expires at the given local (wall clock) time in the current UTC

    22 offset and are re-scheduled when either the UTC offset or DST change occurs. </p> </li>

    23 </ul>

    24 <p>The Alarm Server maintains a queue of alarms and the format of these alarms

    25 may be either fixed or floating time format. </p>

    26 <p>Hence, if the user adds an alarm defining one of its characteristics as <xref href="GUID-20A42BF7-A0F5-3177-9592-E3AE097B4CF2.dita#GUID-20A42BF7-A0F5-3177-9592-E3AE097B4CF2/GUID-EBAEFA64-7892-32D6-B8BF-EBE4EC9AFB83"><apiname>TAlarmCharacteristics::EAlarmCharacteristicsIsFixed</apiname></xref>,

    27 then it is added in the alarm queue as fixed time format based alarm. </p>

    28 <p> </p>

    29 <p> <b>NOTE</b>: </p>

    30 <ul>

    31 <li id="GUID-14A58869-C859-5F7B-A28A-319F180DD8CE"><p> <b>UTC time</b> is

    32 the non-secure system time in UTC (UTC time range is from 0-24, so after 12,

    33 the time is expressed in PM). </p> <p> <b>Standard Time</b> = UTC Time + Timezone/UTC

    34 offset </p> <p> <b>Wall Clock/local time</b> = UTC Time + Timezone/UTC offset

    35 ± DST offset </p> </li>

    36 <li id="GUID-24513E63-880C-5147-9A5F-AFF047370175"><p>All alarms (irrespective

    37 of the time format) undergo rescheduling and re-evaluation of their next due

    38 time (considering their repeat definition) only when either system time/date

    39 or workdays change. </p> </li>

    40 <li id="GUID-80D105D4-D99D-56F3-9D92-11F7686FF3C1"><p>Only the floating time

    41 format based alarms undergo re-scheduling and re-evaluation of their next

    42 due time if the system time/date, workdays, UTC offset changes or DST rollover

    43 event occurs. </p> </li>

    44 </ul>

    45 </conbody></concept>