|
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-455ED16F-D288-42C9-AA7A-AE5822F7A5BC" xml:lang="en"><title>Time Quickstart</title><shortdesc>Provides a brief overview of the contents of the Time platform |
|
13 service.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
14 <p> Time platform service provides the state of the device |
|
15 (mobile). It is controlled by a state machine that is SSM. These states |
|
16 are defined by system state policies within a SSM plug-in and system |
|
17 state changes are triggered by system-wide property changes or external |
|
18 requests. </p> |
|
19 <section id="GUID-E019BE30-391D-4055-B244-CFFB62C37E46-GENID-1-2-1-10-1-5-1-10-1-1-4-1-3-2"> |
|
20 <title>Concepts</title><ul> |
|
21 <li><p><xref href="GUID-CC79A63E-15DF-3437-983B-9A90966B3004.dita"><apiname>MRtcAdaptation</apiname></xref>: An SPI that allows customizing |
|
22 of the functionality of Real Time Clock (RTC) adaptation interface. </p></li> |
|
23 <li><p>Alarm Server: manages all alarms on the device and enables |
|
24 client UI applications to use the services provided by the Alarm Server. |
|
25 It relies on the Alarm UI to notify, which includes displaying and |
|
26 playing sounds. </p></li> |
|
27 <li><p>Alarm Client and Alarm Shared: are the static interface DLLs. |
|
28 Alarm client is the client side of the Alarm Server, which allows |
|
29 other components to interact with the Alarm Server. The Alarm Shared |
|
30 facilitates a common format shared across server and its clients for |
|
31 providing definition for an alarm. It consists of shared objects such |
|
32 as alarm class, IPC messages, repeat definitions, alarm states. </p></li> |
|
33 <li><p>System State Manager (SSM): manages the state of a device throughout |
|
34 its lifecycle. SSM extends the existing Generic Start-up Architecture |
|
35 (GSA) and also manages the system state and the system-wide property.</p></li> |
|
36 </ul></section> |
|
37 <section id="GUID-E019BE30-391D-4055-B244-CFFB62C37E46-GENID-1-2-1-10-1-5-1-10-1-1-4-1-3-3"> |
|
38 <title>Key uses for hardware implementators</title> |
|
39 <ul> |
|
40 <li><p>Including session alarms</p></li> |
|
41 <li><p>Adding, updating and deleting alarms. </p></li> |
|
42 <li><p>Performing alarm category-based operations such as retrieval |
|
43 and deletion.</p></li> |
|
44 </ul> </section> |
|
45 <section id="GUID-E019BE30-391D-4055-B244-CFFB62C37E46-GENID-1-2-1-10-1-5-1-10-1-1-4-1-3-4"><title>Key |
|
46 uses for device creators</title> <ul> |
|
47 <li><p>Activating an alarm on a specific date.</p></li> |
|
48 </ul> </section> |
|
49 </conbody></concept> |