User guide

Developers guidelines | AT commands
306 June 2010
vEvent Object
Example
vCalendar vEvent
object (MEETING): BEGIN:VCALENDAR
VERSION:1.0
PRODID:Sony Ericsson Calendar 1.0
BEGIN:VEVENT
DTSTART:19990125T123000
DTEND:19990125T170000
AALARM:19990125T121500
CATEGORIES:MEETING
SUMMARY;QUOTED-PRINTABLE;CHARSET=ISO-8859-1:Meeting
with Lars
LOCATION;QUOTED-PRINTABLE;CHARSET=ISO-8859-1:In my
room
X-IRMC-LUID:1E12FF7C01AB
END:VEVENT
END:VCALENDAR
Description: This is a definition of the vEvent object, which is related to the
vCalendar object. These objects are used when a user-defined cal-
endar entry is exchanged. The phone supports all-day event meet-
ings. The sync engine sends the vCalendar object with DTSTART,
set the date YYYYMMDD and leave out the time THHMMSS out.
The DTSTART is mandatory, as well as the DTEND. The same prin-
ciples applies for DTEND, that is, THHMMSS is skipped.
Syntax: <vevent-object>
“BEGIN:VEVENT“<CR>
“DTSTART:“<date_and_time>
“DTEND:“<date_and_time>
“AALARM:“<date_and_time>
“CATEGORIES:“<category>
“SUMMARY;“<encoding>“;“<character_set>“:“<summary>
“LOCATION;“<encoding>“;“<character_set>“:“<location>
“X-IRMC-LUID:“<x_irmc_luid>
“END:VEVENT“
Parameters:
<date_and_time>: String. <year><month><day>T<hour><minute<second>.
The date and time values for all vCalendar properties are formatted
as a string consistent with the ISO 8601 representation for
combinations of dates and times.
Note: All time values are given in local time.
Example
<date_and_time>: 19960415T083000. 8:30 AM on April 15, 1996 local time.
<category>: “MEETING“ | “PHONE CALL“ | “MISCELLANEOUS“
<encoding>: “QUOTED-PRINTABLE“ | “BASE-64“ | “8BIT“
<character_set>: “ISO-8859-1“ | “UTF-8“
<summary>: String. Maximum length 36 bytes.