US20100161720A1 - System and method for providing content to a mobile device - Google Patents
System and method for providing content to a mobile device Download PDFInfo
- Publication number
- US20100161720A1 US20100161720A1 US12/402,386 US40238609A US2010161720A1 US 20100161720 A1 US20100161720 A1 US 20100161720A1 US 40238609 A US40238609 A US 40238609A US 2010161720 A1 US2010161720 A1 US 2010161720A1
- Authority
- US
- United States
- Prior art keywords
- data
- computing device
- mobile computing
- user
- processing circuit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 title description 24
- 238000012545 processing Methods 0.000 claims abstract description 93
- 230000006870 function Effects 0.000 claims abstract description 32
- 230000015654 memory Effects 0.000 claims abstract description 13
- 238000004891 communication Methods 0.000 description 17
- 230000004044 response Effects 0.000 description 10
- 230000006399 behavior Effects 0.000 description 7
- 230000001413 cellular effect Effects 0.000 description 7
- 238000007726 management method Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 4
- 230000006855 networking Effects 0.000 description 4
- 230000000007 visual effect Effects 0.000 description 4
- 238000012790 confirmation Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 238000012552 review Methods 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 239000013589 supplement Substances 0.000 description 2
- 241000700605 Viruses Species 0.000 description 1
- 230000001133 acceleration Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005108 dry cleaning Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 235000013410 fast food Nutrition 0.000 description 1
- 235000013305 food Nutrition 0.000 description 1
- 238000009472 formulation Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 238000010237 hybrid technique Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 235000012054 meals Nutrition 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000005236 sound signal Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 235000019640 taste Nutrition 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/487—Arrangements for providing information services, e.g. recorded voice services or time announcements
- H04M3/4872—Non-interactive information services
- H04M3/4878—Advertisement messages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0261—Targeted advertisements based on user location
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0241—Advertisements
- G06Q30/0251—Targeted advertisements
- G06Q30/0267—Wireless devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/029—Location-based management or tracking services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
- H04W4/21—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel for social networking applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2203/00—Aspects of automatic or semi-automatic exchanges
- H04M2203/20—Aspects of automatic or semi-automatic exchanges related to features of supplementary services
- H04M2203/2072—Schedules, e.g. personal calendars
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/15—Information service where the information is dependent on the location of the subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2242/00—Special services or facilities
- H04M2242/30—Determination of the location of a subscriber
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42059—Making use of the calling party identifier
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42348—Location-based services which utilize the location information of a target
- H04M3/42357—Location-based services which utilize the location information of a target where the information is provided to a monitoring entity such as a potential calling party or a call processing server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
Definitions
- the present disclosure relates generally to the field of mobile devices, and more specifically, to systems and methods for performing functions based on past uses of a device or behaviors of a user of the device.
- FIG. 1 is a front view of a mobile device according to an exemplary embodiment.
- FIG. 2 is a back view of the mobile device of FIG. 1 according to an exemplary embodiment.
- FIG. 3 is a side view of the mobile device of FIG. 1 according to an exemplary embodiment.
- FIG. 4 is a block diagram of the mobile device of FIG. 1 according to an exemplary embodiment.
- FIG. 5 is a block diagram of a system for providing content to a mobile device according to an exemplary embodiment.
- FIG. 6 is a flow chart of a method of providing content to a mobile device according to an exemplary embodiment.
- FIG. 7 is a front view of a display of a mobile device according to an exemplary embodiment.
- FIG. 8 is a front view of a display of a mobile device according to an exemplary embodiment.
- FIG. 9 is a front view of a display of a mobile device according to an exemplary embodiment.
- FIG. 10 is a flowchart of a system and method for performing a function based on use data and a present condition, accordingly to an exemplary embodiment.
- a mobile device 10 is shown.
- the teachings herein can be applied to device 10 or to other electronic devices (e.g., a desktop computer), mobile computing devices (e.g., a laptop computer) or handheld computing devices, such as a personal digital assistant (PDA), smartphone, mobile telephone, personal navigation device, etc.
- device 10 may be a smartphone, which is a combination mobile telephone and handheld computer having PDA functionality.
- PDA functionality can comprise one or more of personal information management (e.g., including personal data applications such as email, calendar, contacts, etc.), database functions, word processing, spreadsheets, voice memo recording, Global Positioning System (GPS) functionality, etc.
- personal information management e.g., including personal data applications such as email, calendar, contacts, etc.
- database functions e.g., word processing, spreadsheets, voice memo recording, Global Positioning System (GPS) functionality, etc.
- GPS Global Positioning System
- Device 10 may be configured to synchronize personal information from these applications with a computer (e.g., a desktop, laptop, server, etc.). Device 10 may be further configured to receive and operate additional applications provided to device 10 after manufacture, e.g., via wired or wireless download, SecureDigital card, etc.
- a computer e.g., a desktop, laptop, server, etc.
- Device 10 may be further configured to receive and operate additional applications provided to device 10 after manufacture, e.g., via wired or wireless download, SecureDigital card, etc.
- device 10 includes a housing 12 and a front side 14 and a back side 16 .
- Device 10 further comprises a display 18 and a user input device 20 (e.g., a QWERTY keyboard, buttons, touch screen, speech recognition engine, etc.).
- Display 18 may comprise a touch screen display in order to provide user input to a processor 40 (see FIG. 4 ) to control functions, such as to select options displayed on display 18 , enter text input to device 10 , or enter other types of input.
- Display 18 also provides images (see, e.g., FIG. 7 ) that are displayed and may be viewed by users of device 10 .
- User input device 20 can provide similar inputs as those of touch screen display 18 .
- Display 18 may comprise a capacitive touch screen, a mutual capacitance touch screen, a self capacitance touch screen, a resistive touch screen, a touch screen using cameras and light such as a surface multi-touch screen, proximity sensors, or other touch screen technologies, and so on.
- Display 18 may be configured to receive inputs from finger touches at a plurality of locations on display 18 at the same time.
- Display 18 may be configured to receive a finger swipe or other directional input, which may be interpreted by a processing circuit to control certain functions distinct from a single touch input.
- housing 12 is configured to hold a screen such as display 18 in a fixed relationship above a user input device such as user input device 20 in a substantially parallel or same plane.
- This fixed relationship excludes a hinged or movable relationship between the screen and the user input device (e.g., a plurality of keys) in the fixed embodiment.
- Device 10 may be a handheld computer, which is a computer small enough to be carried in a hand of a user, comprising such devices as typical mobile telephones and personal digital assistants, but excluding typical laptop computers and tablet PCs.
- the various input devices and other components of device 10 as described below may be positioned anywhere on device 10 (e.g., the front surface shown in FIG. 1 , the rear surface shown in FIG. 2 , the side surfaces as shown in FIG. 3 , etc.).
- various components such as a keyboard etc. may be retractable to slide in and out from a portion of device 10 to be revealed along any of the sides of device 10 , etc.
- housing 12 may be any size, shape, and have a variety of length, width, thickness, and volume dimensions.
- width 13 may be no more than about 200 millimeters (mm), 100 mm, 85 mm, or 65 mm, or alternatively, at least about 30 mm, 50 mm, or 55 mm.
- Length 15 may be no more than about 200 mm, 150 mm, 135 mm, or 125 mm, or alternatively, at least about 70 mm or 100 mm.
- Thickness 17 may be no more than about 150 mm, 50 mm, 25 mm, or mm, or alternatively, at least about 10 mm, 15 mm, or 50 mm.
- the volume of housing 12 may be no more than about 2500 cubic centimeters (cc) or 1500 cc, or alternatively, at least about 1000 cc or 600 cc.
- device 10 comprises a processing circuit 46 comprising a processor 40 .
- Processor 40 can comprise one or more microprocessors, microcontrollers, and other analog and/or digital circuit components configured to perform the functions described herein.
- Processor 40 may comprise one or more memories (e.g., random access memory, read only memory, flash, etc.) configured to store software applications provided during manufacture or subsequent to manufacture by the user or by a distributor of device 10 .
- processor 40 can comprise a first applications microprocessor configured to run a variety of personal information management applications, such as email, a calendar, contacts, etc., and a second, radio processor on a separate chip or as part of a dual-core chip with the application processor.
- the radio processor may be configured to operate telephony functionality.
- Device 10 can be configured for cellular radio telephone communication, such as Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), Third Generation (3G) systems such as Wide-Band CDMA (WCDMA), or other cellular radio telephone technologies.
- Device 10 can further be configured for data communication functionality, for example, via GSM with General Packet Radio Service (GPRS) systems (GSM/GPRS), CDMA/1XRTT systems, Enhanced Data Rates for Global Evolution (EDGE) systems, Evolution Data Only or Evolution Data Optimized (EV-DO), and/or other data communication technologies.
- GPRS General Packet Radio Service
- EDGE Enhanced Data Rates for Global Evolution
- EV-DO Evolution Data Only or Evolution Data Optimized
- Device 10 comprises a receiver 38 which comprises analog and/or digital electrical components configured to receive and transmit wireless signals via antenna 22 to provide cellular telephone and/or data communications with a fixed wireless access point, such as a cellular telephone tower, in conjunction with a network carrier, such as, Verizon Wireless, Sprint, etc.
- Device 10 can further comprise circuitry to provide communication over a local area network, such as Ethernet or according to an IEEE 802.11x standard or a personal area network, such as a Bluetooth or infrared communication technology.
- Device 10 further comprises a microphone 36 (see FIG. 2 ) configured to receive audio signals, such as voice signals, from a user or other person in the vicinity of device 10 , typically by way of spoken words.
- processor 40 can further be configured to provide video conferencing capabilities by displaying on display 18 video from a remote participant to a video conference, by providing a video camera on device 10 for providing images to the remote participant, by providing text messaging, two-way audio streaming in full- and/or half-duplex mode, etc.
- Device 10 further comprises a location determining application, shown in FIG. 3 as GPS application 44 .
- GPS application 44 can communicate with and provide the location of device 10 at any given time.
- Device 10 may employ one or more location determination techniques including, for example, Global Positioning System (GPS) techniques, Cell Global Identity (CGI) techniques, CGI including timing advance (TA) techniques, Enhanced Forward Link Trilateration (EFLT) techniques, Time Difference of Arrival (TDOA) techniques, Angle of Arrival (AOA) techniques, Advanced Forward Link Trilateration (AFTL) techniques, Observed Time Difference of Arrival (OTDOA) techniques, Enhanced Observed Time Difference (EOTD) techniques, Assisted GPS (AGPS) techniques, hybrid techniques (e.g., GPS/CGI, AGPS/CGI, GPS/AFTL or AGPS/AFTL for CDMA networks, GPS/EOTD or AGPS/EOTD for GSM/GPRS networks, GPS/OTDOA or AGPS/OTDOA for UMTS networks), triangulation techniques such as Wi-Fi triang
- Device 10 may be arranged to operate in one or more location determination modes including, for example, a standalone mode, a mobile station (MS) assisted mode, and/or an MS-based mode.
- a standalone mode such as a standalone GPS mode
- device 10 may be arranged to autonomously determine its location without real-time network interaction or support.
- device 10 may be arranged to communicate over a radio access network (e.g., UMTS radio access network) with a location determination entity such as a location proxy server (LPS) and/or a mobile positioning center (MPC).
- a radio access network e.g., UMTS radio access network
- LPS location proxy server
- MPC mobile positioning center
- Device 10 further comprises a memory 42 coupled to or as part of processor 40 .
- Memory 42 may store a variety of data (e.g., context data, etc.) such as information, data, applications, files, etc. that may be used or accessed using device 10 .
- calendar data may include data regarding various appointments such as location data (e.g., an individual's residence, a commercial establishment, an address or other geographic indicator such as a city, state, etc., a conference room number, and so on), time/date data (e.g., a date and/or time for a specific appointment, data regarding a recurring appointment, etc.), attendee data, and other data related to an appoint or meeting.
- location data e.g., an individual's residence, a commercial establishment, an address or other geographic indicator such as a city, state, etc., a conference room number, and so on
- time/date data e.g., a date and/or time for a specific appointment, data regarding a recurring appointment
- Contacts data may include information regarding specific contacts, such as names, addresses, phone numbers, email addresses, fax numbers, and contact-specific notes (e.g., notes about the specific contact such as a birthday, anniversary, etc.).
- Messaging data may include information related to a variety of messaging applications including email, text messaging, short message service (SMS), and so on.
- SMS short message service
- device 10 may utilize other context data in accordance with the various embodiments disclosed herein (e.g., data related to web-sites the user has visited using device 10 , bookmarks or favorites for web-sites, data downloaded from a user's social networking account on a web-site (e.g., a MySpace or Facebook account), data related to audio and/or video clips (e.g., songs, videos, etc.), to-do lists, memo applications, gaming applications, etc.).
- context data e.g., data related to web-sites the user has visited using device 10 , bookmarks or favorites for web-sites, data downloaded from a user's social networking account on a web-site (e.g., a MySpace or Facebook account), data related to audio and/or video clips (e.g., songs, videos, etc.), to-do lists, memo applications, gaming applications, etc.).
- data related to web-sites the user has visited using device 10 e.g., bookmarks or favorites for web-sites,
- device 10 may be configured to receive and provide content (e.g., generic alerts or notifications, general inquiries, advertisement data, selectable links, icons, etc., and so on) to users.
- content e.g., generic alerts or notifications, general inquiries, advertisement data, selectable links, icons, etc., and so on
- device 10 may communicate with servers 50 , 52 , which may in turn communicate with one or more advertisement sources 54 , 56 , 58 (e.g., ad sources such as retailers, restaurants, services, etc.).
- advertisement sources 54 , 56 , 58 e.g., ad sources such as retailers, restaurants, services, etc.
- server 52 may be an advertisement service configured to provide advertisement data (e.g., visual advertisements, audible advertisements, e-coupons, etc.) from ad sources 54 , 56 , 58 to device 10 (either in coordination with, or independent from, servers 48 , 50 , as discussed in further detail below).
- Server 50 may be a server associated with an application developer that provides applications to be run on or provided to device 10 .
- server 50 and/or server 52 may be a server associated with a manufacturer of device 10 .
- sources 54 , 56 , 58 may provide advertisement data to device 10 without utilizing servers 50 , 52 (e.g., such that the advertisement data is received by processor 40 of device 10 from sources 54 , 56 , 58 ).
- the advertisement data or content may include a variety of information and be provided in a variety of ways.
- content may be provided to a user of device 10 in the form of a visual image provided on display 18 .
- an icon may be displayed on device 10 and may be selected by a user to provide an enlarged advertisement such as an electronic coupon, etc.
- device 10 may provide an audible message (e.g., a recording of an advertisement, etc.).
- advertisement data may be provided on display 18 and superimposed over another image, such as the current image the user is viewing, a geographic map indicating the location of the establishment(s) the advertisement data is associated with, and so on.
- the content may include or be non-advertisement data such as general point-of-interest data, appointment data, etc.
- other types of content or advertisement data may be provided to device 10 (e.g., text, graphics, audio data, video data, etc.).
- server 52 may be involved in providing content or advertisement data to device 10 .
- server 52 may be associated with an advertisement service (e.g., AdSense, provided by Google, Inc., Mountain View, Calif.) and be configured to provide advertisement data to device 10 independent from server 50 .
- AdSense e.g., AdSense, provided by Google, Inc., Mountain View, Calif.
- server 52 may communicate with device 10 and with one or more of ad sources 54 , 56 , 58 .
- Ad sources 54 , 56 , 58 may provide advertisement data to server 52 , which may in turn provide the advertisement data to mobile device 10 .
- server 52 may provide the advertisement data based at least in part on certain criteria or data (e.g., to act as a filter to provide advertisement data having higher relevance to a user), such as a location of device 10 , historical data associated with the usage of device 10 (e.g., web browsing history, location history), user-specific data (data stored in an information management application such as an email application, calendar application, contacts application, and so on), or some other criteria or data.
- criteria or data may be defined by a user and the access to such criteria or data for filtering or otherwise providing advertisement data and other content to device 10 may be limited by a user or other entity.
- server 52 may permit various ad sources (e.g., ad sources 54 , 56 , 58 ) to register with server 52 in order to have their advertisement data provided to users (e.g., a user of device 10 ). Based on certain criteria or data, the advertisement data may then be selected for delivery to various devices/users.
- ad sources e.g., ad sources 54 , 56 , 58
- users e.g., a user of device 10
- the advertisement data may then be selected for delivery to various devices/users.
- server 52 may be configured to provide advertisement data or other content to device 10 in conjunction with or through server 50 .
- server 50 may be or include a server associated with an application developer that provides applications (e.g., mobile device-specific applications, such as games, financial tools, location-based mapping programs, music players, etc.) to device 10 .
- Advertisement data may be provided to (by one or more of servers 50 , 52 ) and/or displayed on device 10 while one or more applications provided by server 50 are running on device 10 .
- one or more advertisements provided by server 52 may be displayed along a top, side, or bottom portion of display 18 while a user is running an application provided by server 50 .
- server 50 may be a server associated with a manufacturer of device 10 , and may have wireless or other access to data unavailable to server 52 (e.g., user-specific data such as data from an information management application, including email, calendar, contacts, and other applications).
- Server 50 may provide data associated with device 10 (and/or the associated user) to server 52 .
- Such data may be used, for example, to filter advertisement data or other content being provided to device 10 to increase the relevancy of the advertisement data to the particular device/user.
- the various embodiments discussed herein are provided for purposes of illustration only, and that more or fewer servers or other parties/entities may be involved in the provision of advertisement data or other content to device 10 . All such embodiments are deemed to be within the scope of the present disclosure.
- Context data may generally refer to data associated with the context of device 10 or a user thereof, and may include historical data (e.g., data associated with past usage patterns of device 10 such as movement of the device, locations of the device, messaging data, web browsing activity, transactions executed using device 10 , etc.), data associated with the current state of device 10 (e.g., mobile-specific inputs such as a current location, direction of travel, speed/acceleration of movement, etc., a current time of day, date, etc.), data associated with an information management application (e.g., an email or other messaging application, a calendar application, a contacts application, and so on), or other data accessible by or otherwise associated with device 10 or a user thereof (e.g., data associated with mobile devices or users of mobile devices that are included in a contact listing, social networking group,
- Context data may in some embodiments generally refer to any type of data or information that may be used to determine a user's context, and may include or indicate usage patterns of device 10 such as on/off patterns (e.g., a pattern of higher of usage (e.g., times of day during which device 10 is typically on or off, etc.), web browsing (e.g., web sites visited, etc.), location/movement history (e.g., modes of travel, locations visited, etc.), and so on.
- on/off patterns e.g., a pattern of higher of usage (e.g., times of day during which device 10 is typically on or off, etc.)
- web browsing e.g., web sites visited, etc.
- location/movement history e.g., modes of travel, locations visited, etc.
- device 10 may access data indicating a planned/future destination (e.g., location) of a user (e.g., as indicated by a calendar or other information management application) in addition to the user's current location, and provide the user with data regarding nearby points of interest (e.g., hours of operation, whether open /closed, etc.) or other establishments.
- a planned/future destination e.g., location
- points of interest e.g., hours of operation, whether open /closed, etc.
- device 10 may access data indicating that the user is outside of a particular geographic area (e.g., outside a certain distance from a home location, a work location, etc., outside an area code of a mobile phone number associated with device 10 , outside of an address contained in a contacts application, and so on), and/or data indicating that a user has recently moved locations (e.g., as a result of travelling via plane, train, etc.), and trigger the delivery of content based on the user's location and/or on a time-sensitive basis (e.g., based on departure times, arrival times, etc.).
- a particular geographic area e.g., outside a certain distance from a home location, a work location, etc., outside an area code of a mobile phone number associated with device 10 , outside of an address contained in a contacts application, and so on
- data indicating that a user has recently moved locations e.g., as a result of travelling via plane, train, etc.
- a time-sensitive basis e
- Device 10 may further access data indicating that a user has “free time” (e.g., as indicated by an appointment calendar or other application) and provide content regarding points of interest or establishments in the vicinity of the user (or similarly, on or near a route between the user and a location associated with one or more scheduled appointments).
- a user may provide time-sensitive offers for nearby establishments to the user based on, for example, the user's available time prior to a scheduled departure time.
- device 10 may be configured to provide (e.g., deliver, trigger or initiate the delivery of, filter, etc.) content based on context data.
- the content may be provided in the form of a generic alert or notification (e.g., “Are you hungry?”, “Do you want to listen to music?”, “Would you like to try a new restaurant?”, “Would you like to visit one of your favorite restaurants?”, “Do you want to send an invite out to your friends?”, etc.) that when selected, directs a user to more specific data or information (e.g., “Lunch Special at Sam's Deli today”, etc.).
- a generic alert or notification e.g., “Are you hungry?”, “Do you want to listen to music?”, “Would you like to try a new restaurant?”, “Would you like to visit one of your favorite restaurants?”, “Do you want to send an invite out to your friends?”, etc.
- generic content may include content offering the best price for a certain item or service (e.g., “Looking for the best price for gas near you?”), or similarly, content offering to locate a preferred vendor, point of interest, etc., such as a gas station, fast food restaurant, coffee shop, etc. that, based on a user's current location, a given mode of transportation, and/or the hours of operation of the vendor or establishment, will still be open when the user arrives (e.g., “Looking for the nearest gas station?”).
- a preferred vendor, point of interest, etc. such as a gas station, fast food restaurant, coffee shop, etc. that, based on a user's current location, a given mode of transportation, and/or the hours of operation of the vendor or establishment, will still be open when the user arrives (e.g., “Looking for the nearest gas station?”).
- Other generic alerts may include offers to locate ATM machines or other computer terminal or user terminals (e.g., taking into account any additional fees charged by the ATM), public parking (e.g., taking into account hours of operation, pricing, etc.), lodging (e.g., taking into account vacancy, room rates, and other data regarding hotels, etc.), and so on.
- Various other types of generic alerts may be provided that take into account a wide variety of context data and other data (e.g., metadata associated with various establishments, etc.) in order to increase the relevancy of the content to users.
- context data may be stored in a variety of ways and utilizing a variety of storage devices and systems, such as in memory of a mobile device such as device 10 , using one or more servers that are separate from device 10 , using one or more servers that are associated with an ad service, an ad sponsor (e.g., a retailer, etc.), via a data storage system accessible via the Internet or another network system, and so on.
- ad service e.g., a retailer, etc.
- Other suitable means of storing context data may be used according various other embodiments.
- context data may be accessed (e.g., retrieved, monitored, stored, etc.) (step 62 ). Accessing context data may be done by processor 40 , servers 50 , 52 , or a combination thereof. As discussed above, accessing context data may include accessing or monitoring a wide variety of data either stored on device 10 or otherwise accessible by device 10 .
- content may be provided to device 10 (step 64 ).
- the content is provided in a generic format (e.g., as a generic notification or alert, etc.) and is not tied to any particular entity such as ad sources 54 , 56 , 58 , etc.
- the content may include a selectable link such that an input (e.g., a selection of the link) may be received by device 10 (step 66 ) in response to the content being provided.
- additional content may be provided to a user (e.g., more specific data, advertisement data, driving or other directions, etc.) (step 68 ).
- the additional content may include, for example, advertisement data from ad sources 54 , 56 , 58 , point of interest information (e.g., non-advertisement data or information about specific destinations, which may be in proximity to device 10 or in some other predetermined geographic location(s), a website, and so on).
- point of interest information e.g., non-advertisement data or information about specific destinations, which may be in proximity to device 10 or in some other predetermined geographic location(s), a website, and so on.
- Utilizing context data takes into consideration a user's context in triggering content such as generic notifications, advertisement data, and other content, and may enhance the quality of the content provided to users by increasing the relevancy of the content to the user in accordance with the user's context (e.g., location, current appointments, historical usage patterns, etc.).
- content may be provided based on time data and/or data from a personal information management application such as a calendar application. For example, at a predetermined time (e.g., a typical meal time such as lunch time, etc., a user-configurable time, a pre-set time, etc.), calendar data associated with device 10 may be accessed to determine, for example, whether a user has an appointment scheduled (e.g., a lunch appointment). If the user has no appointment scheduled, device 10 may be configured to provide the user with content such as a generic alert or notification (e.g., “Are you hungry?”, “Do you want to go out to eat?”, etc.).
- a generic alert or notification e.g., “Are you hungry?”, “Do you want to go out to eat?”, etc.
- the notification may include a selectable link or be otherwise selectable (e.g., via a touch screen or other input device), such that should the user select, for example, a link provided with the generic notification, device 10 may then provide more specific, additional content or information.
- the additional content may be any of a wide variety of content, including targeted advertisements (e.g., ads, e-coupons, discounts, etc. selected based on past user behavior, the location of the user, user-configurable preference data, etc.), an option to send out a notification to other users or mobile devices (e.g., an option to send out a lunch invitation to other mobile devices identified via a contacts application, a social networking application or listing, the location(s) of other users/devices, etc.), and so on.
- the process of providing progressively more specific data to device 10 in response to continued responses or other user inputs may be repeated as part of providing content to device 10 .
- content may be provided based upon the movement and/or location of device 10 .
- device 10 may be configured to, for example, determine when a user has left a building or similar environment, which may in turn trigger the delivery of content to the user (e.g., “Need directions?”, etc.).
- device 10 may further take into account a direction of travel (e.g., via an integrated compass, etc.), a speed of travel (e.g., via a GPS system, accelerometer, etc.), and so on.
- the content provided to the user may vary based on what points of interest are in the general direction of travel of device 10 , based on a predicted mode of travel (e.g., walking, driving, etc.) determined based upon the speed of travel, based on calendar appointment data (e.g., by knowing where a user may be going based upon appointment data), and so on.
- a predicted mode of travel e.g., walking, driving, etc.
- calendar appointment data e.g., by knowing where a user may be going based upon appointment data
- content may be provided to additional devices based on inputs associated with, or content provided to, device 10 .
- content such as an advertisement may be provided to a user via display 18 of device 10 .
- a user may select the advertisement in order to navigate to, for example, a web site hosted by the source of the advertisement.
- additional content may automatically be provided to additional devices (e.g., additional mobile devices identified in a social network listing, etc.).
- additional devices e.g., additional mobile devices identified in a social network listing, etc.
- the same or a similar advertisement may be provided to a group of users that are in a contacts application of the user, users that may be identified based upon some type of social networking grouping or listing (e.g., via being identified as “friends,” contacts,” etc.
- social network listings may include email listings (e.g., personal or professional listings or groups, such as a marketing group of a business, a sales team, etc.) a class list for a particular academic institution and/or year, a sports team (e.g., a school and/or youth sports team, etc.) and/or other social network listings that may be more or less permanent/temporary in nature.
- email listings e.g., personal or professional listings or groups, such as a marketing group of a business, a sales team, etc.
- a class list for a particular academic institution and/or year e.g., a sports team (e.g., a school and/or youth sports team, etc.) and/or other social network listings that may be more or less permanent/temporary in nature.
- display 18 is shown according to various exemplary embodiments as including content provided to a user.
- content such as generic notifications, advertisement data, etc.
- content may include or be provided in the form of a selectable link or identifier 80 (e.g., an icon, selectable text or graphics, etc.).
- Link 80 may be an icon with a graphical representation intended to convey a message to a user (e.g., such as an icon with a graphical representation of a map that is associated with driving directions, etc., and so on).
- Icon 80 may be sized such that it is relatively smaller than one or more other icons or identifiers (e.g., icons or other identifiers associated with applications, files, etc.
- icon 80 may be provided as part of a status or notification bar or area 74 on display 18 .
- the content or icon and notification or status bar may be provided in any of wide variety of locations on display 18 , including a bottom portion (see icon 80 and notification bar 74 ), a side portion (see notification bars 72 , 76 ), or a top portion (see notification bar 70 ).
- an application developer e.g., a developer associated with one of servers 50 , 52
- icon 80 may be provided in other areas or portions than those shown in FIG. 7 .
- Additional content 84 may include a generic notification or message, advertisement data from an ad source (e.g., one or more of ad sources 54 , 56 , 58 , etc.), non-advertisement data, etc.
- icon 80 may include a representation of a map.
- additional content 84 may include a generic notification or question such as “Do you need directions?”.
- Additional content 84 may include a selectable link that enables a user to select additional content 84 .
- the user may be provided with yet further content 86 .
- content 86 may include driving directions, a list of popular destinations for a user (which may be selectable to provide even further content), and so on.
- the content provided may continue to increase in size or prominence (e.g., as shown with the increasing relative sizes of icon 80 , additional content 84 , and content 86 ).
- the amount of content provided may increase as a user continues to engage the content provided.
- the specificity of the content may increase as a user becomes more engaged (e.g., from generic to greater levels of specificity).
- a user may be permitted to interact (e.g., enter into transactions, make reservations, provide and/or receive contact information, etc.) with various entities associated with the content provided to device 10 .
- additional content e.g., additional content such as additional content 84 shown in FIG. 8
- a user may be permitted to, for example, make dinner reservations (including automatically making an appointment in a calendar application), enter into transactions such as paying for a dinner, etc., exchange contact data with ad sources and other entities, and so on.
- the systems and methods described herein may be implemented to provide data to a wide variety of mobile devices that may take a wide variety of forms (e.g., differing form functions, etc.) and have a wide variety of functional capabilities such as visual display capabilities, input/output capabilities (e.g., touch screen, non-touch screen devices, etc.), audible output capabilities, etc.
- the content provided to device 10 may be formatted based on the characteristics or capabilities of device 10 .
- device 10 may be configured to receive the content and perform such formatting based on data stored on device 10 , accessible via device 10 , provided as part of the content itself (e.g., as embedded data or formatting instructions) and so on.
- the formatting may further be performed for a wide variety of devices (e.g., a handheld device, a relatively smaller-sized device such as a watch, etc., a relatively larger-sized device such as a television, etc.), and so on.
- device 10 may be configured to provide and/or format content such as advertisements etc. as sessions change (e.g., as an application moves through different modes or states such as downloading, launch, a ready/usage state, ending/shut-down, etc.).
- a user may download an application to device 10 , during which content may be provided in the form of, for example, dynamic and/or static ads, sponsorships, etc.
- an initial “splash screen” e.g., a screen or page provided to the user while an application is launched
- a “ready” state e.g., ready to be used by the user
- one or more interstitial pages may be provided with further content. Similar content may be provided as the application is closed or shut down.
- certain display portions or areas may be dedicated to content such as advertisements on a permanent or temporary basis.
- device 10 may provide users with alerts or other notifications that include relevant content such as advertising or other data.
- content such as sponsored links or logos, etc. may be provided in connection with various search queries.
- certain content provided by device 10 may include brand information such as logos, etc.
- a system and method for performing a function based on past uses of a mobile computing device or behaviors of a user of the mobile computing device will be described.
- One or more components of the system and method may be operable as an algorithm on the mobile computing device, on a server computer in communication with the mobile computing device, or on another computing device in communication with the mobile computing device.
- a memory is configured to store use data indicative of a pattern of past uses of the mobile computing device.
- the memory may store the data temporarily and then back up the data to a remote server, may receive the data from a remote server configured to monitor and store use data, or may store the use data for a longer period.
- the use data can represent a past behavior of a user of the device.
- the use data may be retrieved or determined based on data from one or more sources operating on the mobile computing device or remote from the computing device, such as a location determination circuit, a time of day clock, a source of a date and day of the week, a database of geographic points of interest (e.g., location and extent of a parking lot, restaurant, bridge, gas station, etc.), a mass transit schedule database or other database stored on a remote server, a phone call log, an application store available on a remote server for downloading new software applications, an on-line reservation system for a restaurant, train, etc., a wireless transceiver circuit configured to receive wireless signals (e.g., radio frequency, infrared, etc.) from nearby or remote devices, metadata for one or more audio music files recently played by the user, textual input from a user entered via a keyboard or data from any other application operating on the mobile computing device, such as a calendar application, contacts application, phone application, notes application, task list application, gaming application, music and/or video player application, etc.
- a pattern of past uses may comprise a plurality of past uses of the mobile computing device, based on any of the use data described herein.
- the system is configured to determine or detect a present condition, situation, or context of the mobile computing device and/or user thereof.
- the present condition may be one which is currently applicable, or recently applicable, to the device (e.g., detecting that the mobile device has just passed a point of interest may be a present condition for some period of time).
- the present condition may be retrieved or determined based on data from one or more sources operating on the mobile computing device or remote from the computing device, such a traffic data available from a remote site (e.g., such as Google Maps), a calendar application, a date and/or time of day source, a location determination circuit, a source of geographic point of interest data, an application store available on a remote server for downloading new software applications, user inputs, a time counter configured to detect the passage of one or more predetermined periods of time, a distance counter configured to detect a traveled distance, a navigation application configured to determine a route traveled, a wireless transceiver circuit configured to receive wireless signals from nearby or remote devices, or other data sources.
- a traffic data available from a remote site (e.g., such as Google Maps)
- a calendar application e.g., such as Google Maps
- a date and/or time of day source e.g., such as Google Maps
- a location determination circuit e.g., such as Google Maps
- the mobile computing device may be configured to perform a function based at least on the use data and the present condition.
- the function comprise generating a notification to the user, such as by displaying a message, alert, textual data, etc. in a window, full screen, etc., and/or by providing an audible alert, such as a beep, series of beeps, playing an audio file, etc and/or by vibrating or providing other outputs to the user.
- the function may further comprise performing operations within other applications operable on the mobile computing device, such as adding a resource locator link and/or identifier to a “favorites” or bookmark list in a browser application, adding a phone number to a list of frequently called numbers, etc.
- the function may further comprise delaying a function to be performed, such as delaying a download of data or a synchronization operation.
- the function may further comprise downloading a program from a server computer, filtering a list of potential files to be downloaded to present a subset of the list to the user for selection, running a search on a local or remote geographic information database, calculating a route using a navigation or mapping application, etc.
- the function may further comprise sending wireless data to a remove device containing a command, request, alert, or other data.
- processing circuits programmed with algorithms for tracking a user's behavior and performing functions based on the past experience or historical knowledge of the user.
- the algorithms may be operable on processing circuitry on the mobile computing device, a server computer, or portions of the algorithm on both a mobile device and a server computer.
- the algorithms may be operable to predict one or more functions the user may wish to perform with the device based on the past experience or historical usage of the device and may be configured to perform the one or more functions based on one or more present conditions, such as a triggering event or occurrence.
- the mobile device may be configured to suggest a function and await user confirmation (e.g., via pressing a key, speaking into a microphone on the device, etc.) or may be configured to perform the function without awaiting user confirmation.
- a processing circuit may be configured to generate an alarm to wake up a user at a time earlier than a predetermined typical wake-up time based on a present condition of data from a traffic report indicating traffic is worse than usual along a predetermined traveling route.
- the processing circuit may be configured to determine based on time of day and location based signals collected over a plurality of days the predetermined traveling route.
- the processing circuit may further be configured to store data indicative of typical or average traffic conditions at one or more points along the route.
- the mobile device may be configured to receive a user selection of an alarm time.
- the processing circuit may be configured at some predetermined time period prior to the selected alarm time to receive current traffic data along the predetermined traveling route, calculate or retrieve from memory a time period, subtract the time period from the user-selected alarm time, and then program the mobile device to provide the alarm at the new time.
- the processing circuit may be configured to determine when the mobile device arrives at a location (e.g., a place of work) and to suggest a new alarm or wake-up time based on one or more previous commute times stored by the processing circuit to assist the user in arriving at work more reliably at a predetermined time. For example, if the processing circuit detects the user repeatedly arrives at 8:05 AM and has an alarm set to 6:30 AM, the processing circuit may determine that the user intends to arrive at work at 8:00 AM and to suggest the user switch the alarm time to 6:25 AM.
- the processing circuit may be configured to learn over a period of days or weeks where a user will be located with the device at a given time (e.g., during a commute, during lunch, etc.) based on past experience and to predict a function needed by the user at a present or future time based on the data indicative of past experience or behavior.
- the mobile device may be configured to receive certain data to replace or supplement the use data or past experience data, such as a desired lunch time, a commute route, current location, etc.
- a processing circuit may be configured to monitor the presence and/or signal strength of wireless networks at locations along a route, such as a frequently traveled route, such as a commute route or weekend vacation route.
- the processing circuit may be configured to store one or more locations at which a wireless signal becomes weaker or unavailable (e.g., “dead spots”, weak spots, etc.).
- the mobile device may be configured to notify a user via an alert or other alarm that a dead spot is approaching.
- the device may further be configured to suggest other available networks for a handoff of a wireless communication session, such as a voice or data session, which may be a handoff to a cellular network of a different carrier, to a Wi-Fi access point, etc.
- the data of other wireless networks may be stored in a memory from previous data collected by the mobile device along the route or may be retrieved from a commercially-available database of network data accessible on a server computer (e.g., a database offered by Boingo Wireless, Inc., Los Angeles, Calif.).
- the processing circuit may be configured to store present and/or signal strength of wireless networks at any location, regardless of any route data.
- the processing circuit may further obtain such data via download from a server.
- the processing circuit may be configured to change the behavior of the phone based on knowledge of the level or quality of wireless connectivity the device will have in certain locations.
- the device may be configured to delay a wireless download and/or upload operation until the device reaches the Wi-Fi network.
- This feature may be useful for downloading software updates to the mobile device, software patches or new versions of software, or other data to be communicated wirelessly.
- the processing circuit may be configured to schedule wireless communications based on predictions of where the device will be at times of the day (e.g., based on a current route, projected route, location and time data from prior days (e.g., the mobile device is home after 6 pm each night for a plurality of nights in communication with a Wi-Fi network with a suitable signal strength), or other based on other characteristics).
- a processing circuit may be configured to store user preferences or rankings associated with locations and/or types of events previously attended.
- the device may be configured to alert the user that the user previously indicated they did not want to visit these types of events or locations.
- the processing circuit may also receive current traffic data and further provide the alert based on the current traffic data to suggest that the user may not want to attend the event because of traffic.
- the processing circuit may be configured to learn what not to do based at least in part on things previously done with the device and optionally also in response to a user ranking or assessment of the location or event.
- a processing circuit may be configured to store a plurality of user-selectable time zones in a list based on locations previously visited by the mobile device.
- the mobile device may be configured to learn a time zone of a person associated with a contact in an contacts location based on the user of the mobile device traveling to visit the person. The time zone may be stored in the contact data file.
- the mobile device may be configured to generate an alert for the user if the user initiates a telephone call to the contact and a time of day source indicates that based on the time zone, the time may be received by the contact at an inconvenient time, such as after and/or before a predetermined time of day, as indicated by a time of day source and the time zone associated with the contact.
- the contacts application may be configured to display data indicative of a time of day at the contact's location based on time of day data and the time zone associated with the contact.
- a processing circuit may be configured to store data indicative of where the mobile device has traveled to, such as a foreign country, outside of a home state (as determined based on use data indicating past location), etc.
- the processing circuit may then be configured to download applications or suggest applications for download to the user based on the data indicative of where the mobile device has traveled to. For example, if the device has recently traveled to a foreign country, the device may be configured to identify one or more applications relating to the foreign country available for download from a remote server or items available for purchase (e.g., a French/English dictionary, a currency exchange application, etc.) and to notify the user of the availability of such applications or items (e.g., a travel book).
- the recently-traveled data may be used as a filter for an application store or other function of the device or a server in communication with the device.
- the recently-traveled data may further comprise frequency of travel data or number of travel events data, to distinguish a location infrequently visited from one frequently visited, which data may further be used to filter applications for download or items for purchase. For example, if a user frequently travels to France, the mobile device may be configured to suggest downloading applications operable or items written in the French language instead of English language.
- a processing circuit may be configured to store metadata associated with one or more applications downloaded from a remote server. The processing circuit may then be configured to filter applications available for download or items available for purchase based on one or more of the metadata items. For example, if a user frequently downloads gaming applications, the processing circuit may detect a user request to access an application store at a server and, in response, the processing circuit may be configured to filter a set of applications available for download based on the frequent-download data and to present to the user one or more or only gaming applications. According to yet another embodiment, the processing circuit may be configured to filter applications for download based on applications that are downloaded and frequently used (or recently used), to further reduce the number of applications to be viewed by the user of the mobile computing device.
- the processing circuit may be configured to store data indicating the mobile device has been used at or in association with a restaurant or other dining location.
- the use data may comprise data indicating that a dinner reservation has been made using the mobile device and dinner reservation web site, that a phone call has been placed to the restaurant, that the device has entered the restaurant based on location data, that the device has been used to make a purchase at the restaurant, such as with a near-field communication device or other transaction processing circuit, etc.
- the processing circuit may be configured to store data about the restaurant along with data about other restaurants similarly gathered.
- the processing circuit may be configured to determine that a user may presently wish to review restaurant suggestions, which may be determined based on time of day (e.g., lunch time, dinner time, etc.), based on a user request to review restaurants suggestions, or based on other present conditions.
- the processing circuit may then function to generate one or more restaurant or dining location suggestions based on the prior use data and to present the one or more restaurant suggestions to the user, optionally along with location, web site, phone number, mapping, reviews, and/or other data about the restaurant.
- the processing circuit may be configured to suggest a new dish for the user to try, based on dish data received from the restaurant or from a server configured to store dishes recommended by other patrons or by friends in a friend list stored by the mobile device.
- a processing circuit may be configured to identify one or more gas stations at which a user of a mobile device has recently or frequently fills up their car with gas.
- the processing circuit may identify the gas station based on one or more of location data, point of interest information (e.g., comprising a location of a gas station and data indicating the point of interest is a gas station), a period of time between visits to the gas station and/or other gas stations (which may indicate whether the gas station was visited for a gas purchase or for a non-gas purchase), transaction data indicating the mobile device was used to make a transaction to purchase gas (e.g., using a near-field communication device or other transaction circuit), or other data.
- point of interest information e.g., comprising a location of a gas station and data indicating the point of interest is a gas station
- a period of time between visits to the gas station and/or other gas stations which may indicate whether the gas station was visited for a gas purchase or for a non-gas purchase
- transaction data indicating the
- the processing circuit may then be configured to determine a present condition, such as a present location of the device approaching or located at the gas station, a predetermined period of time having passed and/or distance having been traveled at vehicle speeds since the last gas fill-up (e.g., which may indicate that the user's vehicle will soon be in need of fuel), the user traveling near a second gas station selected as described below, and/or other present conditions (e.g., a user turning on the device).
- a present condition such as a present location of the device approaching or located at the gas station, a predetermined period of time having passed and/or distance having been traveled at vehicle speeds since the last gas fill-up (e.g., which may indicate that the user's vehicle will soon be in need of fuel), the user traveling near a second gas station selected as described below, and/or other present conditions (e.g., a user turning on the device).
- the processing circuit may be configured to perform one or more of the following functions based on the identified gas stations and present condition: perform a search of a remote web site for nearby gas stations offering a lower price on gas (e.g., which may include a special, coupon, etc.), present an alert to the user comprising information about the lower price and location, provide directions, a map, or other data about the gas stations offering the lower price.
- a search of a remote web site for nearby gas stations offering a lower price on gas e.g., which may include a special, coupon, etc.
- present an alert to the user comprising information about the lower price and location, provide directions, a map, or other data about the gas stations offering the lower price.
- a processing circuit may be configured to present advertisements to a user via the user's mobile computing device based on past usage data of the mobile computing device, such as a past location (e.g., a point of interest recently visited, a point of interest frequented or visited a plurality of times in a predetermined time period, etc.).
- a past location e.g., a point of interest recently visited, a point of interest frequented or visited a plurality of times in a predetermined time period, etc.
- a processing circuit may be configured to receive a user request for a point of interest or other retail location, which may be provided generically by the user (e.g., a barber, a dry cleaner, a book store, a restaurant, etc.) and may include additional criteria about the point of interest to be found (e.g., a predetermined rating level, such as at least two stars, a price range, etc.).
- the processing circuit may be configured to identify one or more points of interest meeting the criteria provided by the user based further on location data representative of a route previously or frequently traveled by the user in the past (e.g., a daily commute).
- the processing circuit may be configured to identify one or more points of interest along the route, near a point on the route, or closer than other points to the route, and to present the points of interest to the user, such as in an alert, on a map, etc.
- This functionality may be operated from within a task list or notes application operable on the mobile device, to assist the user in completing a task entered by the user (e.g., “get a haircut,” “drop off drycleaning,” etc.).
- a processing circuit may be configured to store use data from a telephone call log (e.g., phone numbers, times of calls, persons called incoming our outgoing, etc.).
- the processing circuit may be configured to perform functions based on the telephone call log information and any present condition. For example, if the processing circuit determines that phone calls have been made to Chinese restaurants (e.g., recently, frequently, exclusively, etc.), which may be based on data from the call log and/or data from a web site or other server configured to provide additional data to supplement data from the call log, the processing circuit may be configured to determine and/or store a preference for Chinese restaurants.
- a present condition such as a time of day representing a typical time to eat (e.g., noon, 6 pm, etc.), a typical time to eat for the user based on previous times during which the user has eaten (e.g., based on calendar data, location data, reservations made using the mobile device, dining transactions made using the mobile device, periodic eating at a particular restaurant (e.g., every Monday is Chinese food day), etc.)
- the processing circuit may be configured to provide a function of alerting or suggesting to the user a restaurant or nearby restaurant based on the data (in this case, a Chinese restaurant), or to prompt the user to confirm placing a phone call to a favorite restaurant to place an order or make a reservation.
- the mobile device may be configured to store preferred menu items and to transfer the menu items as an order to the restaurant through a web site, text message, etc. at a predetermined time and in response to user confirmation to place the order.
- the mobile device may be configured to prompt the user (e.g., “the usual?”).
- the processing circuit may be configured to store data representative of a mass transit service (e.g., bus, train, flight, etc.) used or frequently used by a user of the mobile device.
- the data may be stored based on location data indicating travel along a mass transit route (e.g., a train track or rail line), typically a plurality of times to indicate a pattern or frequency of travel.
- the processing circuit may then be configured to retrieve data indicating a delay or cancellation in the mass transit route typically traveled, which may be a present condition.
- the processing circuit may be configured to alert the user of the mobile device as to the delay or cancellation.
- the processing circuit may be configured to determine that the mobile device has traveled along two or more different routes, at least one of which has been traveled a plurality of times indicating some frequency or regularity of the travel route.
- the processing circuit may be configured to determine a present traffic condition and, based on the present traffic condition and past route data, display a recommendation to the user as to which of the two or more different routes to travel.
- the processing circuit may be configured to determine that the mobile device has repeatedly traveled a first route, that an alternative route is available which may be a better route for one or more reasons (e.g., shorter travel time, less traffic, less uncertainty due to potential traffic issues, shorter travel distance, the route goes near a point of interest determined to be of interest to the user, etc.).
- a processing circuit may be configured to store data indicating a preferred parking lot, such as in an urban setting, at an airport, etc.
- the preferred or historical parking lot data may be used by the processing circuit to provide an indication the user that the preferred parking lot is full, closed, etc., using data from a web server monitoring the parking lot capacity and status.
- the processing circuit may provide the indication in response to determining that the user is approaching the parking lot.
- a processing circuit may be configured to store data indicative of prior music files played by the mobile device and one or more elements of metadata about the prior music files, frequency of playing each music file, date of download or stored on the mobile device, etc. Based on one or more of this data, the processing circuit may be configured to search for additional music files for potential download, using similar styles, artists, genre, etc., and to suggest the additional music files to the user. The processing circuit may further be configured to search for concerts coming to town based on historical music file data, recent location data of the device, determined musical tastes, etc. and to provide an alert to the user of the concert coming to town, for example with a text or e-mail message containing a link for the user to click on to see concert information, order tickets, etc.
- the processing circuit may be configured to determine a home location from an address data stored in a contact for oneself, based on data indicating the mobile device returns to that location every night or otherwise daily, or based on other data.
- the processing circuit may then be configured to determine when the mobile device is approaching the home (e.g., a predetermined distance or time away from the home), based on determining that the mobile device has traveled certain points along a previously-traveled route home, and to provide a wireless message to a system in the home or to another mobile or fixed computing system based on the determination that that the device is approaching or nearing the home.
- the mobile device may be configured to send a message to the home control system to control one or more of the systems (e.g., disable or check security system, turn on lights, unlock doors, etc.).
- the mobile device may be configured to send a text message to another mobile device (e.g., a spouse's or other family members' mobile device) to advise them that the user is nearing home (e.g., “dad will be home in about 5 minutes,” etc.).
- the message may be based on approaching another location or system other than the home, such as a vehicle, and may further be based on data indicating the mobile device is moving away from another location or system, such as a shopping mail.
- the mobile device may send a message to the vehicle (e.g., directly via Bluetooth or other short-range wireless network, or indirectly via a cellular or Wi-Fi network) to command the vehicle to unlock the doors, release the trunk door, and/or remote start the vehicle.
- the processing circuit may be configured to detect a use of the mobile device, such as visiting a web site (or visiting it frequently or a plurality of times in a predetermined time period), making a phone call (or calling a particular number frequently or a plurality of times in a predetermined time period), etc.
- the processing circuit may be configured to perform a function based on the detected use, such as adding a bookmark, favorite, or link to a list of such favorites in a web browser application, wherein the link is associated with the web site visited.
- a phone number may be added to a speed dial list (e.g., having a predetermined number or number sequence associated with it shorter than the phone number, having an icon which can be tapped, such as with a photo of the person associated with the phone number, etc.) based on the phone call data.
- the processing circuit may be configured to display an alert based on a frequently-called person approaching the mobile device, may display a map showing their location, etc.
- the processing circuit may be configured to determine that another mobile device is typically detected in the proximity of the mobile device at a predetermined time each day or on certain days and that the device has not been detected in proximity. The processing circuit may then be configured to prompt the user to phone or contact the mobile device of the other person.
- One use of this embodiment may be at a construction site where one or more workers are expected to be located at the site at a predetermined time and a mobile device monitors the locations of the mobile devices of the workers to confirm they have arrived, and to send a communication to the other mobile devices which have not yet arrived (e.g., a text message, phone call, etc.).
- the expected time of arrival and devices expected may be received via manual input from a user or may be detected based on prior history at the work site and stored in a memory on the mobile device or a server in communication therewith.
- the processing circuit may be configured to determine use data based on when the device is turned on or off (or allowed to power off) by a user. For example, if the processing circuit determines that the device is typically powered off after 10 PM and night powered on until 5 AM, the processing circuit may be configured to schedule or delay certain wireless download, synchronization, virus scan, or other operations until the time of after 10 PM and/or before 5 AM. The device may further be configured to stop certain operations initiated before a predetermined time period based on an expectation that the user will turn on and use the device, again based on data stored regarding prior usage of the device.
- the processing circuit may be configured to determine that the mobile device is located at a work location and may be configured (automatically or in response to a user request) to stop, delay, or cease synchronization of data, such as e-mails, based on an assumption that the user will be handling e-mail communications from a laptop or desktop computer while at work or while at a particular location of work (e.g., the desk versus the lab). Battery life of the mobile device may be conserved using such a feature.
- a processing circuit is configured to determine that the mobile device is located in a city, state, country or other geographic location not previously visited by the device (or not previously detected by the program operating the feature). Alternatively, the processing circuit may determine that the mobile device is located at a hotel or other lodging point and to determine that the mobile device may want additional data based on the fact that the user is staying at a hotel. The processing circuit may be configured to prompt the user to indicate whether the user is traveling for business or pleasure. The processing circuit may then be configured to provide data indicative of local points of interest and/or events (e.g., things to do, restaurants, attractions, events, etc.) based on the determination and/or collected user input. The processing circuit may be configured to provide restaurant, entertainment, local history, news, or other data to the user based on the determination and/or collected user input.
- the processing circuit may be configured to provide restaurant, entertainment, local history, news, or other data to the user based on the determination and/or collected user input.
- the mobile device may be configured to operate a clock application.
- a processing circuit may be configured to determine a home time and local times for places visited or commonly visited, based on use data (e.g., where the device is used, for how long the device is used at each location, etc.), and to store these times in the clock application. Any of the functions described herein may then be performed based at least in part on the time information.
- a processing circuit may be configured to determine times of the day during which a user of a mobile device is typically at work. For example, the device may receive a user selection or input of a work location, or the processing circuit may determine a work location based on a location the device is typically at for a significant portion of a day, estimating based on typical work hours in any one of a plurality of different shifts. The processing circuit may then be configured to determine whether an appointment in a calendar application is scheduled for a time that the user is not typically at work, and may be configured to provide additional reminders or alerts of the meeting beyond a reminder or alert that would typically be provided for a meeting scheduled during typical work hours.
- the reminders may be greater in number, may use more output devices (e.g., display, speaker, vibration, phone call to home, instant message or text message to second computing device, etc.), may be earlier (e.g., more than an hour before the meeting), may be provided during typical work hours regardless of the time of the meeting, etc.
- output devices e.g., display, speaker, vibration, phone call to home, instant message or text message to second computing device, etc.
- may be earlier e.g., more than an hour before the meeting
- devices 10 may be implemented on or via device 10 , via one or more of servers 50 , 52 (e.g., a server associated with an ad service, etc.), or via other devices/components and any combination(s) thereof, and all such combinations are deemed to be within the scope of the present disclosure.
- One or more of device 10 and/or servers 50 , 52 may serve as a “content manager” or “offer manager” to manage, trigger, filter, and/or otherwise control the delivery of content (e.g., advertisements, offers, etc.) to device 10 .
- References to a processing circuit may include use of multiple processing circuits, such as one operable on a mobile device and one operable on one or more server computers.
- Various embodiments disclosed herein may include or be implemented in connection with computer-readable media configured to store machine-executable instructions therein, and/or one or more modules, circuits, units, or other elements that may comprise analog and/or digital circuit components configured or arranged to perform one or more of the steps recited herein.
- computer-readable media may include RAM, ROM, CD-ROM, or other optical disk storage, magnetic disk storage, or any other medium capable of storing and providing access to desired machine-executable instructions.
Abstract
Description
- The present application claims the benefit of U.S. Provisional Application No. 61/140,562, filed Dec. 23, 2008, which is incorporated herein by reference in its entirety.
- The present disclosure relates generally to the field of mobile devices, and more specifically, to systems and methods for performing functions based on past uses of a device or behaviors of a user of the device.
-
FIG. 1 is a front view of a mobile device according to an exemplary embodiment. -
FIG. 2 is a back view of the mobile device ofFIG. 1 according to an exemplary embodiment. -
FIG. 3 is a side view of the mobile device ofFIG. 1 according to an exemplary embodiment. -
FIG. 4 is a block diagram of the mobile device ofFIG. 1 according to an exemplary embodiment. -
FIG. 5 is a block diagram of a system for providing content to a mobile device according to an exemplary embodiment. -
FIG. 6 is a flow chart of a method of providing content to a mobile device according to an exemplary embodiment. -
FIG. 7 is a front view of a display of a mobile device according to an exemplary embodiment. -
FIG. 8 is a front view of a display of a mobile device according to an exemplary embodiment. -
FIG. 9 is a front view of a display of a mobile device according to an exemplary embodiment. -
FIG. 10 is a flowchart of a system and method for performing a function based on use data and a present condition, accordingly to an exemplary embodiment. - Referring to
FIGS. 1-3 , amobile device 10 is shown. The teachings herein can be applied todevice 10 or to other electronic devices (e.g., a desktop computer), mobile computing devices (e.g., a laptop computer) or handheld computing devices, such as a personal digital assistant (PDA), smartphone, mobile telephone, personal navigation device, etc. According to one embodiment,device 10 may be a smartphone, which is a combination mobile telephone and handheld computer having PDA functionality. PDA functionality can comprise one or more of personal information management (e.g., including personal data applications such as email, calendar, contacts, etc.), database functions, word processing, spreadsheets, voice memo recording, Global Positioning System (GPS) functionality, etc.Device 10 may be configured to synchronize personal information from these applications with a computer (e.g., a desktop, laptop, server, etc.).Device 10 may be further configured to receive and operate additional applications provided todevice 10 after manufacture, e.g., via wired or wireless download, SecureDigital card, etc. - As shown in
FIGS. 1-3 ,device 10 includes ahousing 12 and afront side 14 and aback side 16.Device 10 further comprises adisplay 18 and a user input device 20 (e.g., a QWERTY keyboard, buttons, touch screen, speech recognition engine, etc.).Display 18 may comprise a touch screen display in order to provide user input to a processor 40 (seeFIG. 4 ) to control functions, such as to select options displayed ondisplay 18, enter text input todevice 10, or enter other types of input.Display 18 also provides images (see, e.g.,FIG. 7 ) that are displayed and may be viewed by users ofdevice 10.User input device 20 can provide similar inputs as those oftouch screen display 18.Device 10 can further comprise aspeaker 26, and astylus 30 to assist the user in making selections ondisplay 18.Display 18 may comprise a capacitive touch screen, a mutual capacitance touch screen, a self capacitance touch screen, a resistive touch screen, a touch screen using cameras and light such as a surface multi-touch screen, proximity sensors, or other touch screen technologies, and so on.Display 18 may be configured to receive inputs from finger touches at a plurality of locations ondisplay 18 at the same time.Display 18 may be configured to receive a finger swipe or other directional input, which may be interpreted by a processing circuit to control certain functions distinct from a single touch input. - According to an exemplary embodiment,
housing 12 is configured to hold a screen such asdisplay 18 in a fixed relationship above a user input device such asuser input device 20 in a substantially parallel or same plane. This fixed relationship excludes a hinged or movable relationship between the screen and the user input device (e.g., a plurality of keys) in the fixed embodiment. -
Device 10 may be a handheld computer, which is a computer small enough to be carried in a hand of a user, comprising such devices as typical mobile telephones and personal digital assistants, but excluding typical laptop computers and tablet PCs. The various input devices and other components ofdevice 10 as described below may be positioned anywhere on device 10 (e.g., the front surface shown inFIG. 1 , the rear surface shown inFIG. 2 , the side surfaces as shown inFIG. 3 , etc.). Furthermore, various components such as a keyboard etc. may be retractable to slide in and out from a portion ofdevice 10 to be revealed along any of the sides ofdevice 10, etc. - According to various exemplary embodiments,
housing 12 may be any size, shape, and have a variety of length, width, thickness, and volume dimensions. For example,width 13 may be no more than about 200 millimeters (mm), 100 mm, 85 mm, or 65 mm, or alternatively, at least about 30 mm, 50 mm, or 55 mm.Length 15 may be no more than about 200 mm, 150 mm, 135 mm, or 125 mm, or alternatively, at least about 70 mm or 100 mm.Thickness 17 may be no more than about 150 mm, 50 mm, 25 mm, or mm, or alternatively, at least about 10 mm, 15 mm, or 50 mm. The volume ofhousing 12 may be no more than about 2500 cubic centimeters (cc) or 1500 cc, or alternatively, at least about 1000 cc or 600 cc. - Referring now to
FIG. 4 ,device 10 comprises aprocessing circuit 46 comprising aprocessor 40.Processor 40 can comprise one or more microprocessors, microcontrollers, and other analog and/or digital circuit components configured to perform the functions described herein.Processor 40 may comprise one or more memories (e.g., random access memory, read only memory, flash, etc.) configured to store software applications provided during manufacture or subsequent to manufacture by the user or by a distributor ofdevice 10. In one embodiment,processor 40 can comprise a first applications microprocessor configured to run a variety of personal information management applications, such as email, a calendar, contacts, etc., and a second, radio processor on a separate chip or as part of a dual-core chip with the application processor. The radio processor may be configured to operate telephony functionality.Device 10 can be configured for cellular radio telephone communication, such as Code Division Multiple Access (CDMA), Global System for Mobile Communications (GSM), Third Generation (3G) systems such as Wide-Band CDMA (WCDMA), or other cellular radio telephone technologies.Device 10 can further be configured for data communication functionality, for example, via GSM with General Packet Radio Service (GPRS) systems (GSM/GPRS), CDMA/1XRTT systems, Enhanced Data Rates for Global Evolution (EDGE) systems, Evolution Data Only or Evolution Data Optimized (EV-DO), and/or other data communication technologies. -
Device 10 comprises areceiver 38 which comprises analog and/or digital electrical components configured to receive and transmit wireless signals viaantenna 22 to provide cellular telephone and/or data communications with a fixed wireless access point, such as a cellular telephone tower, in conjunction with a network carrier, such as, Verizon Wireless, Sprint, etc.Device 10 can further comprise circuitry to provide communication over a local area network, such as Ethernet or according to an IEEE 802.11x standard or a personal area network, such as a Bluetooth or infrared communication technology. -
Device 10 further comprises a microphone 36 (seeFIG. 2 ) configured to receive audio signals, such as voice signals, from a user or other person in the vicinity ofdevice 10, typically by way of spoken words. Alternatively or in addition,processor 40 can further be configured to provide video conferencing capabilities by displaying ondisplay 18 video from a remote participant to a video conference, by providing a video camera ondevice 10 for providing images to the remote participant, by providing text messaging, two-way audio streaming in full- and/or half-duplex mode, etc. -
Device 10 further comprises a location determining application, shown inFIG. 3 asGPS application 44.GPS application 44 can communicate with and provide the location ofdevice 10 at any given time.Device 10 may employ one or more location determination techniques including, for example, Global Positioning System (GPS) techniques, Cell Global Identity (CGI) techniques, CGI including timing advance (TA) techniques, Enhanced Forward Link Trilateration (EFLT) techniques, Time Difference of Arrival (TDOA) techniques, Angle of Arrival (AOA) techniques, Advanced Forward Link Trilateration (AFTL) techniques, Observed Time Difference of Arrival (OTDOA) techniques, Enhanced Observed Time Difference (EOTD) techniques, Assisted GPS (AGPS) techniques, hybrid techniques (e.g., GPS/CGI, AGPS/CGI, GPS/AFTL or AGPS/AFTL for CDMA networks, GPS/EOTD or AGPS/EOTD for GSM/GPRS networks, GPS/OTDOA or AGPS/OTDOA for UMTS networks), triangulation techniques such as Wi-Fi triangulation techniques, and so forth. -
Device 10 may be arranged to operate in one or more location determination modes including, for example, a standalone mode, a mobile station (MS) assisted mode, and/or an MS-based mode. In a standalone mode, such as a standalone GPS mode,device 10 may be arranged to autonomously determine its location without real-time network interaction or support. When operating in an MS-assisted mode or an MS-based mode, however,device 10 may be arranged to communicate over a radio access network (e.g., UMTS radio access network) with a location determination entity such as a location proxy server (LPS) and/or a mobile positioning center (MPC). -
Device 10 further comprises amemory 42 coupled to or as part ofprocessor 40.Memory 42 may store a variety of data (e.g., context data, etc.) such as information, data, applications, files, etc. that may be used or accessed usingdevice 10. For example, calendar data may include data regarding various appointments such as location data (e.g., an individual's residence, a commercial establishment, an address or other geographic indicator such as a city, state, etc., a conference room number, and so on), time/date data (e.g., a date and/or time for a specific appointment, data regarding a recurring appointment, etc.), attendee data, and other data related to an appoint or meeting. Contacts data may include information regarding specific contacts, such as names, addresses, phone numbers, email addresses, fax numbers, and contact-specific notes (e.g., notes about the specific contact such as a birthday, anniversary, etc.). Messaging data may include information related to a variety of messaging applications including email, text messaging, short message service (SMS), and so on. According to various other exemplary embodiments,device 10 may utilize other context data in accordance with the various embodiments disclosed herein (e.g., data related to web-sites the user has visited usingdevice 10, bookmarks or favorites for web-sites, data downloaded from a user's social networking account on a web-site (e.g., a MySpace or Facebook account), data related to audio and/or video clips (e.g., songs, videos, etc.), to-do lists, memo applications, gaming applications, etc.). The present disclosure is intended to be applicable to all such embodiments. - Referring now to
FIG. 5 ,device 10 may be configured to receive and provide content (e.g., generic alerts or notifications, general inquiries, advertisement data, selectable links, icons, etc., and so on) to users. As shown inFIG. 5 ,device 10 may communicate withservers more advertisement sources server 52 may be an advertisement service configured to provide advertisement data (e.g., visual advertisements, audible advertisements, e-coupons, etc.) fromad sources servers 48, 50, as discussed in further detail below).Server 50 may be a server associated with an application developer that provides applications to be run on or provided todevice 10. Alternatively,server 50 and/orserver 52 may be a server associated with a manufacturer ofdevice 10. In some embodiments,sources device 10 without utilizingservers 50, 52 (e.g., such that the advertisement data is received byprocessor 40 ofdevice 10 fromsources - According to various exemplary embodiments, the advertisement data or content may include a variety of information and be provided in a variety of ways. For example, content may be provided to a user of
device 10 in the form of a visual image provided ondisplay 18. For example, an icon may be displayed ondevice 10 and may be selected by a user to provide an enlarged advertisement such as an electronic coupon, etc. Alternatively, rather than providing a visual display,device 10 may provide an audible message (e.g., a recording of an advertisement, etc.). Furthermore, advertisement data may be provided ondisplay 18 and superimposed over another image, such as the current image the user is viewing, a geographic map indicating the location of the establishment(s) the advertisement data is associated with, and so on. Further yet, the content may include or be non-advertisement data such as general point-of-interest data, appointment data, etc. According to various other exemplary embodiments, other types of content or advertisement data may be provided to device 10 (e.g., text, graphics, audio data, video data, etc.). - According to various exemplary embodiments, one or more of
servers device 10. For example, in one embodiment,server 52 may be associated with an advertisement service (e.g., AdSense, provided by Google, Inc., Mountain View, Calif.) and be configured to provide advertisement data todevice 10 independent fromserver 50. For example, as shown inFIG. 5 ,server 52 may communicate withdevice 10 and with one or more ofad sources Ad sources server 52, which may in turn provide the advertisement data tomobile device 10. In one example,server 52 may provide the advertisement data based at least in part on certain criteria or data (e.g., to act as a filter to provide advertisement data having higher relevance to a user), such as a location ofdevice 10, historical data associated with the usage of device 10 (e.g., web browsing history, location history), user-specific data (data stored in an information management application such as an email application, calendar application, contacts application, and so on), or some other criteria or data. Such criteria or data may be defined by a user and the access to such criteria or data for filtering or otherwise providing advertisement data and other content todevice 10 may be limited by a user or other entity. In some embodiments,server 52 may permit various ad sources (e.g.,ad sources server 52 in order to have their advertisement data provided to users (e.g., a user of device 10). Based on certain criteria or data, the advertisement data may then be selected for delivery to various devices/users. - According to other embodiments,
server 52 may be configured to provide advertisement data or other content todevice 10 in conjunction with or throughserver 50. For example, as noted above,server 50 may be or include a server associated with an application developer that provides applications (e.g., mobile device-specific applications, such as games, financial tools, location-based mapping programs, music players, etc.) todevice 10. Advertisement data may be provided to (by one or more ofservers 50, 52) and/or displayed ondevice 10 while one or more applications provided byserver 50 are running ondevice 10. For example, one or more advertisements provided byserver 52 may be displayed along a top, side, or bottom portion ofdisplay 18 while a user is running an application provided byserver 50. - In some embodiments,
server 50 may be a server associated with a manufacturer ofdevice 10, and may have wireless or other access to data unavailable to server 52 (e.g., user-specific data such as data from an information management application, including email, calendar, contacts, and other applications).Server 50 may provide data associated with device 10 (and/or the associated user) toserver 52. Such data may be used, for example, to filter advertisement data or other content being provided todevice 10 to increase the relevancy of the advertisement data to the particular device/user. It should be understood that the various embodiments discussed herein are provided for purposes of illustration only, and that more or fewer servers or other parties/entities may be involved in the provision of advertisement data or other content todevice 10. All such embodiments are deemed to be within the scope of the present disclosure. - Referring now to
FIGS. 6-9 , content may be provided todevice 10 based on context data or other information that may indicate where a user is, what the user is /will /has been doing, and so on. Context data may generally refer to data associated with the context ofdevice 10 or a user thereof, and may include historical data (e.g., data associated with past usage patterns ofdevice 10 such as movement of the device, locations of the device, messaging data, web browsing activity, transactions executed usingdevice 10, etc.), data associated with the current state of device 10 (e.g., mobile-specific inputs such as a current location, direction of travel, speed/acceleration of movement, etc., a current time of day, date, etc.), data associated with an information management application (e.g., an email or other messaging application, a calendar application, a contacts application, and so on), or other data accessible by or otherwise associated withdevice 10 or a user thereof (e.g., data associated with mobile devices or users of mobile devices that are included in a contact listing, social networking group, listing, category, etc., other mobile-specific inputs, and so on). Context data may in some embodiments generally refer to any type of data or information that may be used to determine a user's context, and may include or indicate usage patterns ofdevice 10 such as on/off patterns (e.g., a pattern of higher of usage (e.g., times of day during whichdevice 10 is typically on or off, etc.), web browsing (e.g., web sites visited, etc.), location/movement history (e.g., modes of travel, locations visited, etc.), and so on. - As an example,
device 10 may access data indicating a planned/future destination (e.g., location) of a user (e.g., as indicated by a calendar or other information management application) in addition to the user's current location, and provide the user with data regarding nearby points of interest (e.g., hours of operation, whether open /closed, etc.) or other establishments. Similarly,device 10 may access data indicating that the user is outside of a particular geographic area (e.g., outside a certain distance from a home location, a work location, etc., outside an area code of a mobile phone number associated withdevice 10, outside of an address contained in a contacts application, and so on), and/or data indicating that a user has recently moved locations (e.g., as a result of travelling via plane, train, etc.), and trigger the delivery of content based on the user's location and/or on a time-sensitive basis (e.g., based on departure times, arrival times, etc.). -
Device 10 may further access data indicating that a user has “free time” (e.g., as indicated by an appointment calendar or other application) and provide content regarding points of interest or establishments in the vicinity of the user (or similarly, on or near a route between the user and a location associated with one or more scheduled appointments). As an additional example, should the user be waiting for a bus, train, plane, etc., or some other type of public or other transportation,device 10 may provide time-sensitive offers for nearby establishments to the user based on, for example, the user's available time prior to a scheduled departure time. - As indicated above,
device 10 may be configured to provide (e.g., deliver, trigger or initiate the delivery of, filter, etc.) content based on context data. According to some embodiments, the content may be provided in the form of a generic alert or notification (e.g., “Are you hungry?”, “Do you want to listen to music?”, “Would you like to try a new restaurant?”, “Would you like to visit one of your favorite restaurants?”, “Do you want to send an invite out to your friends?”, etc.) that when selected, directs a user to more specific data or information (e.g., “Lunch Special at Sam's Deli today”, etc.). - Other examples of generic content may include content offering the best price for a certain item or service (e.g., “Looking for the best price for gas near you?”), or similarly, content offering to locate a preferred vendor, point of interest, etc., such as a gas station, fast food restaurant, coffee shop, etc. that, based on a user's current location, a given mode of transportation, and/or the hours of operation of the vendor or establishment, will still be open when the user arrives (e.g., “Looking for the nearest gas station?”). Other generic alerts may include offers to locate ATM machines or other computer terminal or user terminals (e.g., taking into account any additional fees charged by the ATM), public parking (e.g., taking into account hours of operation, pricing, etc.), lodging (e.g., taking into account vacancy, room rates, and other data regarding hotels, etc.), and so on. Various other types of generic alerts may be provided that take into account a wide variety of context data and other data (e.g., metadata associated with various establishments, etc.) in order to increase the relevancy of the content to users.
- According to various alternative embodiments, context data may be stored in a variety of ways and utilizing a variety of storage devices and systems, such as in memory of a mobile device such as
device 10, using one or more servers that are separate fromdevice 10, using one or more servers that are associated with an ad service, an ad sponsor (e.g., a retailer, etc.), via a data storage system accessible via the Internet or another network system, and so on. Other suitable means of storing context data may be used according various other embodiments. - Referring to
FIG. 6 , a method of providing content to a user is illustrated according to an exemplary embodiment. First, context data may be accessed (e.g., retrieved, monitored, stored, etc.) (step 62). Accessing context data may be done byprocessor 40,servers device 10 or otherwise accessible bydevice 10. - Based upon the context data, content may be provided to device 10 (step 64). According to an exemplary embodiment, the content is provided in a generic format (e.g., as a generic notification or alert, etc.) and is not tied to any particular entity such as
ad sources ad sources device 10 or in some other predetermined geographic location(s), a website, and so on). - It should be understood that the method illustrated in
FIG. 6 is widely applicable to various types of context data. Utilizing context data takes into consideration a user's context in triggering content such as generic notifications, advertisement data, and other content, and may enhance the quality of the content provided to users by increasing the relevancy of the content to the user in accordance with the user's context (e.g., location, current appointments, historical usage patterns, etc.). - In some embodiments, content may be provided based on time data and/or data from a personal information management application such as a calendar application. For example, at a predetermined time (e.g., a typical meal time such as lunch time, etc., a user-configurable time, a pre-set time, etc.), calendar data associated with
device 10 may be accessed to determine, for example, whether a user has an appointment scheduled (e.g., a lunch appointment). If the user has no appointment scheduled,device 10 may be configured to provide the user with content such as a generic alert or notification (e.g., “Are you hungry?”, “Do you want to go out to eat?”, etc.). The notification may include a selectable link or be otherwise selectable (e.g., via a touch screen or other input device), such that should the user select, for example, a link provided with the generic notification,device 10 may then provide more specific, additional content or information. The additional content may be any of a wide variety of content, including targeted advertisements (e.g., ads, e-coupons, discounts, etc. selected based on past user behavior, the location of the user, user-configurable preference data, etc.), an option to send out a notification to other users or mobile devices (e.g., an option to send out a lunch invitation to other mobile devices identified via a contacts application, a social networking application or listing, the location(s) of other users/devices, etc.), and so on. The process of providing progressively more specific data todevice 10 in response to continued responses or other user inputs may be repeated as part of providing content todevice 10. - In some embodiments, content may be provided based upon the movement and/or location of
device 10. For example,device 10 may be configured to, for example, determine when a user has left a building or similar environment, which may in turn trigger the delivery of content to the user (e.g., “Need directions?”, etc.). In order to provide content with greater relevancy,device 10 may further take into account a direction of travel (e.g., via an integrated compass, etc.), a speed of travel (e.g., via a GPS system, accelerometer, etc.), and so on. For example, the content provided to the user may vary based on what points of interest are in the general direction of travel ofdevice 10, based on a predicted mode of travel (e.g., walking, driving, etc.) determined based upon the speed of travel, based on calendar appointment data (e.g., by knowing where a user may be going based upon appointment data), and so on. - In some embodiments, content may be provided to additional devices based on inputs associated with, or content provided to,
device 10. For example, content such as an advertisement may be provided to a user viadisplay 18 ofdevice 10. A user may select the advertisement in order to navigate to, for example, a web site hosted by the source of the advertisement. In response to the user selecting the advertisement, additional content may automatically be provided to additional devices (e.g., additional mobile devices identified in a social network listing, etc.). For example, should a user select a particular advertisement, the same or a similar advertisement may be provided to a group of users that are in a contacts application of the user, users that may be identified based upon some type of social networking grouping or listing (e.g., via being identified as “friends,” contacts,” etc. as part of an application or web-based service such as Facebook, MySpace, etc. (or a list of contacts having a particular designation on such a service)), users that may be designated, flagged or somehow identified by a user and stored ondevice 10 and/or a server, etc., and so on. Various other means of identifying a social network listing may be used, and the listings may overlap or may be mutually exclusive, etc. For example, social network listings may include email listings (e.g., personal or professional listings or groups, such as a marketing group of a business, a sales team, etc.) a class list for a particular academic institution and/or year, a sports team (e.g., a school and/or youth sports team, etc.) and/or other social network listings that may be more or less permanent/temporary in nature. - Referring to
FIGS. 7-9 ,display 18 is shown according to various exemplary embodiments as including content provided to a user. Referring toFIG. 7 , content such as generic notifications, advertisement data, etc., may include or be provided in the form of a selectable link or identifier 80 (e.g., an icon, selectable text or graphics, etc.).Link 80 may be an icon with a graphical representation intended to convey a message to a user (e.g., such as an icon with a graphical representation of a map that is associated with driving directions, etc., and so on).Icon 80 may be sized such that it is relatively smaller than one or more other icons or identifiers (e.g., icons or other identifiers associated with applications, files, etc. available to device 10) provided ondisplay 18 in order to provide content to users in an unobtrusive manner. Furthermore,icon 80 may be provided as part of a status or notification bar orarea 74 ondisplay 18. As shown inFIG. 7 , the content or icon and notification or status bar may be provided in any of wide variety of locations ondisplay 18, including a bottom portion (seeicon 80 and notification bar 74), a side portion (see notification bars 72, 76), or a top portion (see notification bar 70). In some embodiments, an application developer (e.g., a developer associated with one ofservers 50, 52) may be permitted to feed or provide advertisements or other data to a notification bar displayed ondevice 10, or alternatively, to have advertisements or other content embedded within the area of the display being used by one or more applications. According to various exemplary embodiments,icon 80 may be provided in other areas or portions than those shown inFIG. 7 . - Referring to
FIG. 8 , should a userselect icon 80, the user may be provided withadditional content 84.Additional content 84 may include a generic notification or message, advertisement data from an ad source (e.g., one or more ofad sources icon 80 may include a representation of a map. Upon clicking on the map, a user may be provided withadditional content 84, which may include a generic notification or question such as “Do you need directions?”.Additional content 84 may include a selectable link that enables a user to selectadditional content 84. Upon a user selectingadditional content 84, the user may be provided with yetfurther content 86. For example,content 86 may include driving directions, a list of popular destinations for a user (which may be selectable to provide even further content), and so on. - As shown in
FIG. 7-9 , as a user continues to provide inputs (e.g., selecting content provided to device 10), the content provided may continue to increase in size or prominence (e.g., as shown with the increasing relative sizes oficon 80,additional content 84, and content 86). Furthermore, the amount of content provided may increase as a user continues to engage the content provided. Further yet, the specificity of the content may increase as a user becomes more engaged (e.g., from generic to greater levels of specificity). - According to various exemplary embodiments, as a user continues to engage the content provided to
device 10, a user may be permitted to interact (e.g., enter into transactions, make reservations, provide and/or receive contact information, etc.) with various entities associated with the content provided todevice 10. For example, as a user selects additional content (e.g., additional content such asadditional content 84 shown inFIG. 8 ), a user may be permitted to, for example, make dinner reservations (including automatically making an appointment in a calendar application), enter into transactions such as paying for a dinner, etc., exchange contact data with ad sources and other entities, and so on. - The systems and methods described herein may be implemented to provide data to a wide variety of mobile devices that may take a wide variety of forms (e.g., differing form functions, etc.) and have a wide variety of functional capabilities such as visual display capabilities, input/output capabilities (e.g., touch screen, non-touch screen devices, etc.), audible output capabilities, etc. In some embodiments, the content provided to
device 10 may be formatted based on the characteristics or capabilities ofdevice 10. Alternatively,device 10 may be configured to receive the content and perform such formatting based on data stored ondevice 10, accessible viadevice 10, provided as part of the content itself (e.g., as embedded data or formatting instructions) and so on. The formatting may further be performed for a wide variety of devices (e.g., a handheld device, a relatively smaller-sized device such as a watch, etc., a relatively larger-sized device such as a television, etc.), and so on. - In some embodiments,
device 10 may be configured to provide and/or format content such as advertisements etc. as sessions change (e.g., as an application moves through different modes or states such as downloading, launch, a ready/usage state, ending/shut-down, etc.). For example, a user may download an application todevice 10, during which content may be provided in the form of, for example, dynamic and/or static ads, sponsorships, etc. When the application is launched an initial “splash screen” (e.g., a screen or page provided to the user while an application is launched) may be displayed that includes content such as advertisements, etc., and as the application transitions to a “ready” state (e.g., ready to be used by the user), one or more interstitial pages may be provided with further content. Similar content may be provided as the application is closed or shut down. - In some embodiments, while an application is in use, or active, certain display portions or areas may be dedicated to content such as advertisements on a permanent or temporary basis. Alternatively,
device 10 may provide users with alerts or other notifications that include relevant content such as advertising or other data. Further, for applications having searching capabilities, content such as sponsored links or logos, etc. may be provided in connection with various search queries. Further yet, certain content provided bydevice 10 may include brand information such as logos, etc. - Referring now to
FIG. 10 , a system and method for performing a function based on past uses of a mobile computing device or behaviors of a user of the mobile computing device will be described. One or more components of the system and method may be operable as an algorithm on the mobile computing device, on a server computer in communication with the mobile computing device, or on another computing device in communication with the mobile computing device. At astep 1000, a memory is configured to store use data indicative of a pattern of past uses of the mobile computing device. The memory may store the data temporarily and then back up the data to a remote server, may receive the data from a remote server configured to monitor and store use data, or may store the use data for a longer period. The use data can represent a past behavior of a user of the device. - The use data may be retrieved or determined based on data from one or more sources operating on the mobile computing device or remote from the computing device, such as a location determination circuit, a time of day clock, a source of a date and day of the week, a database of geographic points of interest (e.g., location and extent of a parking lot, restaurant, bridge, gas station, etc.), a mass transit schedule database or other database stored on a remote server, a phone call log, an application store available on a remote server for downloading new software applications, an on-line reservation system for a restaurant, train, etc., a wireless transceiver circuit configured to receive wireless signals (e.g., radio frequency, infrared, etc.) from nearby or remote devices, metadata for one or more audio music files recently played by the user, textual input from a user entered via a keyboard or data from any other application operating on the mobile computing device, such as a calendar application, contacts application, phone application, notes application, task list application, gaming application, music and/or video player application, etc.
- A pattern of past uses may comprise a plurality of past uses of the mobile computing device, based on any of the use data described herein.
- At
step 1002, the system is configured to determine or detect a present condition, situation, or context of the mobile computing device and/or user thereof. The present condition may be one which is currently applicable, or recently applicable, to the device (e.g., detecting that the mobile device has just passed a point of interest may be a present condition for some period of time). The present condition may be retrieved or determined based on data from one or more sources operating on the mobile computing device or remote from the computing device, such a traffic data available from a remote site (e.g., such as Google Maps), a calendar application, a date and/or time of day source, a location determination circuit, a source of geographic point of interest data, an application store available on a remote server for downloading new software applications, user inputs, a time counter configured to detect the passage of one or more predetermined periods of time, a distance counter configured to detect a traveled distance, a navigation application configured to determine a route traveled, a wireless transceiver circuit configured to receive wireless signals from nearby or remote devices, or other data sources. - At
step 1004, the mobile computing device may be configured to perform a function based at least on the use data and the present condition. The function comprise generating a notification to the user, such as by displaying a message, alert, textual data, etc. in a window, full screen, etc., and/or by providing an audible alert, such as a beep, series of beeps, playing an audio file, etc and/or by vibrating or providing other outputs to the user. The function may further comprise performing operations within other applications operable on the mobile computing device, such as adding a resource locator link and/or identifier to a “favorites” or bookmark list in a browser application, adding a phone number to a list of frequently called numbers, etc. The function may further comprise delaying a function to be performed, such as delaying a download of data or a synchronization operation. The function may further comprise downloading a program from a server computer, filtering a list of potential files to be downloaded to present a subset of the list to the user for selection, running a search on a local or remote geographic information database, calculating a route using a navigation or mapping application, etc. The function may further comprise sending wireless data to a remove device containing a command, request, alert, or other data. - Various embodiments are contemplated of processing circuits programmed with algorithms for tracking a user's behavior and performing functions based on the past experience or historical knowledge of the user. As mentioned, the algorithms may be operable on processing circuitry on the mobile computing device, a server computer, or portions of the algorithm on both a mobile device and a server computer. The algorithms may be operable to predict one or more functions the user may wish to perform with the device based on the past experience or historical usage of the device and may be configured to perform the one or more functions based on one or more present conditions, such as a triggering event or occurrence. The mobile device may be configured to suggest a function and await user confirmation (e.g., via pressing a key, speaking into a microphone on the device, etc.) or may be configured to perform the function without awaiting user confirmation.
- According to one embodiment, a processing circuit may be configured to generate an alarm to wake up a user at a time earlier than a predetermined typical wake-up time based on a present condition of data from a traffic report indicating traffic is worse than usual along a predetermined traveling route. The processing circuit may be configured to determine based on time of day and location based signals collected over a plurality of days the predetermined traveling route. The processing circuit may further be configured to store data indicative of typical or average traffic conditions at one or more points along the route. The mobile device may be configured to receive a user selection of an alarm time. Each morning, the processing circuit may be configured at some predetermined time period prior to the selected alarm time to receive current traffic data along the predetermined traveling route, calculate or retrieve from memory a time period, subtract the time period from the user-selected alarm time, and then program the mobile device to provide the alarm at the new time. According to another embodiment, the processing circuit may be configured to determine when the mobile device arrives at a location (e.g., a place of work) and to suggest a new alarm or wake-up time based on one or more previous commute times stored by the processing circuit to assist the user in arriving at work more reliably at a predetermined time. For example, if the processing circuit detects the user repeatedly arrives at 8:05 AM and has an alarm set to 6:30 AM, the processing circuit may determine that the user intends to arrive at work at 8:00 AM and to suggest the user switch the alarm time to 6:25 AM.
- The processing circuit may be configured to learn over a period of days or weeks where a user will be located with the device at a given time (e.g., during a commute, during lunch, etc.) based on past experience and to predict a function needed by the user at a present or future time based on the data indicative of past experience or behavior. In other embodiments, the mobile device may be configured to receive certain data to replace or supplement the use data or past experience data, such as a desired lunch time, a commute route, current location, etc.
- According to another embodiment, a processing circuit may be configured to monitor the presence and/or signal strength of wireless networks at locations along a route, such as a frequently traveled route, such as a commute route or weekend vacation route. The processing circuit may be configured to store one or more locations at which a wireless signal becomes weaker or unavailable (e.g., “dead spots”, weak spots, etc.). Upon a subsequent trip, the mobile device may be configured to notify a user via an alert or other alarm that a dead spot is approaching. The device may further be configured to suggest other available networks for a handoff of a wireless communication session, such as a voice or data session, which may be a handoff to a cellular network of a different carrier, to a Wi-Fi access point, etc. The data of other wireless networks may be stored in a memory from previous data collected by the mobile device along the route or may be retrieved from a commercially-available database of network data accessible on a server computer (e.g., a database offered by Boingo Wireless, Inc., Los Angeles, Calif.). In another embodiment, the processing circuit may be configured to store present and/or signal strength of wireless networks at any location, regardless of any route data. The processing circuit may further obtain such data via download from a server. The processing circuit may be configured to change the behavior of the phone based on knowledge of the level or quality of wireless connectivity the device will have in certain locations. For example, if the device will be approaching a good Wi-Fi network, the device may be configured to delay a wireless download and/or upload operation until the device reaches the Wi-Fi network. This feature may be useful for downloading software updates to the mobile device, software patches or new versions of software, or other data to be communicated wirelessly. The processing circuit may be configured to schedule wireless communications based on predictions of where the device will be at times of the day (e.g., based on a current route, projected route, location and time data from prior days (e.g., the mobile device is home after 6 pm each night for a plurality of nights in communication with a Wi-Fi network with a suitable signal strength), or other based on other characteristics).
- According to another embodiment, a processing circuit may be configured to store user preferences or rankings associated with locations and/or types of events previously attended. In response to an indication that the user will participate in a present or future event at a similar location or of a similar types, the device may be configured to alert the user that the user previously indicated they did not want to visit these types of events or locations. The processing circuit may also receive current traffic data and further provide the alert based on the current traffic data to suggest that the user may not want to attend the event because of traffic. In this embodiment, the processing circuit may be configured to learn what not to do based at least in part on things previously done with the device and optionally also in response to a user ranking or assessment of the location or event.
- According to another embodiment, a processing circuit may be configured to store a plurality of user-selectable time zones in a list based on locations previously visited by the mobile device. According to another embodiment, the mobile device may be configured to learn a time zone of a person associated with a contact in an contacts location based on the user of the mobile device traveling to visit the person. The time zone may be stored in the contact data file. According to one example, the mobile device may be configured to generate an alert for the user if the user initiates a telephone call to the contact and a time of day source indicates that based on the time zone, the time may be received by the contact at an inconvenient time, such as after and/or before a predetermined time of day, as indicated by a time of day source and the time zone associated with the contact. Also, the contacts application may be configured to display data indicative of a time of day at the contact's location based on time of day data and the time zone associated with the contact.
- According to another embodiment, a processing circuit may be configured to store data indicative of where the mobile device has traveled to, such as a foreign country, outside of a home state (as determined based on use data indicating past location), etc. The processing circuit may then be configured to download applications or suggest applications for download to the user based on the data indicative of where the mobile device has traveled to. For example, if the device has recently traveled to a foreign country, the device may be configured to identify one or more applications relating to the foreign country available for download from a remote server or items available for purchase (e.g., a French/English dictionary, a currency exchange application, etc.) and to notify the user of the availability of such applications or items (e.g., a travel book). In this manner, the recently-traveled data may be used as a filter for an application store or other function of the device or a server in communication with the device. The recently-traveled data may further comprise frequency of travel data or number of travel events data, to distinguish a location infrequently visited from one frequently visited, which data may further be used to filter applications for download or items for purchase. For example, if a user frequently travels to France, the mobile device may be configured to suggest downloading applications operable or items written in the French language instead of English language.
- According to another embodiment, a processing circuit may be configured to store metadata associated with one or more applications downloaded from a remote server. The processing circuit may then be configured to filter applications available for download or items available for purchase based on one or more of the metadata items. For example, if a user frequently downloads gaming applications, the processing circuit may detect a user request to access an application store at a server and, in response, the processing circuit may be configured to filter a set of applications available for download based on the frequent-download data and to present to the user one or more or only gaming applications. According to yet another embodiment, the processing circuit may be configured to filter applications for download based on applications that are downloaded and frequently used (or recently used), to further reduce the number of applications to be viewed by the user of the mobile computing device.
- According to another embodiment, the processing circuit may be configured to store data indicating the mobile device has been used at or in association with a restaurant or other dining location. The use data may comprise data indicating that a dinner reservation has been made using the mobile device and dinner reservation web site, that a phone call has been placed to the restaurant, that the device has entered the restaurant based on location data, that the device has been used to make a purchase at the restaurant, such as with a near-field communication device or other transaction processing circuit, etc. The processing circuit may be configured to store data about the restaurant along with data about other restaurants similarly gathered. The processing circuit may be configured to determine that a user may presently wish to review restaurant suggestions, which may be determined based on time of day (e.g., lunch time, dinner time, etc.), based on a user request to review restaurants suggestions, or based on other present conditions. The processing circuit may then function to generate one or more restaurant or dining location suggestions based on the prior use data and to present the one or more restaurant suggestions to the user, optionally along with location, web site, phone number, mapping, reviews, and/or other data about the restaurant. According to another embodiment, if the processing circuit detects that the user is visiting (e.g., from location data) or plans to visit (e.g., from calendar data, a reservation made using the phone, etc.) a restaurant that has been visited before, been recently visited, and/or been frequently visited, the processing circuit may be configured to suggest a new dish for the user to try, based on dish data received from the restaurant or from a server configured to store dishes recommended by other patrons or by friends in a friend list stored by the mobile device.
- According to another embodiment, a processing circuit may be configured to identify one or more gas stations at which a user of a mobile device has recently or frequently fills up their car with gas. The processing circuit may identify the gas station based on one or more of location data, point of interest information (e.g., comprising a location of a gas station and data indicating the point of interest is a gas station), a period of time between visits to the gas station and/or other gas stations (which may indicate whether the gas station was visited for a gas purchase or for a non-gas purchase), transaction data indicating the mobile device was used to make a transaction to purchase gas (e.g., using a near-field communication device or other transaction circuit), or other data. The processing circuit may then be configured to determine a present condition, such as a present location of the device approaching or located at the gas station, a predetermined period of time having passed and/or distance having been traveled at vehicle speeds since the last gas fill-up (e.g., which may indicate that the user's vehicle will soon be in need of fuel), the user traveling near a second gas station selected as described below, and/or other present conditions (e.g., a user turning on the device). The processing circuit may be configured to perform one or more of the following functions based on the identified gas stations and present condition: perform a search of a remote web site for nearby gas stations offering a lower price on gas (e.g., which may include a special, coupon, etc.), present an alert to the user comprising information about the lower price and location, provide directions, a map, or other data about the gas stations offering the lower price.
- According to another embodiment, a processing circuit may be configured to present advertisements to a user via the user's mobile computing device based on past usage data of the mobile computing device, such as a past location (e.g., a point of interest recently visited, a point of interest frequented or visited a plurality of times in a predetermined time period, etc.).
- According to another embodiment, a processing circuit may be configured to receive a user request for a point of interest or other retail location, which may be provided generically by the user (e.g., a barber, a dry cleaner, a book store, a restaurant, etc.) and may include additional criteria about the point of interest to be found (e.g., a predetermined rating level, such as at least two stars, a price range, etc.). The processing circuit may be configured to identify one or more points of interest meeting the criteria provided by the user based further on location data representative of a route previously or frequently traveled by the user in the past (e.g., a daily commute). Based on the travel history of the device, the processing circuit may be configured to identify one or more points of interest along the route, near a point on the route, or closer than other points to the route, and to present the points of interest to the user, such as in an alert, on a map, etc. This functionality may be operated from within a task list or notes application operable on the mobile device, to assist the user in completing a task entered by the user (e.g., “get a haircut,” “drop off drycleaning,” etc.).
- According to another exemplary embodiment, a processing circuit may be configured to store use data from a telephone call log (e.g., phone numbers, times of calls, persons called incoming our outgoing, etc.). The processing circuit may be configured to perform functions based on the telephone call log information and any present condition. For example, if the processing circuit determines that phone calls have been made to Chinese restaurants (e.g., recently, frequently, exclusively, etc.), which may be based on data from the call log and/or data from a web site or other server configured to provide additional data to supplement data from the call log, the processing circuit may be configured to determine and/or store a preference for Chinese restaurants. If a present condition is met, such as a time of day representing a typical time to eat (e.g., noon, 6 pm, etc.), a typical time to eat for the user based on previous times during which the user has eaten (e.g., based on calendar data, location data, reservations made using the mobile device, dining transactions made using the mobile device, periodic eating at a particular restaurant (e.g., every Monday is Chinese food day), etc.), the processing circuit may be configured to provide a function of alerting or suggesting to the user a restaurant or nearby restaurant based on the data (in this case, a Chinese restaurant), or to prompt the user to confirm placing a phone call to a favorite restaurant to place an order or make a reservation. The mobile device may be configured to store preferred menu items and to transfer the menu items as an order to the restaurant through a web site, text message, etc. at a predetermined time and in response to user confirmation to place the order. The mobile device may be configured to prompt the user (e.g., “the usual?”).
- According to another embodiment, the processing circuit may be configured to store data representative of a mass transit service (e.g., bus, train, flight, etc.) used or frequently used by a user of the mobile device. The data may be stored based on location data indicating travel along a mass transit route (e.g., a train track or rail line), typically a plurality of times to indicate a pattern or frequency of travel. The processing circuit may then be configured to retrieve data indicating a delay or cancellation in the mass transit route typically traveled, which may be a present condition. The processing circuit may be configured to alert the user of the mobile device as to the delay or cancellation.
- Accordingly to another embodiment, the processing circuit may be configured to determine that the mobile device has traveled along two or more different routes, at least one of which has been traveled a plurality of times indicating some frequency or regularity of the travel route. The processing circuit may be configured to determine a present traffic condition and, based on the present traffic condition and past route data, display a recommendation to the user as to which of the two or more different routes to travel. According to another embodiment, the processing circuit may be configured to determine that the mobile device has repeatedly traveled a first route, that an alternative route is available which may be a better route for one or more reasons (e.g., shorter travel time, less traffic, less uncertainty due to potential traffic issues, shorter travel distance, the route goes near a point of interest determined to be of interest to the user, etc.).
- According to another embodiment, a processing circuit may be configured to store data indicating a preferred parking lot, such as in an urban setting, at an airport, etc. The preferred or historical parking lot data may be used by the processing circuit to provide an indication the user that the preferred parking lot is full, closed, etc., using data from a web server monitoring the parking lot capacity and status. The processing circuit may provide the indication in response to determining that the user is approaching the parking lot.
- According to another embodiment, a processing circuit may be configured to store data indicative of prior music files played by the mobile device and one or more elements of metadata about the prior music files, frequency of playing each music file, date of download or stored on the mobile device, etc. Based on one or more of this data, the processing circuit may be configured to search for additional music files for potential download, using similar styles, artists, genre, etc., and to suggest the additional music files to the user. The processing circuit may further be configured to search for concerts coming to town based on historical music file data, recent location data of the device, determined musical tastes, etc. and to provide an alert to the user of the concert coming to town, for example with a text or e-mail message containing a link for the user to click on to see concert information, order tickets, etc.
- According to another embodiment, the processing circuit may be configured to determine a home location from an address data stored in a contact for oneself, based on data indicating the mobile device returns to that location every night or otherwise daily, or based on other data. The processing circuit may then be configured to determine when the mobile device is approaching the home (e.g., a predetermined distance or time away from the home), based on determining that the mobile device has traveled certain points along a previously-traveled route home, and to provide a wireless message to a system in the home or to another mobile or fixed computing system based on the determination that that the device is approaching or nearing the home. For example, if the home is equipped with a home automation or control system (e.g., security system, lighting system, door locking system, audio control system, HVAC control system, etc.) having web access or access to a cellular network, the mobile device may be configured to send a message to the home control system to control one or more of the systems (e.g., disable or check security system, turn on lights, unlock doors, etc.). As another example, the mobile device may be configured to send a text message to another mobile device (e.g., a spouse's or other family members' mobile device) to advise them that the user is nearing home (e.g., “dad will be home in about 5 minutes,” etc.). In alternative embodiments, the message may be based on approaching another location or system other than the home, such as a vehicle, and may further be based on data indicating the mobile device is moving away from another location or system, such as a shopping mail. In such an embodiment, the mobile device may send a message to the vehicle (e.g., directly via Bluetooth or other short-range wireless network, or indirectly via a cellular or Wi-Fi network) to command the vehicle to unlock the doors, release the trunk door, and/or remote start the vehicle.
- According to another exemplary embodiment, the processing circuit may be configured to detect a use of the mobile device, such as visiting a web site (or visiting it frequently or a plurality of times in a predetermined time period), making a phone call (or calling a particular number frequently or a plurality of times in a predetermined time period), etc. The processing circuit may be configured to perform a function based on the detected use, such as adding a bookmark, favorite, or link to a list of such favorites in a web browser application, wherein the link is associated with the web site visited. In another embodiment, a phone number may be added to a speed dial list (e.g., having a predetermined number or number sequence associated with it shorter than the phone number, having an icon which can be tapped, such as with a photo of the person associated with the phone number, etc.) based on the phone call data. In another embodiment, the processing circuit may be configured to display an alert based on a frequently-called person approaching the mobile device, may display a map showing their location, etc. In another embodiment, the processing circuit may be configured to determine that another mobile device is typically detected in the proximity of the mobile device at a predetermined time each day or on certain days and that the device has not been detected in proximity. The processing circuit may then be configured to prompt the user to phone or contact the mobile device of the other person. One use of this embodiment may be at a construction site where one or more workers are expected to be located at the site at a predetermined time and a mobile device monitors the locations of the mobile devices of the workers to confirm they have arrived, and to send a communication to the other mobile devices which have not yet arrived (e.g., a text message, phone call, etc.). The expected time of arrival and devices expected may be received via manual input from a user or may be detected based on prior history at the work site and stored in a memory on the mobile device or a server in communication therewith.
- According to another embodiment, the processing circuit may be configured to determine use data based on when the device is turned on or off (or allowed to power off) by a user. For example, if the processing circuit determines that the device is typically powered off after 10 PM and night powered on until 5 AM, the processing circuit may be configured to schedule or delay certain wireless download, synchronization, virus scan, or other operations until the time of after 10 PM and/or before 5 AM. The device may further be configured to stop certain operations initiated before a predetermined time period based on an expectation that the user will turn on and use the device, again based on data stored regarding prior usage of the device. In another embodiment, the processing circuit may be configured to determine that the mobile device is located at a work location and may be configured (automatically or in response to a user request) to stop, delay, or cease synchronization of data, such as e-mails, based on an assumption that the user will be handling e-mail communications from a laptop or desktop computer while at work or while at a particular location of work (e.g., the desk versus the lab). Battery life of the mobile device may be conserved using such a feature.
- According to another embodiment, a processing circuit is configured to determine that the mobile device is located in a city, state, country or other geographic location not previously visited by the device (or not previously detected by the program operating the feature). Alternatively, the processing circuit may determine that the mobile device is located at a hotel or other lodging point and to determine that the mobile device may want additional data based on the fact that the user is staying at a hotel. The processing circuit may be configured to prompt the user to indicate whether the user is traveling for business or pleasure. The processing circuit may then be configured to provide data indicative of local points of interest and/or events (e.g., things to do, restaurants, attractions, events, etc.) based on the determination and/or collected user input. The processing circuit may be configured to provide restaurant, entertainment, local history, news, or other data to the user based on the determination and/or collected user input.
- According to another embodiment, the mobile device may be configured to operate a clock application. A processing circuit may be configured to determine a home time and local times for places visited or commonly visited, based on use data (e.g., where the device is used, for how long the device is used at each location, etc.), and to store these times in the clock application. Any of the functions described herein may then be performed based at least in part on the time information.
- According to another embodiment, a processing circuit may be configured to determine times of the day during which a user of a mobile device is typically at work. For example, the device may receive a user selection or input of a work location, or the processing circuit may determine a work location based on a location the device is typically at for a significant portion of a day, estimating based on typical work hours in any one of a plurality of different shifts. The processing circuit may then be configured to determine whether an appointment in a calendar application is scheduled for a time that the user is not typically at work, and may be configured to provide additional reminders or alerts of the meeting beyond a reminder or alert that would typically be provided for a meeting scheduled during typical work hours. For example, the reminders may be greater in number, may use more output devices (e.g., display, speaker, vibration, phone call to home, instant message or text message to second computing device, etc.), may be earlier (e.g., more than an hour before the meeting), may be provided during typical work hours regardless of the time of the meeting, etc.
- It should be understood that the various systems and methods described herein may be implemented on or via
device 10, via one or more ofservers 50, 52 (e.g., a server associated with an ad service, etc.), or via other devices/components and any combination(s) thereof, and all such combinations are deemed to be within the scope of the present disclosure. One or more ofdevice 10 and/orservers device 10. References to a processing circuit may include use of multiple processing circuits, such as one operable on a mobile device and one operable on one or more server computers. - Various embodiments disclosed herein may include or be implemented in connection with computer-readable media configured to store machine-executable instructions therein, and/or one or more modules, circuits, units, or other elements that may comprise analog and/or digital circuit components configured or arranged to perform one or more of the steps recited herein. By way of example, computer-readable media may include RAM, ROM, CD-ROM, or other optical disk storage, magnetic disk storage, or any other medium capable of storing and providing access to desired machine-executable instructions.
- While the detailed drawings, specific examples and particular formulations given describe exemplary embodiments, they serve the purpose of illustration only. The hardware and software configurations shown and described may differ depending on the chosen performance characteristics and physical characteristics of the computing devices. The systems shown and described are not limited to the precise details and conditions disclosed. Furthermore, other substitutions, modifications, changes, and omissions may be made in the design, operating conditions, and arrangement of the exemplary embodiments without departing from the scope of the present disclosure as expressed in the appended claims.
Claims (16)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/402,386 US20100161720A1 (en) | 2008-12-23 | 2009-03-11 | System and method for providing content to a mobile device |
GB1112452A GB2478507A (en) | 2008-12-23 | 2009-12-17 | System and method for providing content to a mobile device |
PCT/US2009/068525 WO2010075174A2 (en) | 2008-12-23 | 2009-12-17 | System and method for providing content to a mobile device |
DE112009004349T DE112009004349T5 (en) | 2008-12-23 | 2009-12-17 | System and method for providing content to a mobile device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14056208P | 2008-12-23 | 2008-12-23 | |
US12/402,386 US20100161720A1 (en) | 2008-12-23 | 2009-03-11 | System and method for providing content to a mobile device |
Publications (1)
Publication Number | Publication Date |
---|---|
US20100161720A1 true US20100161720A1 (en) | 2010-06-24 |
Family
ID=42266853
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/402,386 Abandoned US20100161720A1 (en) | 2008-12-23 | 2009-03-11 | System and method for providing content to a mobile device |
US12/422,871 Expired - Fee Related US8135777B2 (en) | 2008-12-23 | 2009-04-13 | System and method for providing content to a mobile device |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/422,871 Expired - Fee Related US8135777B2 (en) | 2008-12-23 | 2009-04-13 | System and method for providing content to a mobile device |
Country Status (4)
Country | Link |
---|---|
US (2) | US20100161720A1 (en) |
DE (1) | DE112009004349T5 (en) |
GB (1) | GB2478507A (en) |
WO (1) | WO2010075174A2 (en) |
Cited By (113)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090265236A1 (en) * | 2008-04-21 | 2009-10-22 | Verizon Business Network Services Inc. | Aggregation and use of information relating to a users context for personalized advertisements |
US20100185391A1 (en) * | 2009-01-21 | 2010-07-22 | Htc Corporation | Method, apparatus, and recording medium for selecting location |
US20100235454A1 (en) * | 2009-03-16 | 2010-09-16 | Apple Inc. | Application communication with external accessories |
US20110029383A1 (en) * | 2009-07-28 | 2011-02-03 | Randy Engel | System and method for providing advertising content via an integrated home based device |
US20110196969A1 (en) * | 2010-02-08 | 2011-08-11 | Paccar Inc | In-vehicle communication device with social networking |
US20110225291A1 (en) * | 2010-03-15 | 2011-09-15 | Cellco Partnership D/B/A Verizon Wireless | Using social networking to help users purchase mobile applications and devices |
US20110258301A1 (en) * | 2010-04-15 | 2011-10-20 | Research In Motion Limited | Method and system for transmitting an application to a device |
US20110289493A1 (en) * | 2010-05-21 | 2011-11-24 | Derrick Keefe | System that provides embedded software to an embedded system |
US20110287784A1 (en) * | 2010-05-24 | 2011-11-24 | Moshe Levin | Method and system for mobile station location |
US20110320450A1 (en) * | 2010-06-29 | 2011-12-29 | Alice Liu | Location based grouping of browsing histories |
US20120042257A1 (en) * | 2010-08-11 | 2012-02-16 | Microsoft Corporation | Updating application data after anticipating imminent use |
US20120084248A1 (en) * | 2010-09-30 | 2012-04-05 | Microsoft Corporation | Providing suggestions based on user intent |
CN102446118A (en) * | 2010-11-17 | 2012-05-09 | 微软公司 | Contextual and task focused computing |
US20120136905A1 (en) * | 2010-11-30 | 2012-05-31 | Pullara Samuel J | Information feed update mechanism |
US20120143952A1 (en) * | 2010-12-01 | 2012-06-07 | Von Graf Fred | System and method for event framework |
JP2012108614A (en) * | 2010-11-15 | 2012-06-07 | Sharp Corp | Terminal and advertisement display method |
US20120166530A1 (en) * | 2010-12-22 | 2012-06-28 | Erick Tseng | Timing for providing relevant notifications for a user based on user interaction with notifications |
US20120185717A1 (en) * | 2009-09-16 | 2012-07-19 | Samsung Electronics Co., Ltd. | Apparatus and method for reducing power consumption in portable terminal |
US20120197982A1 (en) * | 2009-06-22 | 2012-08-02 | Clayster Asia Ltd. | Method and computer system for introducing client devices into a client-server network |
US20120296680A1 (en) * | 2011-04-25 | 2012-11-22 | Scott Bergen Jantz | Provision of Alert Messages to Customers of an Establishment |
US20120311465A1 (en) * | 2011-05-31 | 2012-12-06 | Microsoft Corporation | Accessing Web Content Based on Mobile Contextual Data |
US20120323692A1 (en) * | 2011-06-16 | 2012-12-20 | Jon Shutter | Method and System for Providing Location Targeted Advertisements |
US20120322548A1 (en) * | 2011-06-15 | 2012-12-20 | Microsoft Corporation | Position-based decision to provide service |
US20130055121A1 (en) * | 2011-08-29 | 2013-02-28 | Samsung Electronics Co., Ltd. | Apparatus and method for displaying splash screen |
US20130065585A1 (en) * | 2011-09-09 | 2013-03-14 | Interdigital Patent Holdings, Inc. | Methods and apparatus for accessing localized applications |
US20130091229A1 (en) * | 2011-10-07 | 2013-04-11 | Salesforce.Com, Inc. | Computer Implemented Methods And Apparatus For Providing Selective Notifications In An Online Social Network |
US20130232010A1 (en) * | 2012-03-02 | 2013-09-05 | International Business Machines Corporation | Mobile device cluster advertisement delivery |
US8588808B2 (en) | 2010-05-24 | 2013-11-19 | Nice-Systems Ltd. | Method and system for estimation of mobile station velocity in a cellular system based on geographical data |
US20140010121A1 (en) * | 2011-03-21 | 2014-01-09 | Mayuresh Madhukar Patil | Method and system for providing calendar services in a universal plug and play home network environment |
US20140047016A1 (en) * | 2010-10-21 | 2014-02-13 | Bindu Rama Rao | Server infrastructure, mobile client device and app for mobile blogging and sharing |
US20140074536A1 (en) * | 2012-09-10 | 2014-03-13 | Dana Meushar | Meetings and Events Coordinating System and Method |
US20140156281A1 (en) * | 2012-12-03 | 2014-06-05 | Qualcomm Incorporated | Voice-controlled configuration of an automation system |
US20140171117A1 (en) * | 2012-12-14 | 2014-06-19 | Anthony G. LaMarca | Location-aware management of lists of uniform resource locators (urls) for mobile devices |
US8768876B2 (en) | 2012-02-24 | 2014-07-01 | Placed, Inc. | Inference pipeline system and method |
US20140228052A1 (en) * | 2011-07-01 | 2014-08-14 | Alcatel Lucent | Method for alerting a mobile device at a predetermined destination |
US20140237109A1 (en) * | 2013-02-17 | 2014-08-21 | Onavo Mobile Ltd. | Techniques for determining a mobile application download attribution |
US20140242971A1 (en) * | 2011-05-20 | 2014-08-28 | Renault S.A.S. | Access and customization of a motor vehicle by telephone |
US20140257696A1 (en) * | 2013-03-07 | 2014-09-11 | Kamal Zamer | Travel Pattern Analysis |
US20140297455A1 (en) * | 2013-03-29 | 2014-10-02 | Ebay Inc. | Routine suggestion system |
US8862533B2 (en) | 2011-11-21 | 2014-10-14 | Motorola Mobility Llc | Method and apparatus for portable electronic device media data storage |
US20140321624A1 (en) * | 2011-05-09 | 2014-10-30 | Google Inc. | Automatically establishing a telephonic connection between devices |
US20140330769A1 (en) * | 2012-05-08 | 2014-11-06 | 24/7 Customer, Inc. | Predictive 411 |
US20150011249A1 (en) * | 2011-04-27 | 2015-01-08 | Google Inc. | Mobile device location determination using wi-fi signals |
US8948779B1 (en) * | 2012-02-01 | 2015-02-03 | Sprint Communications Company L.P. | Communication profiles for mobile devices based on historical characteristics |
US8949212B1 (en) * | 2011-07-08 | 2015-02-03 | Hariharan Dhandapani | Location-based informaton display |
US8972357B2 (en) * | 2012-02-24 | 2015-03-03 | Placed, Inc. | System and method for data collection to validate location data |
US20150073685A1 (en) * | 2013-09-09 | 2015-03-12 | Electronics And Telecommunications Research Institute | General-purpose vehicle remote control device and method |
US8984030B2 (en) | 2011-05-04 | 2015-03-17 | International Business Machines Corporation | Journaling and integrity in mobile clouded collaborative spaces |
US20150143281A1 (en) * | 2013-11-19 | 2015-05-21 | Apple Inc. | Notifications and reminders based on user states |
US9052200B1 (en) * | 2014-05-30 | 2015-06-09 | Google Inc. | Automatic travel directions |
US20150264544A1 (en) * | 2012-05-14 | 2015-09-17 | Michael Lu | Classified relation networking optimization platform in open wireless architecture (owa) mobile cloud terminal device |
US20150277572A1 (en) * | 2012-10-24 | 2015-10-01 | Intel Corporation | Smart contextual display for a wearable device |
US20150287020A1 (en) * | 2014-04-03 | 2015-10-08 | Mastercard International Incorporated | Inferring cardholder from known locations |
US20150347910A1 (en) * | 2013-03-14 | 2015-12-03 | Google Inc. | Devices, methods, and associated information processing for security in a smart-sensored home |
US20160224835A1 (en) * | 2014-08-20 | 2016-08-04 | Gopro, Inc. | Scene and activity identification in video summary generation |
US9418358B2 (en) * | 2014-12-05 | 2016-08-16 | Bank Of America Corporation | Pre-configure and customize ATM interaction using mobile device |
US20160290820A1 (en) * | 2015-03-30 | 2016-10-06 | Alpine Electronics, Inc. | Method of displaying point on navigation map |
US20160314496A1 (en) * | 2013-12-27 | 2016-10-27 | Google Inc. | Notification engine |
US20160323702A1 (en) * | 2015-05-01 | 2016-11-03 | Martin Labrie | Location based information service application |
US9614920B1 (en) | 2013-12-04 | 2017-04-04 | Google Inc. | Context based group suggestion and creation |
US9628576B1 (en) * | 2013-12-04 | 2017-04-18 | Google Inc. | Application and sharer specific recipient suggestions |
US9679605B2 (en) | 2015-01-29 | 2017-06-13 | Gopro, Inc. | Variable playback speed template for video editing application |
US9721611B2 (en) | 2015-10-20 | 2017-08-01 | Gopro, Inc. | System and method of generating video from video clips based on moments of interest within the video clips |
US9734870B2 (en) | 2015-01-05 | 2017-08-15 | Gopro, Inc. | Media identifier generation for camera-captured media |
US9761278B1 (en) | 2016-01-04 | 2017-09-12 | Gopro, Inc. | Systems and methods for generating recommendations of post-capture users to edit digital media content |
US9787862B1 (en) | 2016-01-19 | 2017-10-10 | Gopro, Inc. | Apparatus and methods for generating content proxy |
US9792502B2 (en) | 2014-07-23 | 2017-10-17 | Gopro, Inc. | Generating video summaries for a video using video summary templates |
US9838730B1 (en) | 2016-04-07 | 2017-12-05 | Gopro, Inc. | Systems and methods for audio track selection in video editing |
US9871994B1 (en) | 2016-01-19 | 2018-01-16 | Gopro, Inc. | Apparatus and methods for providing content context using session metadata |
US9913081B1 (en) * | 2016-10-13 | 2018-03-06 | GM Global Technology Operations LLC | Method and device for communicating with a vehicle system module while conserving power by using two different short range wireless communication (SRWC) protocols |
US9916863B1 (en) | 2017-02-24 | 2018-03-13 | Gopro, Inc. | Systems and methods for editing videos based on shakiness measures |
US9953679B1 (en) | 2016-05-24 | 2018-04-24 | Gopro, Inc. | Systems and methods for generating a time lapse video |
US9953224B1 (en) | 2016-08-23 | 2018-04-24 | Gopro, Inc. | Systems and methods for generating a video summary |
US20180113586A1 (en) * | 2016-10-25 | 2018-04-26 | International Business Machines Corporation | Context aware user interface |
US9967515B1 (en) | 2016-06-15 | 2018-05-08 | Gopro, Inc. | Systems and methods for bidirectional speed ramping |
US10015469B2 (en) | 2012-07-03 | 2018-07-03 | Gopro, Inc. | Image blur based on 3D depth information |
US20180192263A1 (en) * | 2012-10-19 | 2018-07-05 | Facebook, Inc. | Predicting the future state of a mobile device user |
US10044972B1 (en) | 2016-09-30 | 2018-08-07 | Gopro, Inc. | Systems and methods for automatically transferring audiovisual content |
US10078644B1 (en) | 2016-01-19 | 2018-09-18 | Gopro, Inc. | Apparatus and methods for manipulating multicamera content using content proxy |
US10115297B2 (en) * | 2015-03-27 | 2018-10-30 | Google Llc | Configuring a smart home controller |
US10129464B1 (en) | 2016-02-18 | 2018-11-13 | Gopro, Inc. | User interface for creating composite images |
US10147058B1 (en) * | 2012-09-07 | 2018-12-04 | Noble Systems Corporation | Monitoring schedule adherence of call center agents |
US10229719B1 (en) | 2016-05-09 | 2019-03-12 | Gopro, Inc. | Systems and methods for generating highlights for a video |
US10306547B2 (en) | 2017-06-28 | 2019-05-28 | Microsoft Technology Licensing, Llc | Intelligent access point scanning based on a profile |
US10338955B1 (en) | 2015-10-22 | 2019-07-02 | Gopro, Inc. | Systems and methods that effectuate transmission of workflow between computing platforms |
US10354282B2 (en) * | 2013-10-31 | 2019-07-16 | International Business Machines Corporation | Communicating with a customer traveling on a route to a location |
US20190217817A1 (en) * | 2016-08-08 | 2019-07-18 | Audi Ag | Control device and method for unlocking a motor vehicle with integrated nfc-control device |
US10360663B1 (en) | 2017-04-07 | 2019-07-23 | Gopro, Inc. | Systems and methods to create a dynamic blur effect in visual content |
US10397415B1 (en) | 2016-09-30 | 2019-08-27 | Gopro, Inc. | Systems and methods for automatically transferring audiovisual content |
US20190287071A1 (en) * | 2018-03-16 | 2019-09-19 | Oracle International Corporation | Beaconized time entry system |
US10423983B2 (en) | 2014-09-16 | 2019-09-24 | Snap Inc. | Determining targeting information based on a predictive targeting model |
US10453325B2 (en) | 2015-06-01 | 2019-10-22 | Apple Inc. | Creation of reminders using activity state of an application |
US10475327B2 (en) * | 2015-06-05 | 2019-11-12 | Apple Inc. | Smart location-based reminders |
US10491741B2 (en) | 2015-06-04 | 2019-11-26 | Apple Inc. | Sending smart alerts on a device at opportune moments using sensors |
US10510050B2 (en) | 2012-09-10 | 2019-12-17 | Private Secretary, Ltd. | Meetings and events coordinating system and method |
US10512111B2 (en) * | 2017-12-12 | 2019-12-17 | Canon Kabushiki Kaisha | Electronic apparatus and control method thereof |
US10635731B2 (en) * | 2018-07-30 | 2020-04-28 | Bank Of America Corporation | System for generating and executing editable multiple-step requests |
US10664778B2 (en) | 2007-05-17 | 2020-05-26 | Avaya Inc. | Negotiation of a future communication by use of a personal virtual assistant (PVA) |
US10817898B2 (en) | 2015-08-13 | 2020-10-27 | Placed, Llc | Determining exposures to content presented by physical objects |
US10963293B2 (en) | 2010-12-21 | 2021-03-30 | Microsoft Technology Licensing, Llc | Interactions with contextual and task-based computing environments |
US20210158250A1 (en) * | 2019-11-26 | 2021-05-27 | Alarm.Com Incorporated | System and method integrating smart vehicles with a monitoring system |
US11042151B2 (en) | 2018-11-08 | 2021-06-22 | Toyota Motor North America, Inc. | Systems and methods for remotely activating a vehicle |
US11099023B1 (en) * | 2016-01-05 | 2021-08-24 | Open Invention Network Llc | Intermediate navigation destinations |
US11106988B2 (en) | 2016-10-06 | 2021-08-31 | Gopro, Inc. | Systems and methods for determining predicted risk for a flight path of an unmanned aerial vehicle |
US20210365976A1 (en) * | 2020-05-22 | 2021-11-25 | Capital One Services, Llc | Utilizing machine learning and a smart transaction card to automatically identify optimal prices and rebates for items during in-person shopping |
US11221996B2 (en) * | 2007-01-07 | 2022-01-11 | Apple Inc. | Widget synchronization in accordance with synchronization preferences |
US11423718B2 (en) * | 2018-02-14 | 2022-08-23 | Samsung Electronics Co., Ltd. | Electronic device and method for providing key |
US20220303235A1 (en) * | 2012-06-12 | 2022-09-22 | Line Corporation | Messenger-linked service system and method using a social graph of a messenger platform |
US20220322187A1 (en) * | 2020-10-02 | 2022-10-06 | Samsung Electronics Co., Ltd. | Network switching device and method for operating of network switching device |
US20230176910A1 (en) * | 2011-03-25 | 2023-06-08 | Google Llc | Provision of computer resources based on location history |
US11734712B2 (en) | 2012-02-24 | 2023-08-22 | Foursquare Labs, Inc. | Attributing in-store visits to media consumption based on data collected from user devices |
US11880853B2 (en) * | 2020-11-03 | 2024-01-23 | Capital One Services, Llc | Utilizing machine learning and transaction data to determine fuel prices at fuel stations |
US11967222B2 (en) | 2022-02-03 | 2024-04-23 | Google Llc | Configuring a smart home controller |
Families Citing this family (65)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7676394B2 (en) | 2005-09-14 | 2010-03-09 | Jumptap, Inc. | Dynamic bidding and expected value |
US7769764B2 (en) | 2005-09-14 | 2010-08-03 | Jumptap, Inc. | Mobile advertisement syndication |
US8532633B2 (en) | 2005-09-14 | 2013-09-10 | Jumptap, Inc. | System for targeting advertising content to a plurality of mobile communication facilities |
US9703892B2 (en) | 2005-09-14 | 2017-07-11 | Millennial Media Llc | Predictive text completion for a mobile communication facility |
US8660891B2 (en) | 2005-11-01 | 2014-02-25 | Millennial Media | Interactive mobile advertisement banners |
US8812526B2 (en) | 2005-09-14 | 2014-08-19 | Millennial Media, Inc. | Mobile content cross-inventory yield optimization |
US8503995B2 (en) | 2005-09-14 | 2013-08-06 | Jumptap, Inc. | Mobile dynamic advertisement creation and placement |
US8819659B2 (en) | 2005-09-14 | 2014-08-26 | Millennial Media, Inc. | Mobile search service instant activation |
US9201979B2 (en) | 2005-09-14 | 2015-12-01 | Millennial Media, Inc. | Syndication of a behavioral profile associated with an availability condition using a monetization platform |
US7752209B2 (en) | 2005-09-14 | 2010-07-06 | Jumptap, Inc. | Presenting sponsored content on a mobile communication facility |
US8688671B2 (en) | 2005-09-14 | 2014-04-01 | Millennial Media | Managing sponsored content based on geographic region |
US20100076994A1 (en) * | 2005-11-05 | 2010-03-25 | Adam Soroca | Using Mobile Communication Facility Device Data Within a Monetization Platform |
US10911894B2 (en) | 2005-09-14 | 2021-02-02 | Verizon Media Inc. | Use of dynamic content generation parameters based on previous performance of those parameters |
US10038756B2 (en) | 2005-09-14 | 2018-07-31 | Millenial Media LLC | Managing sponsored content based on device characteristics |
US8805339B2 (en) | 2005-09-14 | 2014-08-12 | Millennial Media, Inc. | Categorization of a mobile user profile based on browse and viewing behavior |
US8364540B2 (en) * | 2005-09-14 | 2013-01-29 | Jumptap, Inc. | Contextual targeting of content using a monetization platform |
US7577665B2 (en) | 2005-09-14 | 2009-08-18 | Jumptap, Inc. | User characteristic influenced search results |
US7702318B2 (en) | 2005-09-14 | 2010-04-20 | Jumptap, Inc. | Presentation of sponsored content based on mobile transaction event |
US8832100B2 (en) | 2005-09-14 | 2014-09-09 | Millennial Media, Inc. | User transaction history influenced search results |
US9076175B2 (en) | 2005-09-14 | 2015-07-07 | Millennial Media, Inc. | Mobile comparison shopping |
US8666376B2 (en) | 2005-09-14 | 2014-03-04 | Millennial Media | Location based mobile shopping affinity program |
US8238888B2 (en) | 2006-09-13 | 2012-08-07 | Jumptap, Inc. | Methods and systems for mobile coupon placement |
US9471925B2 (en) | 2005-09-14 | 2016-10-18 | Millennial Media Llc | Increasing mobile interactivity |
US8615719B2 (en) | 2005-09-14 | 2013-12-24 | Jumptap, Inc. | Managing sponsored content for delivery to mobile communication facilities |
US10592930B2 (en) | 2005-09-14 | 2020-03-17 | Millenial Media, LLC | Syndication of a behavioral profile using a monetization platform |
US8989718B2 (en) | 2005-09-14 | 2015-03-24 | Millennial Media, Inc. | Idle screen advertising |
US20110313853A1 (en) | 2005-09-14 | 2011-12-22 | Jorey Ramer | System for targeting advertising content to a plurality of mobile communication facilities |
US8103545B2 (en) | 2005-09-14 | 2012-01-24 | Jumptap, Inc. | Managing payment for sponsored content presented to mobile communication facilities |
US8364521B2 (en) | 2005-09-14 | 2013-01-29 | Jumptap, Inc. | Rendering targeted advertisement on mobile communication facilities |
US7660581B2 (en) | 2005-09-14 | 2010-02-09 | Jumptap, Inc. | Managing sponsored content based on usage history |
US8209344B2 (en) | 2005-09-14 | 2012-06-26 | Jumptap, Inc. | Embedding sponsored content in mobile applications |
US9058406B2 (en) | 2005-09-14 | 2015-06-16 | Millennial Media, Inc. | Management of multiple advertising inventories using a monetization platform |
US7912458B2 (en) | 2005-09-14 | 2011-03-22 | Jumptap, Inc. | Interaction analysis and prioritization of mobile content |
US8751292B2 (en) * | 2007-10-19 | 2014-06-10 | Intuit Inc. | Method and system for providing sellers access to selected consumers |
US20090112707A1 (en) * | 2007-10-26 | 2009-04-30 | Benjamin Weiss | Method and system for using a point-of sale system to correlate transactions to a coupon database |
ES2358027B1 (en) * | 2009-05-18 | 2012-03-15 | Vodafone España, S.A.U | SYSTEM AND METHOD FOR ENABLING MESSENGER? A TRIPPED BY PROXIMITY, IN CERTAIN AREAS? COVERAGE AREAS FOR SOCIAL NETWORKS AND COMMUNITY-BASED SERVICES. |
KR101544371B1 (en) * | 2009-08-07 | 2015-08-17 | 삼성전자주식회사 | Mobile terminal reflecting user's environment and method for operating the same |
KR101584058B1 (en) * | 2009-08-07 | 2016-01-12 | 삼성전자주식회사 | Mobile terminal providing environment adapted to present situation and method for operating the same |
US8861844B2 (en) | 2010-03-29 | 2014-10-14 | Ebay Inc. | Pre-computing digests for image similarity searching of image-based listings in a network-based publication system |
US9405773B2 (en) | 2010-03-29 | 2016-08-02 | Ebay Inc. | Searching for more products like a specified product |
US9792638B2 (en) | 2010-03-29 | 2017-10-17 | Ebay Inc. | Using silhouette images to reduce product selection error in an e-commerce environment |
US8412594B2 (en) | 2010-08-28 | 2013-04-02 | Ebay Inc. | Multilevel silhouettes in an online shopping environment |
US8478306B2 (en) | 2010-11-10 | 2013-07-02 | Google Inc. | Self-aware profile switching on a mobile computing device |
FR2968497B1 (en) | 2010-12-02 | 2013-07-05 | Yoosfer | METHOD AND SYSTEM FOR DIFFUSING COMPUTER CONTENT TO A MOBILE TERMINAL |
US20120221413A1 (en) * | 2011-02-25 | 2012-08-30 | Motorola Mobility, Inc. | Intelligent presentation of advertising with navigation |
CN102158881B (en) * | 2011-04-28 | 2013-07-31 | 武汉虹信通信技术有限责任公司 | Method and device for completely evaluating 3G visual telephone quality |
US20130085860A1 (en) * | 2011-10-04 | 2013-04-04 | Ebay Inc. | Systems and methods to deliver context sensitive dynamic mobile advertisements |
US20130173796A1 (en) * | 2011-12-30 | 2013-07-04 | United Video Properties, Inc. | Systems and methods for managing a media content queue |
US9503683B2 (en) * | 2012-03-27 | 2016-11-22 | Google Inc. | Providing users access to applications during video communications |
US10423984B2 (en) * | 2012-10-16 | 2019-09-24 | Facebook, Inc. | Sponsored stories in notifications |
CN104903970A (en) * | 2012-11-06 | 2015-09-09 | 科蒂公司 | UV LED lightbar setting UV-curable nail formulation |
US9432806B2 (en) | 2012-12-04 | 2016-08-30 | Ebay Inc. | Dynamic geofence based on members within |
US10402915B2 (en) | 2013-05-10 | 2019-09-03 | Samsung Electronics Co., Ltd. | Methods and systems for on-device social grouping |
US10341421B2 (en) | 2013-05-10 | 2019-07-02 | Samsung Electronics Co., Ltd. | On-device social grouping for automated responses |
US9426629B2 (en) | 2013-08-28 | 2016-08-23 | At&T Mobility Ii Llc | Autonomous pull and display of location based service applications by a mobile device based on context of the mobile device |
US9659306B1 (en) | 2013-09-20 | 2017-05-23 | Intuit Inc. | Method and system for linking social media systems and financial management systems to provide social group-based marketing programs |
US10296946B2 (en) * | 2013-12-24 | 2019-05-21 | Amobee, Inc. | Audience usage pattern analysis |
US9325654B2 (en) | 2014-02-28 | 2016-04-26 | Aol Inc. | Systems and methods for optimizing message notification timing based on electronic content consumption associated with a geographic location |
US10318990B2 (en) | 2014-04-01 | 2019-06-11 | Ebay Inc. | Selecting users relevant to a geofence |
US9584968B2 (en) | 2014-05-21 | 2017-02-28 | Aol Inc. | Systems and methods for deploying dynamic geo-fences based on content consumption levels in a geographic location |
US11477602B2 (en) * | 2014-06-10 | 2022-10-18 | Verizon Patent And Licensing Inc. | Systems and methods for optimizing and refining message notification timing |
JP6246085B2 (en) * | 2014-07-01 | 2017-12-13 | 株式会社オプティム | Portable terminal, content panel display method, portable terminal program |
US20160071227A1 (en) * | 2014-09-09 | 2016-03-10 | Mastercard International Incorporated | Transaction Systems and Methods for Travelers Using Mass-Transit Vehicles and Facilities |
CN105824588A (en) | 2015-01-06 | 2016-08-03 | 阿里巴巴集团控股有限公司 | Display method and apparatus of reminding messages |
FR3046270B1 (en) * | 2015-12-24 | 2018-11-16 | Worldline | AUTOMATIC OR SEMI-AUTOMATIC SUGGESTION, LAUNCH AND DOWNLOAD SYSTEM FOR INTELLIGENT MOBILE OBJECT APPLICATIONS |
Citations (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6073075A (en) * | 1995-11-01 | 2000-06-06 | Hitachi, Ltd. | Method and system for providing information for a mobile terminal |
US6259405B1 (en) * | 1995-06-06 | 2001-07-10 | Wayport, Inc. | Geographic based communications service |
US6310955B1 (en) * | 1998-06-16 | 2001-10-30 | Lucent Technologies Inc. | Methods and apparatus for enabling portable telephone handset to automatically go off-hook |
US20010047272A1 (en) * | 2000-02-29 | 2001-11-29 | Frietas Nathanial X. | Flexible wireless advertisement integration in wireless software applications |
US6359571B1 (en) * | 1998-10-13 | 2002-03-19 | Hitachi, Ltd. | Broadcasting type information providing system and travel environment information collecting device |
US20020052781A1 (en) * | 1999-09-10 | 2002-05-02 | Avantgo, Inc. | Interactive advertisement mechanism on a mobile device |
US6397246B1 (en) * | 1998-11-13 | 2002-05-28 | International Business Machines Corporation | Method and system for processing document requests in a network system |
US20020077118A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a wireless service provider |
US20020095312A1 (en) * | 2000-09-22 | 2002-07-18 | Tammy Wheat | Facilitating realtime information interexchange between a telecommunications network and a service provider |
US20020121989A1 (en) * | 2001-03-05 | 2002-09-05 | Ronnie Burns | Method and system for providing personalized traffic alerts |
US6456234B1 (en) * | 2000-06-07 | 2002-09-24 | William J. Johnson | System and method for proactive content delivery by situation location |
US20030001727A1 (en) * | 2001-06-29 | 2003-01-02 | Steinmark Daniel E. | System and method for creating an adjusted alarm time |
US20030050046A1 (en) * | 2001-07-09 | 2003-03-13 | Shane Conneely | Notification infrastructure for sending device-specific wireless notifications |
US6581025B2 (en) * | 1995-04-17 | 2003-06-17 | Discovision Associates | Time and work tracker for wireless devices |
US6675204B2 (en) * | 1998-04-08 | 2004-01-06 | Access Co., Ltd. | Wireless communication device with markup language based man-machine interface |
US6678613B2 (en) * | 2001-09-21 | 2004-01-13 | International Business Machines Corporation | Method and apparatus for notifying a user of an appointment |
US20040076279A1 (en) * | 2000-05-16 | 2004-04-22 | John Taschereau | Method and system for providing geographically targeted information and advertising |
US20040127198A1 (en) * | 2002-12-30 | 2004-07-01 | Roskind James A. | Automatically changing a mobile device configuration based on environmental condition |
US6766017B1 (en) * | 1998-04-14 | 2004-07-20 | Samsung Electronics Co., Ltd. | Dialing method in mobile telephone |
US6782253B1 (en) * | 2000-08-10 | 2004-08-24 | Koninklijke Philips Electronics N.V. | Mobile micro portal |
US6795710B1 (en) * | 2001-01-05 | 2004-09-21 | Palmone, Inc. | Identifying client patterns using online location-based derivative analysis |
US20040225437A1 (en) * | 2003-02-05 | 2004-11-11 | Yoshinori Endo | Route search method and traffic information display method for a navigation device |
US6823188B1 (en) * | 2000-07-26 | 2004-11-23 | International Business Machines Corporation | Automated proximity notification |
US6847969B1 (en) * | 1999-05-03 | 2005-01-25 | Streetspace, Inc. | Method and system for providing personalized online services and advertisements in public spaces |
US20050102329A1 (en) * | 2003-11-10 | 2005-05-12 | Jiang Zhaowei C. | Backup and restore in mobile applications |
US6922567B1 (en) * | 2000-08-22 | 2005-07-26 | Telefonaktiebolaget L.M. Ericsson | Systems, methods and computer program products for identifying items of interest that are geographically proximate to wireless communicator users |
US6961567B1 (en) * | 2000-12-07 | 2005-11-01 | Palm, Inc. | Generic activation and registration framework for wireless devices |
US20050245241A1 (en) * | 2004-04-28 | 2005-11-03 | Terry Durand | Mobile advertising and directory assistance |
US20060036490A1 (en) * | 2004-08-13 | 2006-02-16 | Michelle Sagalyn | Methods and apparatus for marketing community-oriented advertising opportunities |
US20060041472A1 (en) * | 2004-08-23 | 2006-02-23 | Lukose Rajan M | Systems and methods of interfacing an advertisement with a message presentation client |
US20060149461A1 (en) * | 2004-12-31 | 2006-07-06 | Henry Rowley | Transportation routing |
US20060156209A1 (en) * | 2003-02-25 | 2006-07-13 | Satoshi Matsuura | Application program prediction method and mobile terminal |
US20060293928A1 (en) * | 2005-06-27 | 2006-12-28 | Eric Schumacher | Method and system to recommend insurance plans |
US20070111711A1 (en) * | 2005-11-17 | 2007-05-17 | Nitesh Ratnakar | Yellow Book for the Phone |
US20070123305A1 (en) * | 2005-11-29 | 2007-05-31 | Chun-Wei Chen | Method For Securing a Near Field Communication Device of a Mobile Phone |
US20070149256A1 (en) * | 2005-12-22 | 2007-06-28 | Burgan John M | Method of hibernating and pre-booting a mobile communication device to reduce apparent start up time |
US20070198698A1 (en) * | 2006-02-23 | 2007-08-23 | Boyd John D | System and method for scheduling content updates in a content-based application |
US7266379B2 (en) * | 2001-05-30 | 2007-09-04 | Palm, Inc. | Resource location through location history |
US20070263863A1 (en) * | 2006-05-10 | 2007-11-15 | Ketul Sakhpara | Intelligent user interface |
US20070271234A1 (en) * | 2006-05-22 | 2007-11-22 | Ravikiran Chickmangalore N | Information Exchange Among Members of a Group of Communication Device Users |
US20080032666A1 (en) * | 2006-08-07 | 2008-02-07 | Microsoft Corporation | Location based notification services |
US20080052413A1 (en) * | 2006-08-28 | 2008-02-28 | Microsoft Corporation | Serving locally relevant advertisements |
US20080132219A1 (en) * | 2003-12-15 | 2008-06-05 | International Business Machines Corporation | Method and Apparatus for Preconditioning Mobile Devices for Network and Other Operations |
US20080160966A1 (en) * | 2006-12-28 | 2008-07-03 | Mckiou Kevin W | Service zones for providing location-based services in a wireless network |
US20080167938A1 (en) * | 2006-12-29 | 2008-07-10 | Aol Llc | Reserving a time block in a calendar application to account for a travel time between geographic locations of appointments |
US20080195457A1 (en) * | 2006-08-16 | 2008-08-14 | Bellsouth Intellectual Property Corporation | Methods and computer-readable media for location-based targeted advertising |
US20080195312A1 (en) * | 2007-02-14 | 2008-08-14 | Bellsouth Intellectual Property Corporation | Methods, systems, and computer program products for schedule management based on locations of wireless devices |
US7424447B2 (en) * | 2002-08-26 | 2008-09-09 | Aperture Investments, Llc | List-based selection system and methods for using same |
US20080249969A1 (en) * | 2007-04-04 | 2008-10-09 | The Hong Kong University Of Science And Technology | Intelligent agent for distributed services for mobile devices |
US20080268868A1 (en) * | 2007-03-23 | 2008-10-30 | Jill Maitland | Method and apparatus for merchant search and offer presentation |
US20090076906A1 (en) * | 2007-09-14 | 2009-03-19 | Palm, Inc. | System and method for providing advertisement data to a mobile computing device |
US8073460B1 (en) * | 2007-03-08 | 2011-12-06 | Amazon Technologies, Inc. | System and method for providing advertisement based on mobile device travel patterns |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6549792B1 (en) | 1999-06-25 | 2003-04-15 | Agere Systems Inc. | Accelerometer influenced communication device |
US6947976B1 (en) * | 2000-07-31 | 2005-09-20 | Vindigo, Inc. | System and method for providing location-based and time-based information to a user of a handheld device |
US20020137530A1 (en) * | 2001-03-08 | 2002-09-26 | Katyayini Karve | Cellular telephone with SMS message forwarding |
US20030186722A1 (en) * | 2002-03-28 | 2003-10-02 | Comverse, Ltd. | Method and device for real time GSM user device profile interrogation and registration |
US20040203643A1 (en) * | 2002-06-13 | 2004-10-14 | Bhogal Kulvir Singh | Communication device interaction with a personal information manager |
DE10228608A1 (en) | 2002-06-26 | 2004-01-15 | Süß, Karin | Mobilephone with integrated alarm system, has movement sensor for releasing alarm signal via detection of accelerating torque |
TW591398B (en) * | 2002-09-26 | 2004-06-11 | Tatung Co | Method of implementing a plurality of system tray areas |
US20050096982A1 (en) * | 2003-09-16 | 2005-05-05 | Morton David L. | Method of viral marketing for email and internet based advertising |
WO2005071932A1 (en) | 2004-01-22 | 2005-08-04 | Siemens Aktiengesellschaft | Mobile telephone |
EP1631050B1 (en) | 2004-08-26 | 2007-06-13 | Samsung Electronics Co., Ltd. | Mobile system, method, and computer program for managing conversational user interface according to detected usage patterns |
US7817983B2 (en) | 2005-03-14 | 2010-10-19 | Qualcomm Incorporated | Method and apparatus for monitoring usage patterns of a wireless device |
US8289158B2 (en) * | 2005-04-14 | 2012-10-16 | Research In Motion Limited | System and method for customizing notifications in a mobile electronic device |
US20070150825A1 (en) * | 2005-12-22 | 2007-06-28 | Jack Jachner | Custom presence icons |
US8571580B2 (en) * | 2006-06-01 | 2013-10-29 | Loopt Llc. | Displaying the location of individuals on an interactive map display on a mobile communication device |
US20080291022A1 (en) * | 2007-05-23 | 2008-11-27 | Erick Simon Amador | Automatic locating system |
US20090006194A1 (en) * | 2007-06-27 | 2009-01-01 | Microsoft Corporation | Location, destination and other contextual information-based mobile advertisements |
-
2009
- 2009-03-11 US US12/402,386 patent/US20100161720A1/en not_active Abandoned
- 2009-04-13 US US12/422,871 patent/US8135777B2/en not_active Expired - Fee Related
- 2009-12-17 DE DE112009004349T patent/DE112009004349T5/en not_active Withdrawn
- 2009-12-17 WO PCT/US2009/068525 patent/WO2010075174A2/en active Application Filing
- 2009-12-17 GB GB1112452A patent/GB2478507A/en not_active Withdrawn
Patent Citations (56)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6581025B2 (en) * | 1995-04-17 | 2003-06-17 | Discovision Associates | Time and work tracker for wireless devices |
US6259405B1 (en) * | 1995-06-06 | 2001-07-10 | Wayport, Inc. | Geographic based communications service |
US6073075A (en) * | 1995-11-01 | 2000-06-06 | Hitachi, Ltd. | Method and system for providing information for a mobile terminal |
US6675204B2 (en) * | 1998-04-08 | 2004-01-06 | Access Co., Ltd. | Wireless communication device with markup language based man-machine interface |
US6766017B1 (en) * | 1998-04-14 | 2004-07-20 | Samsung Electronics Co., Ltd. | Dialing method in mobile telephone |
US6310955B1 (en) * | 1998-06-16 | 2001-10-30 | Lucent Technologies Inc. | Methods and apparatus for enabling portable telephone handset to automatically go off-hook |
US6359571B1 (en) * | 1998-10-13 | 2002-03-19 | Hitachi, Ltd. | Broadcasting type information providing system and travel environment information collecting device |
US6397246B1 (en) * | 1998-11-13 | 2002-05-28 | International Business Machines Corporation | Method and system for processing document requests in a network system |
US6847969B1 (en) * | 1999-05-03 | 2005-01-25 | Streetspace, Inc. | Method and system for providing personalized online services and advertisements in public spaces |
US20020052781A1 (en) * | 1999-09-10 | 2002-05-02 | Avantgo, Inc. | Interactive advertisement mechanism on a mobile device |
US20010047272A1 (en) * | 2000-02-29 | 2001-11-29 | Frietas Nathanial X. | Flexible wireless advertisement integration in wireless software applications |
US20040076279A1 (en) * | 2000-05-16 | 2004-04-22 | John Taschereau | Method and system for providing geographically targeted information and advertising |
US6456234B1 (en) * | 2000-06-07 | 2002-09-24 | William J. Johnson | System and method for proactive content delivery by situation location |
US6823188B1 (en) * | 2000-07-26 | 2004-11-23 | International Business Machines Corporation | Automated proximity notification |
US6782253B1 (en) * | 2000-08-10 | 2004-08-24 | Koninklijke Philips Electronics N.V. | Mobile micro portal |
US6922567B1 (en) * | 2000-08-22 | 2005-07-26 | Telefonaktiebolaget L.M. Ericsson | Systems, methods and computer program products for identifying items of interest that are geographically proximate to wireless communicator users |
US20020095312A1 (en) * | 2000-09-22 | 2002-07-18 | Tammy Wheat | Facilitating realtime information interexchange between a telecommunications network and a service provider |
US20070178899A1 (en) * | 2000-12-07 | 2007-08-02 | Palm, Inc. | Mobile device capable of registering with multiple servers |
US20060030306A1 (en) * | 2000-12-07 | 2006-02-09 | Kuhn Brian G | Generic activation and registration framework for wireless devices |
US6961567B1 (en) * | 2000-12-07 | 2005-11-01 | Palm, Inc. | Generic activation and registration framework for wireless devices |
US20020077118A1 (en) * | 2000-12-19 | 2002-06-20 | Zellner Samuel N. | Location blocking service from a wireless service provider |
US7536190B1 (en) * | 2001-01-05 | 2009-05-19 | Palm, Inc. | Providing content based on user-specific information from a wireless device |
US7103370B1 (en) * | 2001-01-05 | 2006-09-05 | Palm, Inc. | Identifying client patterns using online location-based derivative analysis |
US6795710B1 (en) * | 2001-01-05 | 2004-09-21 | Palmone, Inc. | Identifying client patterns using online location-based derivative analysis |
US20020121989A1 (en) * | 2001-03-05 | 2002-09-05 | Ronnie Burns | Method and system for providing personalized traffic alerts |
US7266379B2 (en) * | 2001-05-30 | 2007-09-04 | Palm, Inc. | Resource location through location history |
US20030001727A1 (en) * | 2001-06-29 | 2003-01-02 | Steinmark Daniel E. | System and method for creating an adjusted alarm time |
US20030050046A1 (en) * | 2001-07-09 | 2003-03-13 | Shane Conneely | Notification infrastructure for sending device-specific wireless notifications |
US6678613B2 (en) * | 2001-09-21 | 2004-01-13 | International Business Machines Corporation | Method and apparatus for notifying a user of an appointment |
US7424447B2 (en) * | 2002-08-26 | 2008-09-09 | Aperture Investments, Llc | List-based selection system and methods for using same |
US20040127198A1 (en) * | 2002-12-30 | 2004-07-01 | Roskind James A. | Automatically changing a mobile device configuration based on environmental condition |
US20040225437A1 (en) * | 2003-02-05 | 2004-11-11 | Yoshinori Endo | Route search method and traffic information display method for a navigation device |
US20060156209A1 (en) * | 2003-02-25 | 2006-07-13 | Satoshi Matsuura | Application program prediction method and mobile terminal |
US20050102329A1 (en) * | 2003-11-10 | 2005-05-12 | Jiang Zhaowei C. | Backup and restore in mobile applications |
US20080132219A1 (en) * | 2003-12-15 | 2008-06-05 | International Business Machines Corporation | Method and Apparatus for Preconditioning Mobile Devices for Network and Other Operations |
US20050245241A1 (en) * | 2004-04-28 | 2005-11-03 | Terry Durand | Mobile advertising and directory assistance |
US20060036490A1 (en) * | 2004-08-13 | 2006-02-16 | Michelle Sagalyn | Methods and apparatus for marketing community-oriented advertising opportunities |
US20060041472A1 (en) * | 2004-08-23 | 2006-02-23 | Lukose Rajan M | Systems and methods of interfacing an advertisement with a message presentation client |
US20060149461A1 (en) * | 2004-12-31 | 2006-07-06 | Henry Rowley | Transportation routing |
US20060293928A1 (en) * | 2005-06-27 | 2006-12-28 | Eric Schumacher | Method and system to recommend insurance plans |
US20070111711A1 (en) * | 2005-11-17 | 2007-05-17 | Nitesh Ratnakar | Yellow Book for the Phone |
US20070123305A1 (en) * | 2005-11-29 | 2007-05-31 | Chun-Wei Chen | Method For Securing a Near Field Communication Device of a Mobile Phone |
US20070149256A1 (en) * | 2005-12-22 | 2007-06-28 | Burgan John M | Method of hibernating and pre-booting a mobile communication device to reduce apparent start up time |
US20070198698A1 (en) * | 2006-02-23 | 2007-08-23 | Boyd John D | System and method for scheduling content updates in a content-based application |
US20070263863A1 (en) * | 2006-05-10 | 2007-11-15 | Ketul Sakhpara | Intelligent user interface |
US20070271234A1 (en) * | 2006-05-22 | 2007-11-22 | Ravikiran Chickmangalore N | Information Exchange Among Members of a Group of Communication Device Users |
US20080032666A1 (en) * | 2006-08-07 | 2008-02-07 | Microsoft Corporation | Location based notification services |
US20080195457A1 (en) * | 2006-08-16 | 2008-08-14 | Bellsouth Intellectual Property Corporation | Methods and computer-readable media for location-based targeted advertising |
US20080052413A1 (en) * | 2006-08-28 | 2008-02-28 | Microsoft Corporation | Serving locally relevant advertisements |
US20080160966A1 (en) * | 2006-12-28 | 2008-07-03 | Mckiou Kevin W | Service zones for providing location-based services in a wireless network |
US20080167938A1 (en) * | 2006-12-29 | 2008-07-10 | Aol Llc | Reserving a time block in a calendar application to account for a travel time between geographic locations of appointments |
US20080195312A1 (en) * | 2007-02-14 | 2008-08-14 | Bellsouth Intellectual Property Corporation | Methods, systems, and computer program products for schedule management based on locations of wireless devices |
US8073460B1 (en) * | 2007-03-08 | 2011-12-06 | Amazon Technologies, Inc. | System and method for providing advertisement based on mobile device travel patterns |
US20080268868A1 (en) * | 2007-03-23 | 2008-10-30 | Jill Maitland | Method and apparatus for merchant search and offer presentation |
US20080249969A1 (en) * | 2007-04-04 | 2008-10-09 | The Hong Kong University Of Science And Technology | Intelligent agent for distributed services for mobile devices |
US20090076906A1 (en) * | 2007-09-14 | 2009-03-19 | Palm, Inc. | System and method for providing advertisement data to a mobile computing device |
Cited By (211)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11221996B2 (en) * | 2007-01-07 | 2022-01-11 | Apple Inc. | Widget synchronization in accordance with synchronization preferences |
US10664778B2 (en) | 2007-05-17 | 2020-05-26 | Avaya Inc. | Negotiation of a future communication by use of a personal virtual assistant (PVA) |
US10504124B2 (en) * | 2008-04-21 | 2019-12-10 | Verizon Patent And Licensing Inc. | Aggregation and use of information relating to a users context for personalized advertisements |
US20090265236A1 (en) * | 2008-04-21 | 2009-10-22 | Verizon Business Network Services Inc. | Aggregation and use of information relating to a users context for personalized advertisements |
US20100185391A1 (en) * | 2009-01-21 | 2010-07-22 | Htc Corporation | Method, apparatus, and recording medium for selecting location |
US9223882B2 (en) * | 2009-01-21 | 2015-12-29 | Htc Corporation | Method, apparatus, and recording medium for selecting location of mobile device |
US20100235552A1 (en) * | 2009-03-16 | 2010-09-16 | Apple Inc. | Accessory interface to portable media device using sessions |
US9069908B2 (en) | 2009-03-16 | 2015-06-30 | Apple Inc. | Accessory and mobile computing device communication using an application communication protocol |
US9736281B2 (en) | 2009-03-16 | 2017-08-15 | Apple Inc. | Accessory and mobile computing device communication using an application communication protocol |
US8775652B2 (en) | 2009-03-16 | 2014-07-08 | Apple Inc. | Communication between a mobile computing device and an accessory using an accessory protocol and an application protocol |
US20100235518A1 (en) * | 2009-03-16 | 2010-09-16 | Apple Inc. | Connection to multiple accessories with multiple accessory-specific protocols |
US8700789B2 (en) | 2009-03-16 | 2014-04-15 | Apple Inc. | Accessory and mobile computing device communication using an application communication protocol |
US8639733B2 (en) | 2009-03-16 | 2014-01-28 | Apple Inc. | Automatic identification of compatible applications and accessories |
US20100235373A1 (en) * | 2009-03-16 | 2010-09-16 | Apple Inc. | Automatic identification of compatible applications and accessories |
US8554924B2 (en) | 2009-03-16 | 2013-10-08 | Apple Inc. | Connection to multiple accessories with multiple accessory-specific protocols |
US8402145B2 (en) | 2009-03-16 | 2013-03-19 | Apple Inc. | Application communication with external accessories |
US8402128B2 (en) * | 2009-03-16 | 2013-03-19 | Apple Inc. | Accessory attachment protocol and responsive actions |
US20100235425A1 (en) * | 2009-03-16 | 2010-09-16 | Apple Inc. | Accessory and mobile computing device communication using an application communication protocol |
US8341318B2 (en) | 2009-03-16 | 2012-12-25 | Apple Inc. | Techniques for facilitating communication between an accessory and a mobile computing device using application specific protocols |
US20100235454A1 (en) * | 2009-03-16 | 2010-09-16 | Apple Inc. | Application communication with external accessories |
US9354901B2 (en) * | 2009-06-22 | 2016-05-31 | Clayster Asia Ltd. | Method and computer system for introducing client devices into a client-server network |
US20120197982A1 (en) * | 2009-06-22 | 2012-08-02 | Clayster Asia Ltd. | Method and computer system for introducing client devices into a client-server network |
US20110029383A1 (en) * | 2009-07-28 | 2011-02-03 | Randy Engel | System and method for providing advertising content via an integrated home based device |
US9693310B2 (en) | 2009-09-16 | 2017-06-27 | Samsung Electronics Co., Ltd. | Apparatus and method for reducing power consumption in portable terminal |
US20120185717A1 (en) * | 2009-09-16 | 2012-07-19 | Samsung Electronics Co., Ltd. | Apparatus and method for reducing power consumption in portable terminal |
US9485735B2 (en) | 2009-09-16 | 2016-11-01 | Samsung Electronics Co., Ltd. | Apparatus and method for reducing power consumption in portable terminal |
US10993185B2 (en) | 2009-09-16 | 2021-04-27 | Samsung Electronics Co., Ltd. | Apparatus and method for reducing power consumption in portable terminal |
US9167527B2 (en) * | 2009-09-16 | 2015-10-20 | Samsung Electronics Co., Ltd. | Apparatus and method for reducing power consumption in portable terminal |
US9854530B2 (en) | 2009-09-16 | 2017-12-26 | Samsung Electronics Co., Ltd. | Apparatus and method for reducing power consumption in portable terminal |
US10111175B2 (en) | 2009-09-16 | 2018-10-23 | Samsung Electronics Co., Ltd. | Apparatus and method for reducing power consumption in portable terminal |
US20110196969A1 (en) * | 2010-02-08 | 2011-08-11 | Paccar Inc | In-vehicle communication device with social networking |
US9060381B2 (en) * | 2010-02-08 | 2015-06-16 | Paccar Inc | In-vehicle communication device with social networking |
US8285840B2 (en) * | 2010-03-15 | 2012-10-09 | Cellco Partnership | Using social networking to help users purchase mobile applications and devices |
US20110225291A1 (en) * | 2010-03-15 | 2011-09-15 | Cellco Partnership D/B/A Verizon Wireless | Using social networking to help users purchase mobile applications and devices |
US9584624B2 (en) * | 2010-04-15 | 2017-02-28 | Blackberry Limited | Method and system for transmitting an application to a device |
US20110258301A1 (en) * | 2010-04-15 | 2011-10-20 | Research In Motion Limited | Method and system for transmitting an application to a device |
US8386589B2 (en) * | 2010-05-21 | 2013-02-26 | Qnx Software Systems Limited | System that provides embedded software to an embedded system |
US20110289493A1 (en) * | 2010-05-21 | 2011-11-24 | Derrick Keefe | System that provides embedded software to an embedded system |
US8200244B2 (en) * | 2010-05-24 | 2012-06-12 | Nice Systems Ltd. | Method and system for mobile station location |
US8478294B2 (en) | 2010-05-24 | 2013-07-02 | Nice-Systems Ltd. | Method and system for mobile station location |
US8588808B2 (en) | 2010-05-24 | 2013-11-19 | Nice-Systems Ltd. | Method and system for estimation of mobile station velocity in a cellular system based on geographical data |
US20110287784A1 (en) * | 2010-05-24 | 2011-11-24 | Moshe Levin | Method and system for mobile station location |
US9798822B2 (en) * | 2010-06-29 | 2017-10-24 | Apple Inc. | Location based grouping of browsing histories |
US20110320450A1 (en) * | 2010-06-29 | 2011-12-29 | Alice Liu | Location based grouping of browsing histories |
US20120042257A1 (en) * | 2010-08-11 | 2012-02-16 | Microsoft Corporation | Updating application data after anticipating imminent use |
US20120084248A1 (en) * | 2010-09-30 | 2012-04-05 | Microsoft Corporation | Providing suggestions based on user intent |
US20140047016A1 (en) * | 2010-10-21 | 2014-02-13 | Bindu Rama Rao | Server infrastructure, mobile client device and app for mobile blogging and sharing |
JP2012108614A (en) * | 2010-11-15 | 2012-06-07 | Sharp Corp | Terminal and advertisement display method |
CN102446118A (en) * | 2010-11-17 | 2012-05-09 | 微软公司 | Contextual and task focused computing |
US20120124126A1 (en) * | 2010-11-17 | 2012-05-17 | Microsoft Corporation | Contextual and task focused computing |
US20120136905A1 (en) * | 2010-11-30 | 2012-05-31 | Pullara Samuel J | Information feed update mechanism |
US10474720B2 (en) * | 2010-11-30 | 2019-11-12 | Tw Seagull Acquisition Corp. | Information feed update mechanism |
US20120143952A1 (en) * | 2010-12-01 | 2012-06-07 | Von Graf Fred | System and method for event framework |
US10963293B2 (en) | 2010-12-21 | 2021-03-30 | Microsoft Technology Licensing, Llc | Interactions with contextual and task-based computing environments |
US8751636B2 (en) * | 2010-12-22 | 2014-06-10 | Facebook, Inc. | Timing for providing relevant notifications for a user based on user interaction with notifications |
US9385986B2 (en) | 2010-12-22 | 2016-07-05 | Facebook, Inc. | Timing for providing relevant notifications for a user based on user interaction with notifications |
US20120166530A1 (en) * | 2010-12-22 | 2012-06-28 | Erick Tseng | Timing for providing relevant notifications for a user based on user interaction with notifications |
US20140010121A1 (en) * | 2011-03-21 | 2014-01-09 | Mayuresh Madhukar Patil | Method and system for providing calendar services in a universal plug and play home network environment |
KR20140016948A (en) * | 2011-03-21 | 2014-02-10 | 삼성전자주식회사 | Method and system for providing calender services in a universal plug and play home network environment |
US10952038B2 (en) * | 2011-03-21 | 2021-03-16 | Samsung Electronics Co., Ltd. | Method and system for providing calendar services in a universal plug and play home network environment |
US20230176910A1 (en) * | 2011-03-25 | 2023-06-08 | Google Llc | Provision of computer resources based on location history |
US20120296680A1 (en) * | 2011-04-25 | 2012-11-22 | Scott Bergen Jantz | Provision of Alert Messages to Customers of an Establishment |
US10078804B2 (en) | 2011-04-25 | 2018-09-18 | Heartland Payment Systems, Llc | Provision of alert messages to customers of an establishment |
US9299037B2 (en) * | 2011-04-25 | 2016-03-29 | Heartland Payment Systems, Inc. | Provision of alert messages to customers of an establishment |
US20150011249A1 (en) * | 2011-04-27 | 2015-01-08 | Google Inc. | Mobile device location determination using wi-fi signals |
US8984030B2 (en) | 2011-05-04 | 2015-03-17 | International Business Machines Corporation | Journaling and integrity in mobile clouded collaborative spaces |
US20140321624A1 (en) * | 2011-05-09 | 2014-10-30 | Google Inc. | Automatically establishing a telephonic connection between devices |
US20140242971A1 (en) * | 2011-05-20 | 2014-08-28 | Renault S.A.S. | Access and customization of a motor vehicle by telephone |
US9021364B2 (en) * | 2011-05-31 | 2015-04-28 | Microsoft Technology Licensing, Llc | Accessing web content based on mobile contextual data |
US20120311465A1 (en) * | 2011-05-31 | 2012-12-06 | Microsoft Corporation | Accessing Web Content Based on Mobile Contextual Data |
US9339727B2 (en) * | 2011-06-15 | 2016-05-17 | Microsoft Technology Licensing, Llc | Position-based decision to provide service |
US10981070B2 (en) | 2011-06-15 | 2021-04-20 | Microsoft Technology Licensing, Llc | Position-based decision to provide service |
US20120322548A1 (en) * | 2011-06-15 | 2012-12-20 | Microsoft Corporation | Position-based decision to provide service |
US20120323692A1 (en) * | 2011-06-16 | 2012-12-20 | Jon Shutter | Method and System for Providing Location Targeted Advertisements |
US20140228052A1 (en) * | 2011-07-01 | 2014-08-14 | Alcatel Lucent | Method for alerting a mobile device at a predetermined destination |
US8949212B1 (en) * | 2011-07-08 | 2015-02-03 | Hariharan Dhandapani | Location-based informaton display |
US20130055121A1 (en) * | 2011-08-29 | 2013-02-28 | Samsung Electronics Co., Ltd. | Apparatus and method for displaying splash screen |
US9125012B2 (en) * | 2011-09-09 | 2015-09-01 | Interdigital Patent Holdings, Inc. | Methods and apparatus for accessing localized applications |
US20130065585A1 (en) * | 2011-09-09 | 2013-03-14 | Interdigital Patent Holdings, Inc. | Methods and apparatus for accessing localized applications |
TWI587718B (en) * | 2011-09-09 | 2017-06-11 | 內數位專利控股公司 | Methods and apparatus for accessing localized applications |
US10904733B2 (en) | 2011-09-09 | 2021-01-26 | Interdigital Patent Holdings, Inc. | Accessing local networks in a communications network |
US10064211B2 (en) | 2011-09-09 | 2018-08-28 | Interdigital Patent Holdings, Inc. | Accessing applications by devices in proximity in a communications network |
US9542711B2 (en) * | 2011-10-07 | 2017-01-10 | Salesforce.Com, Inc. | Computer implemented methods and apparatus for providing selective notifications in an online social network |
US20130091229A1 (en) * | 2011-10-07 | 2013-04-11 | Salesforce.Com, Inc. | Computer Implemented Methods And Apparatus For Providing Selective Notifications In An Online Social Network |
US8862533B2 (en) | 2011-11-21 | 2014-10-14 | Motorola Mobility Llc | Method and apparatus for portable electronic device media data storage |
US8948779B1 (en) * | 2012-02-01 | 2015-02-03 | Sprint Communications Company L.P. | Communication profiles for mobile devices based on historical characteristics |
US8972357B2 (en) * | 2012-02-24 | 2015-03-03 | Placed, Inc. | System and method for data collection to validate location data |
US10204137B2 (en) | 2012-02-24 | 2019-02-12 | Snap Inc. | System and method for data collection to validate location data |
US11734712B2 (en) | 2012-02-24 | 2023-08-22 | Foursquare Labs, Inc. | Attributing in-store visits to media consumption based on data collected from user devices |
US11182383B1 (en) | 2012-02-24 | 2021-11-23 | Placed, Llc | System and method for data collection to validate location data |
US8768876B2 (en) | 2012-02-24 | 2014-07-01 | Placed, Inc. | Inference pipeline system and method |
US9256832B2 (en) | 2012-02-24 | 2016-02-09 | Placed, Inc. | Inference pipeline system and method |
US20130232010A1 (en) * | 2012-03-02 | 2013-09-05 | International Business Machines Corporation | Mobile device cluster advertisement delivery |
US9824373B2 (en) * | 2012-03-02 | 2017-11-21 | International Business Machines Corporation | Mobile device cluster advertisement delivery |
US9224158B2 (en) | 2012-03-02 | 2015-12-29 | International Business Machines Corporation | Mobile device cluster advertisement delivery |
CN104145289A (en) * | 2012-03-02 | 2014-11-12 | 国际商业机器公司 | Mobile device cluster advertisement delivery |
US9460237B2 (en) * | 2012-05-08 | 2016-10-04 | 24/7 Customer, Inc. | Predictive 411 |
US20140330769A1 (en) * | 2012-05-08 | 2014-11-06 | 24/7 Customer, Inc. | Predictive 411 |
US20150264544A1 (en) * | 2012-05-14 | 2015-09-17 | Michael Lu | Classified relation networking optimization platform in open wireless architecture (owa) mobile cloud terminal device |
US10003943B2 (en) * | 2012-05-14 | 2018-06-19 | Michael Lu | Classified relation networking optimization platform in open wireless architecture (OWA) mobile cloud terminal device |
US20220303235A1 (en) * | 2012-06-12 | 2022-09-22 | Line Corporation | Messenger-linked service system and method using a social graph of a messenger platform |
US11863506B2 (en) * | 2012-06-12 | 2024-01-02 | Line Corporation | Messenger-linked service system and method using a social graph of a messenger platform |
US10015469B2 (en) | 2012-07-03 | 2018-07-03 | Gopro, Inc. | Image blur based on 3D depth information |
US10147058B1 (en) * | 2012-09-07 | 2018-12-04 | Noble Systems Corporation | Monitoring schedule adherence of call center agents |
US10510050B2 (en) | 2012-09-10 | 2019-12-17 | Private Secretary, Ltd. | Meetings and events coordinating system and method |
US20140074536A1 (en) * | 2012-09-10 | 2014-03-13 | Dana Meushar | Meetings and Events Coordinating System and Method |
US20180192263A1 (en) * | 2012-10-19 | 2018-07-05 | Facebook, Inc. | Predicting the future state of a mobile device user |
US10321283B2 (en) * | 2012-10-19 | 2019-06-11 | Facebook, Inc. | Predicting the future state of a mobile device user |
US20150277572A1 (en) * | 2012-10-24 | 2015-10-01 | Intel Corporation | Smart contextual display for a wearable device |
US20140156281A1 (en) * | 2012-12-03 | 2014-06-05 | Qualcomm Incorporated | Voice-controlled configuration of an automation system |
US20140171117A1 (en) * | 2012-12-14 | 2014-06-19 | Anthony G. LaMarca | Location-aware management of lists of uniform resource locators (urls) for mobile devices |
US20140237109A1 (en) * | 2013-02-17 | 2014-08-21 | Onavo Mobile Ltd. | Techniques for determining a mobile application download attribution |
US9491223B2 (en) * | 2013-02-17 | 2016-11-08 | Onavo Mobile Ltd. | Techniques for determining a mobile application download attribution |
US20140257696A1 (en) * | 2013-03-07 | 2014-09-11 | Kamal Zamer | Travel Pattern Analysis |
US9798979B2 (en) * | 2013-03-14 | 2017-10-24 | Google Inc. | Devices, methods, and associated information processing for security in a smart-sensored home |
US10853733B2 (en) | 2013-03-14 | 2020-12-01 | Google Llc | Devices, methods, and associated information processing for security in a smart-sensored home |
US20150347910A1 (en) * | 2013-03-14 | 2015-12-03 | Google Inc. | Devices, methods, and associated information processing for security in a smart-sensored home |
US20170124629A1 (en) * | 2013-03-29 | 2017-05-04 | Paypal, Inc. | Routine suggestion system |
US20140297455A1 (en) * | 2013-03-29 | 2014-10-02 | Ebay Inc. | Routine suggestion system |
US9644591B2 (en) * | 2013-09-09 | 2017-05-09 | Electronics And Telecommunications Research Institute | General-purpose vehicle remote control device and method |
US20150073685A1 (en) * | 2013-09-09 | 2015-03-12 | Electronics And Telecommunications Research Institute | General-purpose vehicle remote control device and method |
US10354281B2 (en) * | 2013-10-31 | 2019-07-16 | International Business Machines Corporation | Communicating with a customer traveling on a route to a location |
US10354282B2 (en) * | 2013-10-31 | 2019-07-16 | International Business Machines Corporation | Communicating with a customer traveling on a route to a location |
US20150143281A1 (en) * | 2013-11-19 | 2015-05-21 | Apple Inc. | Notifications and reminders based on user states |
US9628576B1 (en) * | 2013-12-04 | 2017-04-18 | Google Inc. | Application and sharer specific recipient suggestions |
US9614920B1 (en) | 2013-12-04 | 2017-04-04 | Google Inc. | Context based group suggestion and creation |
US20160314496A1 (en) * | 2013-12-27 | 2016-10-27 | Google Inc. | Notification engine |
US20150287020A1 (en) * | 2014-04-03 | 2015-10-08 | Mastercard International Incorporated | Inferring cardholder from known locations |
US9052200B1 (en) * | 2014-05-30 | 2015-06-09 | Google Inc. | Automatic travel directions |
US9685194B2 (en) | 2014-07-23 | 2017-06-20 | Gopro, Inc. | Voice-based video tagging |
US10776629B2 (en) | 2014-07-23 | 2020-09-15 | Gopro, Inc. | Scene and activity identification in video summary generation |
US11069380B2 (en) | 2014-07-23 | 2021-07-20 | Gopro, Inc. | Scene and activity identification in video summary generation |
US10339975B2 (en) | 2014-07-23 | 2019-07-02 | Gopro, Inc. | Voice-based video tagging |
US10074013B2 (en) | 2014-07-23 | 2018-09-11 | Gopro, Inc. | Scene and activity identification in video summary generation |
US11776579B2 (en) | 2014-07-23 | 2023-10-03 | Gopro, Inc. | Scene and activity identification in video summary generation |
US9792502B2 (en) | 2014-07-23 | 2017-10-17 | Gopro, Inc. | Generating video summaries for a video using video summary templates |
US10643663B2 (en) | 2014-08-20 | 2020-05-05 | Gopro, Inc. | Scene and activity identification in video summary generation based on motion detected in a video |
US10262695B2 (en) * | 2014-08-20 | 2019-04-16 | Gopro, Inc. | Scene and activity identification in video summary generation |
US20160224835A1 (en) * | 2014-08-20 | 2016-08-04 | Gopro, Inc. | Scene and activity identification in video summary generation |
US9666232B2 (en) | 2014-08-20 | 2017-05-30 | Gopro, Inc. | Scene and activity identification in video summary generation based on motion detected in a video |
US9646652B2 (en) | 2014-08-20 | 2017-05-09 | Gopro, Inc. | Scene and activity identification in video summary generation based on motion detected in a video |
US10423983B2 (en) | 2014-09-16 | 2019-09-24 | Snap Inc. | Determining targeting information based on a predictive targeting model |
US11625755B1 (en) | 2014-09-16 | 2023-04-11 | Foursquare Labs, Inc. | Determining targeting information based on a predictive targeting model |
US9418358B2 (en) * | 2014-12-05 | 2016-08-16 | Bank Of America Corporation | Pre-configure and customize ATM interaction using mobile device |
US10096341B2 (en) | 2015-01-05 | 2018-10-09 | Gopro, Inc. | Media identifier generation for camera-captured media |
US9734870B2 (en) | 2015-01-05 | 2017-08-15 | Gopro, Inc. | Media identifier generation for camera-captured media |
US10559324B2 (en) | 2015-01-05 | 2020-02-11 | Gopro, Inc. | Media identifier generation for camera-captured media |
US9679605B2 (en) | 2015-01-29 | 2017-06-13 | Gopro, Inc. | Variable playback speed template for video editing application |
US20190066489A1 (en) * | 2015-03-27 | 2019-02-28 | Google Llc | Configuring a Smart Home Controller |
US10559192B2 (en) * | 2015-03-27 | 2020-02-11 | Google Llc | Configuring a smart home controller |
US10115297B2 (en) * | 2015-03-27 | 2018-10-30 | Google Llc | Configuring a smart home controller |
US9528848B2 (en) * | 2015-03-30 | 2016-12-27 | Alpine Electronics, Inc. | Method of displaying point on navigation map |
US20160290820A1 (en) * | 2015-03-30 | 2016-10-06 | Alpine Electronics, Inc. | Method of displaying point on navigation map |
US9866995B2 (en) * | 2015-05-01 | 2018-01-09 | Martin Labrie | Location based information service application |
US10511935B2 (en) * | 2015-05-01 | 2019-12-17 | Martin Labrie | Location based information service application |
US20160323702A1 (en) * | 2015-05-01 | 2016-11-03 | Martin Labrie | Location based information service application |
US10453325B2 (en) | 2015-06-01 | 2019-10-22 | Apple Inc. | Creation of reminders using activity state of an application |
US11386769B2 (en) | 2015-06-01 | 2022-07-12 | Apple Inc. | Creation of reminders using activity state of an application |
US11721196B2 (en) | 2015-06-01 | 2023-08-08 | Apple Inc. | Creation of reminders using activity state of an application |
US10609207B2 (en) | 2015-06-04 | 2020-03-31 | Apple Inc. | Sending smart alerts on a device at opportune moments using sensors |
US10491741B2 (en) | 2015-06-04 | 2019-11-26 | Apple Inc. | Sending smart alerts on a device at opportune moments using sensors |
US10475327B2 (en) * | 2015-06-05 | 2019-11-12 | Apple Inc. | Smart location-based reminders |
US10817898B2 (en) | 2015-08-13 | 2020-10-27 | Placed, Llc | Determining exposures to content presented by physical objects |
US11961116B2 (en) | 2015-08-13 | 2024-04-16 | Foursquare Labs, Inc. | Determining exposures to content presented by physical objects |
US9721611B2 (en) | 2015-10-20 | 2017-08-01 | Gopro, Inc. | System and method of generating video from video clips based on moments of interest within the video clips |
US10338955B1 (en) | 2015-10-22 | 2019-07-02 | Gopro, Inc. | Systems and methods that effectuate transmission of workflow between computing platforms |
US9761278B1 (en) | 2016-01-04 | 2017-09-12 | Gopro, Inc. | Systems and methods for generating recommendations of post-capture users to edit digital media content |
US11099023B1 (en) * | 2016-01-05 | 2021-08-24 | Open Invention Network Llc | Intermediate navigation destinations |
US10402445B2 (en) | 2016-01-19 | 2019-09-03 | Gopro, Inc. | Apparatus and methods for manipulating multicamera content using content proxy |
US10078644B1 (en) | 2016-01-19 | 2018-09-18 | Gopro, Inc. | Apparatus and methods for manipulating multicamera content using content proxy |
US9871994B1 (en) | 2016-01-19 | 2018-01-16 | Gopro, Inc. | Apparatus and methods for providing content context using session metadata |
US9787862B1 (en) | 2016-01-19 | 2017-10-10 | Gopro, Inc. | Apparatus and methods for generating content proxy |
US10129464B1 (en) | 2016-02-18 | 2018-11-13 | Gopro, Inc. | User interface for creating composite images |
US9838730B1 (en) | 2016-04-07 | 2017-12-05 | Gopro, Inc. | Systems and methods for audio track selection in video editing |
US10341712B2 (en) | 2016-04-07 | 2019-07-02 | Gopro, Inc. | Systems and methods for audio track selection in video editing |
US10229719B1 (en) | 2016-05-09 | 2019-03-12 | Gopro, Inc. | Systems and methods for generating highlights for a video |
US9953679B1 (en) | 2016-05-24 | 2018-04-24 | Gopro, Inc. | Systems and methods for generating a time lapse video |
US9967515B1 (en) | 2016-06-15 | 2018-05-08 | Gopro, Inc. | Systems and methods for bidirectional speed ramping |
US10742924B2 (en) | 2016-06-15 | 2020-08-11 | Gopro, Inc. | Systems and methods for bidirectional speed ramping |
US11223795B2 (en) | 2016-06-15 | 2022-01-11 | Gopro, Inc. | Systems and methods for bidirectional speed ramping |
US20190217817A1 (en) * | 2016-08-08 | 2019-07-18 | Audi Ag | Control device and method for unlocking a motor vehicle with integrated nfc-control device |
US10493956B2 (en) * | 2016-08-08 | 2019-12-03 | Audi Ag | Control device and method for unlocking a motor vehicle with integrated NFC-control device |
US11062143B2 (en) | 2016-08-23 | 2021-07-13 | Gopro, Inc. | Systems and methods for generating a video summary |
US9953224B1 (en) | 2016-08-23 | 2018-04-24 | Gopro, Inc. | Systems and methods for generating a video summary |
US10726272B2 (en) | 2016-08-23 | 2020-07-28 | Go Pro, Inc. | Systems and methods for generating a video summary |
US11508154B2 (en) | 2016-08-23 | 2022-11-22 | Gopro, Inc. | Systems and methods for generating a video summary |
US10560655B2 (en) | 2016-09-30 | 2020-02-11 | Gopro, Inc. | Systems and methods for automatically transferring audiovisual content |
US10397415B1 (en) | 2016-09-30 | 2019-08-27 | Gopro, Inc. | Systems and methods for automatically transferring audiovisual content |
US10560591B2 (en) | 2016-09-30 | 2020-02-11 | Gopro, Inc. | Systems and methods for automatically transferring audiovisual content |
US10044972B1 (en) | 2016-09-30 | 2018-08-07 | Gopro, Inc. | Systems and methods for automatically transferring audiovisual content |
US11106988B2 (en) | 2016-10-06 | 2021-08-31 | Gopro, Inc. | Systems and methods for determining predicted risk for a flight path of an unmanned aerial vehicle |
US9913081B1 (en) * | 2016-10-13 | 2018-03-06 | GM Global Technology Operations LLC | Method and device for communicating with a vehicle system module while conserving power by using two different short range wireless communication (SRWC) protocols |
US10452410B2 (en) * | 2016-10-25 | 2019-10-22 | International Business Machines Corporation | Context aware user interface |
US20180113586A1 (en) * | 2016-10-25 | 2018-04-26 | International Business Machines Corporation | Context aware user interface |
US10901758B2 (en) | 2016-10-25 | 2021-01-26 | International Business Machines Corporation | Context aware user interface |
US9916863B1 (en) | 2017-02-24 | 2018-03-13 | Gopro, Inc. | Systems and methods for editing videos based on shakiness measures |
US10360663B1 (en) | 2017-04-07 | 2019-07-23 | Gopro, Inc. | Systems and methods to create a dynamic blur effect in visual content |
US10817992B2 (en) | 2017-04-07 | 2020-10-27 | Gopro, Inc. | Systems and methods to create a dynamic blur effect in visual content |
US10306547B2 (en) | 2017-06-28 | 2019-05-28 | Microsoft Technology Licensing, Llc | Intelligent access point scanning based on a profile |
US10512111B2 (en) * | 2017-12-12 | 2019-12-17 | Canon Kabushiki Kaisha | Electronic apparatus and control method thereof |
US11423718B2 (en) * | 2018-02-14 | 2022-08-23 | Samsung Electronics Co., Ltd. | Electronic device and method for providing key |
US20190287071A1 (en) * | 2018-03-16 | 2019-09-19 | Oracle International Corporation | Beaconized time entry system |
US10635731B2 (en) * | 2018-07-30 | 2020-04-28 | Bank Of America Corporation | System for generating and executing editable multiple-step requests |
US11042151B2 (en) | 2018-11-08 | 2021-06-22 | Toyota Motor North America, Inc. | Systems and methods for remotely activating a vehicle |
US20210158250A1 (en) * | 2019-11-26 | 2021-05-27 | Alarm.Com Incorporated | System and method integrating smart vehicles with a monitoring system |
US11915171B2 (en) * | 2019-11-26 | 2024-02-27 | Alarm.Com Incorporated | System and method integrating smart vehicles with a monitoring system |
US11836755B2 (en) * | 2020-05-22 | 2023-12-05 | Capital One Services, Llc | Utilizing machine learning and a smart transaction card to automatically identify optimal prices and rebates for items during in-person shopping |
US20210365976A1 (en) * | 2020-05-22 | 2021-11-25 | Capital One Services, Llc | Utilizing machine learning and a smart transaction card to automatically identify optimal prices and rebates for items during in-person shopping |
US20220322187A1 (en) * | 2020-10-02 | 2022-10-06 | Samsung Electronics Co., Ltd. | Network switching device and method for operating of network switching device |
US11880853B2 (en) * | 2020-11-03 | 2024-01-23 | Capital One Services, Llc | Utilizing machine learning and transaction data to determine fuel prices at fuel stations |
US11967222B2 (en) | 2022-02-03 | 2024-04-23 | Google Llc | Configuring a smart home controller |
Also Published As
Publication number | Publication date |
---|---|
US20100159904A1 (en) | 2010-06-24 |
US8135777B2 (en) | 2012-03-13 |
WO2010075174A2 (en) | 2010-07-01 |
GB2478507A (en) | 2011-09-07 |
WO2010075174A3 (en) | 2010-10-14 |
DE112009004349T5 (en) | 2012-07-05 |
GB201112452D0 (en) | 2011-08-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20100161720A1 (en) | System and method for providing content to a mobile device | |
US9852449B2 (en) | System and method for providing advertisement data to a mobile computing device | |
US11120372B2 (en) | Performing actions associated with task items that represent tasks to perform | |
US11493347B2 (en) | Using historical location data to improve estimates of location | |
KR101797184B1 (en) | Providing digital content based on expected user behavior | |
US8805348B2 (en) | Diary synchronization for smart phone applications | |
US8504074B2 (en) | System and method for providing advertisement data to a mobile computing device | |
US10230803B2 (en) | System and method for improved mapping and routing | |
US20170032248A1 (en) | Activity Detection Based On Activity Models | |
CN104335205A (en) | Actionable reminder entries | |
JP2012518854A (en) | System and method for delivering sponsored landmarks and location labels | |
TW200831862A (en) | Virtual location markers for mobile mapping | |
KR20140132329A (en) | System, apparatus and method for organizing and presenting offers through virtual channels |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: PALM, INC.,CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COLLIGAN, EDWARD T.;VADASZ, DAVID;COUSINEAU, BERNARD P.;AND OTHERS;SIGNING DATES FROM 20090413 TO 20090507;REEL/FRAME:022741/0817 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A.,NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:PALM, INC.;REEL/FRAME:023406/0671 Effective date: 20091002 Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:PALM, INC.;REEL/FRAME:023406/0671 Effective date: 20091002 |
|
AS | Assignment |
Owner name: PALM, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:024630/0474 Effective date: 20100701 |
|
AS | Assignment |
Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PALM, INC.;REEL/FRAME:025204/0809 Effective date: 20101027 |
|
AS | Assignment |
Owner name: PALM, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.;REEL/FRAME:030341/0459 Effective date: 20130430 |
|
AS | Assignment |
Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PALM, INC.;REEL/FRAME:031837/0659 Effective date: 20131218 Owner name: PALM, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.;REEL/FRAME:031837/0544 Effective date: 20131218 Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PALM, INC.;REEL/FRAME:031837/0239 Effective date: 20131218 |
|
AS | Assignment |
Owner name: QUALCOMM INCORPORATED, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HEWLETT-PACKARD COMPANY;HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.;PALM, INC.;REEL/FRAME:032132/0001 Effective date: 20140123 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |