Intel AMT Features > Alarm Clock > Detailed Description > Multiple Alarms Feature (Starting in Release 8.0)
CollapseAll image

Multiple Alarms Feature (Starting in Release 8.0)

Intel AMT supports up to five alarms. Each is represented by an instance of IPS_AlarmClockOccurrence. Invoke the method AMT_AlarmClockService.AddAlarm() to create a new alarm. If there are already five active alarms, the request will be rejected. The method accepts as input an embedded instance of the class IPS_AlarmClockOccurrence with the following fields set:






The value of the StartTime Datetime format requires a “T” between the date and the time and must end with “Z”. Seconds must be set to zero. For example: "yyyy-mm-ddThh:mm:00Z". The time must be later than the current time or the Set operation will be rejected.



The Interval format is PdDThHmM:

   There must be a P even if there is no hours setting. For example, P1D represents 1 day.

   The d value after the P is integer days. h and m after the T are integer hours and minutes. Valid hours are 0 to 23. Valid minutes are 0 to 59. Invalid values are rejected.

The value should be set to zero if the alarm is set to go off only once.



A user-provided identifier. This must be unique among the defined alarms. The maximum length of the string is 32 characters. It cannot be left empty. Use this field to retrieve a specific alarm.



If true, Intel AMT will delete the instance of IPS_AlarmClockOccurrence once the alarm has occurred.


Embedded Instance Example

The following is an example of the template used as input to the AMT_AlarmClockSettings.AddAlarm() method. The highlighted text shows the defined fields.

- <d:AlarmTemplate xmlns:d="" xmlns:s="">



- <s:StartTime>

<p:Datetime xmlns:p="">2012-12-31T22:00:00Z</p:Datetime>


- <s:Interval>

<p:Interval xmlns:p="">PT12M</p:Interval>





When an alarm occurs, the result depends on the current state of Intel AMT and the host. For example, if the platform is in S0, nothing happens to the platform state. If the platform is in  an Sx state and the defined power package is “On in S0”, Intel AMT will not wake up the host. When the power package is “ON in S0; ME Wake in S3, S4-S5” and connected to AC power, Intel AMT will wake up the host, moving it to S0.

After an alarm occurs one  of three things can happen to the alarm itself:

   If the occurrence has a defined Interval value, the StartTime will be changed to the current start time plus the interval.

   If the occurrence does not have a defined Interval, the alarm will not be reset, but the instance will remain.

   If the occurrence field DeleteOnCompletion is true, Intel AMT will delete the instance.

Backward Compatibility

There is a potential sixth instance of IPS_AlarmClockOccurrence reserved for backward compatibility: Adding an alarm via the legacy interface using the AMT_AlarmClockService properties AMTAlarmClockInterval and NextAMTAlarmTime causes Intel AMT to create an instance of IPS_AlarmClockOccurrence. Intel AMT will create this instance even if five instances already exist. The ElementName for this instance is “Alarm Clock 0”.


Users should not manage this instance directly. The AMT_AlarmClockService properties AMTAlarmClockInterval and NextAMTAlarmTime are deprecated and may be removed in a future release of Intel AMT.


Reason for Last Boot

Release 8.0 also adds an object that captures the cause of the last host boot. If Intel AMT was the source of the reboot, this object identifies which action caused it. See Get the Reason for the Last Boot.

Copyright © 2006-2022, Intel Corporation. All rights reserved.