Determining location of a calendar event

Patent metadata

Field	Value
Publication number	US-2016357804-A1
Application number	US-201514869729-A
Country	US
Kind code	A1
Filing date	Sep 29, 2015
Priority date	Jun 7, 2015
Publication date	Dec 8, 2016
Grant date	—

Abstract

A method of determining a location of an event stored on a calendar application of a device is provided. The method sends a location string associated with the event from the calendar application to a geo coder. The method receives a handle that includes a set of data items that uniquely identifies the location of the event. The data items in the handle are not accessed or individually utilized by the calendar application. Prior to the start of the event, the method requests travel updates to the location of event from a navigation application. The request includes the handle and the start time of the event. The method receives periodic routing updates to the location of the event from the navigation application.

First claim

1 . A method of determining a location of an event stored on a calendar application of a device, the method comprising:
sending a location string associated with the event from the calendar application to a geo coder; receiving a handle comprising a plurality of location data items associated with the location of the event from the geo coder, wherein the calendar application does not access the individual location data items in the plurality of data items of the handle; prior to an start time of the event, requesting travel updates to the location of event from a navigation application, the request comprising the handle and the start time of the event; and receiving periodic travel updates to the location of the event from the navigation application.

2 . The method of claim 1 , wherein the travel updates comprise a time to leave a current location of the device in order to get to the event location on time.

3 . The method of claim 2 , wherein the travel updates further comprise at least one of traffic information and traffic incidents on a route from a current location of the device to the location of the event.

4 . The method of claim 1 , wherein the handle is a binary large object (blob) comprising data.

5 . The method of claim 1 , wherein the plurality of location data items in the handle comprises geographical coordinates of the event location.

6 . The method of claim 5 , wherein the geographical coordinates of the event location comprise a latitude and a longitude associated with the event location.

7 . The method of claim 1 further comprising:
sending a request for individual location data items to the geo coder, the request comprising the handle; and
receiving a set of location data items at the calendar application from the navigation application.

8 . The method of claim 7 , wherein the set of location data items comprise a latitude and a longitude associated with the event location.

9 . The method of claim 7 , wherein the set of location data items comprises a set of entry points to the event location.

10 . The method of claim 7 , wherein the set of location data items comprises a set of photos associated with the event location.

11 . The method of claim 7 , wherein the set of location data items comprises at least one of an street address, a telephone number, a website, and hours of operation associated with the event location.

12 . The method of claim 7 , wherein the set of location data items comprises at least one of a set of reviews, a business category, and a set of applications associated with the event location.

13 . The method of claim 1 , wherein the handle items unambiguously identifies the location of the event.

14 . The method of claim 1 , wherein the handle is synchronized across a plurality of devices.

15 . A non-transitory computer readable medium storing a program for determining a location of an event stored on a calendar application of a device, the program executable by at least one processing unit, the program comprising sets of instructions for:
sending a location string associated with the event from the calendar application to a geo coder; receiving a handle comprising a plurality of location data items associated with the location of the event from the geo coder, wherein the calendar application does not access the individual location data items in the plurality of data items of the handle; requesting travel updates to the location of event from a navigation application prior to an start time of the event, the request comprising the handle and the start time of the event; and receiving periodic travel updates to the location of the event from the navigation application.

16 . The non-transitory computer readable medium of claim 15 , wherein the travel updates comprise a time to leave a current location of the device in order to get to the event location on time.

17 . (canceled)

18 . The non-transitory computer readable medium of claim 15 , wherein the plurality of location data items in the handle comprises geographical coordinates of the event location.

19 - 22 . (canceled)

23 . A device comprising:
a set of processing units; and a non-transitory computer readable medium storing a program for determining a location of an event stored on a calendar application of a device, the program executable by at least one processing unit, the program comprising sets of instructions for:
sending a location string associated with the event from the calendar application to a geo coder;
receiving a handle comprising a plurality of location data items associated with the location of the event from the geo coder, wherein the calendar application does not access the individual location data items in the plurality of data items of the handle;
requesting travel updates to the location of event from a navigation application prior to an start time of the event, the request comprising the handle and the start time of the event; and
receiving periodic travel updates to the location of the event from the navigation application.

24 . The device of claim 23 , wherein the travel updates comprise a time to leave a current location of the device in order to get to the event location on time.

25 - 27 . (canceled)

28 . The device of claim 27 , wherein the set of location data items comprise at least one of (i) a latitude and a longitude associated with the event location, (ii) a set of entry points to the event location, (iii) a set of photos associated with the event location, (iv) an street address, (v) a set of telephone numbers associated with the event location, (vi) a website, (vii) hours of operation associated with the event location, (viii) a set of reviews, (ix) a business category, and (x) a set of applications associated with the event location.

Assignees

• Apple Inc

Inventors

• Mcgavran Christine B
• Adler Scott
• Miladinov Viktor
• Ball Matthew B
• Wagner Thomas

Classifications

• G06F16/29

  Geographical information databases · CPC title

• H04W52/0229

  where the received signal is a wanted signal · CPC title

• G06F1/3206

  Monitoring of events, devices or parameters that trigger a change in power modality · CPC title

• G06F16/2358 Primary

  Change logging, detection, and notification (replication G06F16/27) · CPC title

• H04W4/025

  using location based information parameters · CPC title