# US 2018/0025323 A1 · Storage and structure of calendars with an infinite set of intentional-time events for calendar applications > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0025323 A1 - Document ID: US20180025323A1 - Status: Published application - Kind: A1 - Application number: 15/216,042 - Filed: 2016-07-21 - Published: 2018-01-25 - Earliest claimed: 2016-07-21 - Assignees: Microsoft Technology Licensing, LLC - Applicants: Microsoft Technology Licensing, LLC - Inventors: Fabio Andre PINTOS - Web page: https://patentgrep.com/patent/US20180025323A1 ## CPC - G06Q 10/1093: Calendar-based scheduling for persons or groups - G06F 3/04817: using icons (graphical or visual programming using iconic symbols G06F8/34) - G06F 3/0482: Interaction with lists of selectable items, e.g. menus - G06Q 10/109: Time management, e.g. calendars, reminders, meetings or time accounting - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An event can be stored using an indication of recurrence and an intent-time event time that includes a trigger indicator and optionally an offset. When a view of a calendar having intentional-time events is requested by a calendar application, a calendar service can search a storage resource for the requested calendar and any events that fall within a requested start time and end time. The identified events can be provided to a source of the request. Any intent-time event times that are stored as part of intentional-time events can be calculated based on their triggers and offsets. The calculations may be carried by the calendar service and the results provided to the calendar application or by the calendar application itself. ## Claims ### Claim 1 A calendaring system comprising: a processing system; a storage system; structured calendar data stored on a storage resource of the storage system, the structured calendar data comprising, for each intentional-time event of recurring-type, at least a corresponding event identifier, a calendar identifier indicating a corresponding calendar to which the event belongs, an indication of recurrence, and a corresponding intent-time event time; instructions for supporting a calendar application stored on the storage system, the instructions directing the processing system to at least: receive a request for a calendar view; search a storage resource storing calendar data for a calendar associated with the request and any events associated with the calendar that fall within a start time and an end time; and provide any identified intentional-time events that fall within the start time and the end time to a source of the request. ### Claim 2 (depends on 1) The system of claim 1, further comprising instruction that direct the processing system to at least: get an event start time and end time for each day of an occurrence of an identified intentional-time event using a trigger and any offset indicated by the intent-time event time corresponding to the identified intentional-time event. ### Claim 3 (depends on 2) The system of claim 2, wherein the intent-time event time comprises an astronomical phenomena indicator and a location data. ### Claim 4 (depends on 3) The system of claim 3, wherein the instructions that direct the processing system to get the event start time, direct the processing system to determine, for each day of the occurrence, a trigger time of an astronomical phenomena indicated by the astronomical phenomena indicator at a location indicated by the location data. ### Claim 5 (depends on 2) The system of claim 2, wherein the intent-time event time comprises a tide phenomena indicator and an index to a tide table. ### Claim 6 (depends on 5) The system of claim 5, wherein the instructions that direct the processing system to get the event start time, direct the processing system to determine, for each day of the occurrence, a trigger time of a tide phenomena indicated by the tide phenomena indicator at a location indicated by the index to the tide table. ### Claim 7 A computer-implemented method comprising: receiving, at a server, a request for a calendar view; searching a storage resource storing calendar data for a calendar associated with the request and any events associated with the calendar that fall within a start time and an end time; and getting a resulting calculated actual time of an event start time and an end time for each day of an occurrence of an identified intentional-time event using a trigger and any offset indicated by an intent-time event time corresponding to the identified intentional-time event. ### Claim 8 (depends on 7) The method of claim 7, wherein the intent-time event time comprises an astronomical phenomena indicator and a location data. ### Claim 9 (depends on 8) The method of claim 8, wherein getting the event start time comprises: determining, for each day of the occurrence, a trigger time of an astronomical phenomena indicated by the astronomical phenomena indicator at a location indicated by the location data. ### Claim 10 (depends on 7) The method of claim 7, wherein the intent-time event time comprises a tide phenomena indicator and an index to a tide table. ### Claim 11 (depends on 10) The method of claim 10, wherein getting the event start time comprises: determining, for each day, for each day of the occurrence, a trigger time of a tide phenomena indicated by the tide phenomena indicator at a location indicated by the index to the tide table. ### Claim 12 (depends on 7) The method of claim 7, further comprising: providing the resulting calculated actual time of any identified intentional-time events that fall within the start time and the end time to a source of the request ### Claim 13 (depends on 7) The method of claim 7, further comprising: providing any individual events and any recurring events that do not include an intent-time event time but that fall within the start time and the end time to a source of the request. ### Claim 14 One or more computer-readable storage media having instructions stored thereon that, when executed by a processing system, direct the processing system to at least: receive an input indicative of an intentional-time event of recurring-type; determine an appropriate intent-time format to at least identify any additional information for a trigger; store an indication of recurrence for the intentional-time event in a storage resource storing calendar data; and store a trigger indicator, the any additional information, and any received offset as an event time property for the intentional-time event in the storage resource. ### Claim 15 (depends on 14) The media of claim 14, further comprising instructions stored thereon that direct the processing system to at least: receive a request for a calendar view; search the storage resource for a calendar associated with the request and any events associated with the calendar that fall within a start time and an end time; and provide any identified intentional-time events that fall within the start time and the end time to a source of the request. ### Claim 16 (depends on 15) The media of claim 15, further comprising instruction stored thereon that direct the processing system to at least: get an event start time for each day of an occurrence of an identified intentional-time event using the trigger and any offset stored for the identified intentional-time event. ### Claim 17 (depends on 16) The media of claim 16, wherein the trigger indicator comprises an astronomical phenomena indicator and the any additional information comprises a location data. ### Claim 18 (depends on 17) The media of claim 17, wherein the instructions that direct the processing system to get the event start time, direct the processing system to determine, for each day of the occurrence, a trigger time of an astronomical phenomena indicated by the astronomical phenomena indicator at a location indicated by the location data. ### Claim 19 (depends on 16) The media of claim 16, wherein the trigger indicator comprises a tide phenomena indicator and the any additional information comprises an index to a tide table. ### Claim 20 (depends on 19) The media of claim 19, wherein the instructions that direct the processing system to get the event start time, direct the processing system to determine, for each day of the occurrence, a trigger time of a tide phenomena indicated by the tide phenomena indicator at a location indicated by the index to the tide table.