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-9BE3DEBE-A1CE-5A2F-9746-1E6F2B5B050E" xml:lang="en"><title>Environment

    13 and DST Changes</title><prolog><metadata><keywords/></metadata></prolog><conbody>

    14 <p>This section explains the effect on alarms due to the environment and DST

    15 changes. </p>

    16 <section><title>Environment Changes</title> <p>An environment change typically

    17 involves change in the system time/date, workdays or UTC offset, and due to

    18 this, alarm's expiry time can be put in the past.</p><p>When an environment

    19 change occurs, the Alarm Server can respond in any of the following ways:</p><ul>

    20 <li><p>The Alarm Server queues the alarms that have been skipped. These alarms

    21 then expire immediately and must be acknowledged by the device user.</p></li>

    22 <li><p>The Alarm Server uses <codeph>KSkippedAlarmInstancesPubSubKey</codeph> P&amp;S

    23 key to notify the clients about the skipped calendar alarms. This key can

    24 be used only by the device creators.</p></li>

    25 </ul><p>Alarm Server observes changes in the UTC offset as a locale change

    26 since the UTC offset is set according to the localized position. It observes

    27 this offset from the system, and on change of this offset, only the alarms

    28 in the alarm queue that are based on the floating time undergoes changes.</p><p><b>NOTE</b>:

    29 All alarms in the alarm queue are re-evaluated only if system time/date and

    30 workday changes. This is applicable for all alarms irrespective of their time

    31 formats. The workday changes are also a locale change for the system.</p></section>

    32 <section><title>Daylight Saving Time Changes</title> <p>Daylight Saving Time

    33 (DST) or Summer Time, is a way of utilizing more daylight by advancing the

    34 local time by one hour during the summer. </p> <p>The clocks are adjusted

    35 forward by one hour at the beginning of spring and are adjusted backward in

    36 autumn. The time adjusted backward by one hour in autumn is usually referred

    37 as Standard Time (or Winter Time). In a typical case where a one-hour shift

    38 occurs at 02:00 local time, the clock is adjusted forward from 02:00 standard

    39 time to 03:00 DST in spring and that day has 23 hours. Whereas in autumn,

    40 the clock is adjusted backward from 02:00 DST to 01:00 standard time, repeating

    41 that hour, and that day has 25 hours. </p> <p>Alarm Server observes this DST

    42 event from the Time Zone Server using <xref href="GUID-EAB78B96-8373-3A96-AA36-43207C3FB514.dita"><apiname>KDSTChangePropertyKey</apiname></xref> P&amp;S

    43 key. This key can be used only by the device creators. On receiving notification

    44 of this event through the key, all alarms (based on the floating time format)

    45 in the alarm queue are re-evaluated for their expiry time. </p> </section>

    46 </conbody></concept>