Many users may utilize a search interface, such as a search app, a search website, a social network, etc., to research and/or plan a trip. In an example, a user may search a social network for vacation images for Venice Beach. The user may submit various search queries relating to hotels, air flights, car rental agencies, attractions, and/or other information for Venice Beach through a search website. The search website may provide the user with search results that the user may explore and/or bookmark for later access. The user may call various travel accommodation and entertainment businesses while planning the Venice Beach trip. In this way, the user may research and plan a trip through search interfaces and/or devices (e.g., phone calls through a mobile device; map directions through a mobile map app; etc.).
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key factors or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Among other things, one or more systems and/or techniques for providing a recommendation based upon a predicted travel intent are provided herein. For example, a set of user signals, indicative of an intent for a user to travel to a destination, may be identified based upon a variety of information associated with the user and/or devices used by the user. For example, a user signal may correspond to location information associated with a device (e.g., GPS check-in data obtained when the device accesses a website), search query history (e.g., a query for flights, hotels, locations, attractions, businesses, events, and/or other travel and/or destination information), user browsing history, messages associated with the user, social network posts by the user (e.g., the user may post about a desire to go on a vacation), a calendar entry (e.g., the user may have an entry about meeting with a travel agent or renting a car), a phone call (e.g., a phone call log entry to a hotel reservation company), etc. The set of user signals may be evaluated to determine a predicted travel intent for the user to travel to a destination (e.g., a classifier may be used to identify features indicative of travel, such as by evaluating search terms of queries submitted by the user to identify a location that is a threshold distance away from the user). In an example, a predicted travel date may be derived from the set of user signals. The predicted travel date may be used to identify events (e.g., skiing in winter, fishing season, a baseball game during a baseball season), flights, hotel availability, etc.
It may be appreciated that in one example, a destination may correspond to multiple locations, and is not limited to a single location. In an example, a vacation destination may comprise a cross country trip that includes Las Vegas, the Grand Canyon, San Francisco, and/or a cruise leaving from San Francisco (e.g., the set of user search signals may comprise search terms relating to long distance car rentals, Las Vegas, the Grand Canyon, San Francisco, a cruise line, etc.). In another example, a Europe destination may comprise a local airport, an airport in Rome, Rome, a train ride to Germany, Germany, and/or other locations in Europe (e.g., the set of user search signals may comprise search terms relating to Rome, Germany, and/or other European locations). In this way, the predicted travel intent may correspond to a destination encompassing one or more locations. It may also be appreciated that a user may not end up travelling to the destination and/or the user may travel to some (e.g., one or more) but not all locations associated with the destination.
One or more recommendations may be created based upon the predicted travel intent. A recommendation may comprise weather information, attraction information (e.g., an amusement park), travel accommodation information (e.g., a link to a hotel reservation app), an event at the destination (e.g., a baseball game during a baseball season, a festival, etc.), a news story associated with the destination, a social network photo associated with the destination, a travel route, and/or a plethora of other content and/or information associated with traveling to the destination. In an example, the recommendation may be pushed to a device of the user (e.g., an alert on a mobile device). In another example, the recommendation may be provided as a message through a message system (e.g., email, text, etc.). In another example, the recommendation may be provided through a calendar or task interface. In another example, the recommendation and/or the predicted travel intent may be used to influence information provided by a website. For example, a search engine website may provide one or more information interfaces (e.g., a carousel of news stories provided by a homepage of a search engine website) that may comprise content derived from the recommendation and/or the predicted travel intent (e.g., a celebrity news story may be replaced with a local news story for the destination). In another example, a search engine results page (SERP) may be modified based upon the recommendation and/or the predicted travel intent (e.g., a search result suggestion may correspond to a business at the destination). In another example, a travel interface (e.g., displayed by a website or a mobile app such as a search app hosted on a mobile device) may be provided. The travel interface may be populated with information (e.g., weather, attractions, travel accommodations, selectable interests, travel dates, travel route planning information, social network photos of the destination, and/or a wide variety of other information) associated with the destination.
To the accomplishment of the foregoing and related ends, the following description and annexed drawings set forth certain illustrative aspects and implementations. These are indicative of but a few of the various ways in which one or more aspects may be employed. Other aspects, advantages, and novel features of the disclosure will become apparent from the following detailed description when considered in conjunction with the annexed drawings.
The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are generally used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth to provide an understanding of the claimed subject matter. It may be evident, however, that the claimed subject matter may be practiced without these specific details. In other instances, structures and devices are illustrated in block diagram form in order to facilitate describing the claimed subject matter.
One or more techniques and/or systems for providing a recommendation based upon a predicted travel intent are provided. For example, a predicted travel intent that a user will travel to a destination may be determined. The predicted travel intent may be used to generate recommendations (e.g., a recommendation to book a theatre show the weekend that the user may travel to the destination), populate a travel interface (e.g., a mobile app and/or a website may provide travel accommodation information, weather, attraction information, travel planning functionality, and/or a variety of other information and/or functionality associated with traveling to the destination), and/or may be used to influence that selection of information that is provided by app and/or websites (e.g., a website may modify news interfaces with information associated with the destination).
An embodiment of providing a recommendation based upon a predicted travel intent is illustrated by an exemplary method 100 of
In an example, the destination may correspond to multiple locations (e.g., a trip to LA may involve the beach, an amusement park, and/or other locations near or outside of LA). For example, the set of user signals may be evaluated to identify a set of potential travel locations (e.g., the user may search for “LA vacations”, a particular “amusement park outside of LA”, a “what beaches are within an hour of LA”, and/or other search queries corresponding to locations that may be associated with LA). The set of potential locations may be clustered to create one or more location clusters. In an example, a location cluster comprises one or more potential travel locations of the set of potential travel locations (e.g., LA, a neighboring city comprising the beach, and a neighboring city comprising the amusement park). The destination may be identified based upon the location cluster. For example, the destination may comprise one or more potential travel locations within the location cluster. That is, the destination may correspond to just some of or all of the potential travel locations within the location cluster.
In an example, a set of historical user location data associated with a device of the user may be evaluated to determine a user hub at which the user is located for a threshold percentage of time (e.g., home, work, etc.). Responsive to a potential destination (e.g., identified from the set of user signals) being a threshold distance from the user hub (e.g., at least 50 miles away), the potential destination may be determined as the destination. Responsive to the potential destination not being the threshold distance from the user hub (e.g., less than 50 miles away), the potential destination may not be determined as the destination. In this way, the threshold distance may bet set with a value that corresponds to a threshold amount of traveling that the user will undertake for a potential destination to be considered a travel destination.
In an example, a potential travel date may be determined for the predicted travel intent based upon a global approximate travel timeline (e.g., users may approximately begin traveling after 10 days from identification of a predicted travel intent) and/or based upon an evaluation of the set of user signals (e.g., the user may submit a search query “beach cottage rates for May”, “information about the weeklong summer apple festival in LA”, etc.). The potential travel date may be used to tailor the predicted travel intent and/or recommendations provided for the predicted travel intent (e.g., events occurring at a particular time such as a ski lodge being open; current rates for travel accommodations such as flights or hotel, and/or other time sensitive information).
At 106, a recommendation may be provided based upon the predicted travel intent. The recommendation may comprise a photo from a social network (e.g., a friend of the user may have uploaded a photo of a vacation to LA), an image associated with the destination, a news story associated with the destination, an event at the destination (e.g., a summer festival), an advertisement for a business associated with the destination (e.g., a beach resort lodge), a website link to a website (e.g., a hotel reservation website), an app link to a mobile app (e.g., a travel app), a social network link to a social network profile of an entity associated with the destination (e.g., a sports team that is playing during the potential travel date), an attraction at the destination, and/or a variety of other travel task completion information (e.g., hotel reservation functionality, travel planning functionality, sports tickets to a sporting event at the destination during the potential travel date where the sporting event is identified as being interesting to the user based upon a social network profile of the user, etc.).
The recommendation may be displayed through an alert (e.g., an alert message through a mobile device), an operating system user interface (e.g., an operating system welcome screen, an operating system search charm, etc.), a mobile app, a website, a search engine homepage (e.g., a news interface may be populated with a news story for the destination), a carousel interface (e.g., a website interface through which the user may browse, such as “flip through”, various information associated with the destination), etc. In an example, the recommendation may be provided from a client device to the user (e.g., a mobile search app may identify the predicted travel intent and/or may provide the recommendation through the client device hosting the mobile search app). In another example, the recommendation may be provided to the client device for display to the user (e.g., a search engine server may identify the predicted travel intent based upon search queries submitted to a search engine website hosted by the search engine server and/or may provide the recommendation to the client device such as by displaying the recommendation through the search engine website accessed by a web browser hosted by the client device).
In an example of providing the recommendation, a user interface comprising a set of information interfaces may be identified (e.g., a website comprising a news story carousel, an operating system comprising information tiles, etc.). In another example of providing the recommendation, a travel interface may be populated with the recommendation (e.g., a mobile app, such as a travel app, may display the travel interface populated with the recommendation). In an example, the travel interface may be populated with a confirmable question as to whether the predicted travel intent is correct (e.g., the user may be solicited to enter various information used to adjust and/or elaborate on the predicted travel intent). The travel interface may be populated with a variety of information and/or functionality associated with the destination and/or traveling to the destination. For example, the travel interface may be populated with weather information for the destination, an attraction interface for the destination (e.g., an attraction name, an attraction description, an attraction image, and/or an ability to book tickets for the attraction), a travel accommodation interface for the destination (e.g., a name, image, description, and/or reservation functionality for a hotel, car rental business, and/or airline), a selectable interest interface associated with an interest (e.g., the user may select sports, shopping, running, biking, beaches, skiing, and/or a variety of interests that may be used to tailor recommendations provided for the predicted travel intent), a travel data input interface, a travel route planning interface (e.g., an interactive map), a configuration interface (e.g., the user may tailor the predicted travel intent and/or information recommended to the user for the predicted travel intent), and/or a supplemental information interface (e.g., a link to a travel planning app, a link to a website, a photo of the destination, user reviews for restaurants at the destination, and/or a plethora of other supplemental content). At 108, the method ends.
An embodiment of displaying a travel interface is illustrated by an exemplary method 300 of
Still another embodiment involves a computer-readable medium comprising processor-executable instructions configured to implement one or more of the techniques presented herein. An example embodiment of a computer-readable medium or a computer-readable device is illustrated in
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing at least some of the claims.
As used in this application, the terms “component,” “module,” “system”, “interface”, and/or the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
Furthermore, the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. Of course, many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.
Although not required, embodiments are described in the general context of “computer readable instructions” being executed by one or more computing devices. Computer readable instructions may be distributed via computer readable media (discussed below). Computer readable instructions may be implemented as program modules, such as functions, objects, Application Programming Interfaces (APIs), data structures, and the like, that perform particular tasks or implement particular abstract data types. Typically, the functionality of the computer readable instructions may be combined or distributed as desired in various environments.
In other embodiments, device 912 may include additional features and/or functionality. For example, device 912 may also include additional storage (e.g., removable and/or non-removable) including, but not limited to, magnetic storage, optical storage, and the like. Such additional storage is illustrated in
The term “computer readable media” as used herein includes computer storage media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions or other data. Memory 918 and storage 920 are examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by device 912. Any such computer storage media may be part of device 912.
Device 912 may also include communication connection(s) 926 that allows device 912 to communicate with other devices. Communication connection(s) 926 may include, but is not limited to, a modem, a Network Interface Card (NIC), an integrated network interface, a radio frequency transmitter/receiver, an infrared port, a USB connection, or other interfaces for connecting computing device 912 to other computing devices. Communication connection(s) 926 may include a wired connection or a wireless connection. Communication connection(s) 926 may transmit and/or receive communication media.
The term “computer readable media” may include communication media. Communication media typically embodies computer readable instructions or other data in a “modulated data signal” such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” may include a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
Device 912 may include input device(s) 924 such as keyboard, mouse, pen, voice input device, touch input device, infrared cameras, video input devices, and/or any other input device. Output device(s) 922 such as one or more displays, speakers, printers, and/or any other output device may also be included in device 912. Input device(s) 924 and output device(s) 922 may be connected to device 912 via a wired connection, wireless connection, or any combination thereof. In one embodiment, an input device or an output device from another computing device may be used as input device(s) 924 or output device(s) 922 for computing device 912.
Components of computing device 912 may be connected by various interconnects, such as a bus. Such interconnects may include a Peripheral Component Interconnect (PCI), such as PCI Express, a Universal Serial Bus (USB), firewire (IEEE 1394), an optical bus structure, and the like. In another embodiment, components of computing device 912 may be interconnected by a network. For example, memory 918 may be comprised of multiple physical memory units located in different physical locations interconnected by a network.
Those skilled in the art will realize that storage devices utilized to store computer readable instructions may be distributed across a network. For example, a computing device 930 accessible via a network 928 may store computer readable instructions to implement one or more embodiments provided herein. Computing device 912 may access computing device 930 and download a part or all of the computer readable instructions for execution. Alternatively, computing device 912 may download pieces of the computer readable instructions, as needed, or some instructions may be executed at computing device 912 and some at computing device 930.
Various operations of embodiments are provided herein. In one embodiment, one or more of the operations described may constitute computer readable instructions stored on one or more computer readable media, which if executed by a computing device, will cause the computing device to perform the operations described. The order in which some or all of the operations are described should not be construed as to imply that these operations are necessarily order dependent. Alternative ordering will be appreciated by one skilled in the art having the benefit of this description. Further, it will be understood that not all operations are necessarily present in each embodiment provided herein. Also, it will be understood that not all operations are necessary in some embodiments.
Further, unless specified otherwise, “first,” “second,” and/or the like are not intended to imply a temporal aspect, a spatial aspect, an ordering, etc. Rather, such terms are merely used as identifiers, names, etc. for features, elements, items, etc. For example, a first object and a second object generally correspond to object A and object B or two different or two identical objects or the same object.
Moreover, “exemplary” is used herein to mean serving as an example, instance, illustration, etc., and not necessarily as advantageous. As used herein, “or” is intended to mean an inclusive “or” rather than an exclusive “or”. In addition, “a” and “an” as used in this application are generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Also, at least one of A and B and/or the like generally means A or B or both A and B. Furthermore, to the extent that “includes”, “having”, “has”, “with”, and/or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising”.
Also, although the disclosure has been shown and described with respect to one or more implementations, equivalent alterations and modifications will occur to others skilled in the art based upon a reading and understanding of this specification and the annexed drawings. The disclosure includes all such modifications and alterations and is limited only by the scope of the following claims. In particular regard to the various functions performed by the above described components (e.g., elements, resources, etc.), the terms used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure. In addition, while a particular feature of the disclosure may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application.
This application is a continuation of U.S. application Ser. No. 14/105,095, now U.S. Pat. No. 9,618,343, filed Dec. 12, 2013, titled “PREDICTED TRAVEL INTENT,” which is hereby incorporated by reference in its entirety. To the extent appropriate, the present application claims priority to the above-referenced application.
Number | Name | Date | Kind |
---|---|---|---|
7010570 | Boles et al. | Mar 2006 | B1 |
7103642 | Chen et al. | Sep 2006 | B1 |
7162473 | Dumais | Jan 2007 | B2 |
7167903 | Percival | Jan 2007 | B2 |
7342587 | Danzig et al. | Mar 2008 | B2 |
7487918 | Kudo et al. | Feb 2009 | B2 |
7539656 | Fratkina et al. | May 2009 | B2 |
7650431 | Wang et al. | Jan 2010 | B2 |
7774348 | Delli Santi et al. | Aug 2010 | B2 |
7836403 | Viswanathan et al. | Nov 2010 | B2 |
7895178 | Skillen | Feb 2011 | B2 |
7912915 | Brin | Mar 2011 | B1 |
8024112 | Krumm et al. | Sep 2011 | B2 |
8156135 | Chi et al. | Apr 2012 | B2 |
8171048 | Ge et al. | May 2012 | B2 |
8229911 | Bennett | Jul 2012 | B2 |
8327273 | Christianson et al. | Dec 2012 | B2 |
8473507 | Loofbourrow et al. | Jun 2013 | B2 |
8510285 | Stekkelpak | Aug 2013 | B1 |
8670934 | Weir | Mar 2014 | B2 |
8754777 | Mendis | Jun 2014 | B1 |
8768616 | Kristinsson | Jul 2014 | B2 |
8775080 | Mizuno | Jul 2014 | B2 |
8855901 | Leader | Oct 2014 | B2 |
8990208 | Wang | Mar 2015 | B2 |
9134137 | Brush et al. | Sep 2015 | B2 |
9558283 | Novotny et al. | Jan 2017 | B2 |
9618343 | Kahn et al. | Apr 2017 | B2 |
9703804 | Hill et al. | Jul 2017 | B2 |
20030090515 | Chang et al. | May 2003 | A1 |
20050010647 | Durham | Jan 2005 | A1 |
20050086203 | Gauweiler | Apr 2005 | A1 |
20050131866 | Badros et al. | Jun 2005 | A1 |
20050204276 | Hosea et al. | Sep 2005 | A1 |
20050234939 | Arend et al. | Oct 2005 | A1 |
20060244768 | Witwer | Nov 2006 | A1 |
20060282304 | Bedard et al. | Dec 2006 | A1 |
20070008098 | Wong | Jan 2007 | A1 |
20070073477 | Krumm et al. | Mar 2007 | A1 |
20070073554 | Flinn | Mar 2007 | A1 |
20070112761 | Xu et al. | May 2007 | A1 |
20070266305 | Cong et al. | Nov 2007 | A1 |
20080018453 | Adler | Jan 2008 | A1 |
20080201242 | Minnis et al. | Aug 2008 | A1 |
20080209340 | Tonse et al. | Aug 2008 | A1 |
20080209350 | Sobotka et al. | Aug 2008 | A1 |
20080222119 | Dai et al. | Sep 2008 | A1 |
20090031003 | Velarde | Jan 2009 | A1 |
20090125517 | Krishnaswamy et al. | May 2009 | A1 |
20090204901 | Dharmaji et al. | Aug 2009 | A1 |
20090216563 | Sandoval et al. | Aug 2009 | A1 |
20090254971 | Herz | Oct 2009 | A1 |
20090282021 | Bennett | Nov 2009 | A1 |
20090287657 | Bennett | Nov 2009 | A1 |
20090029964 | Cameron et al. | Dec 2009 | A1 |
20100031335 | Handler | Feb 2010 | A1 |
20100145941 | Vasudevan et al. | Jun 2010 | A1 |
20100203876 | Krishnaswamy et al. | Aug 2010 | A1 |
20100295676 | Khachaturov et al. | Nov 2010 | A1 |
20100299325 | Tzvi et al. | Nov 2010 | A1 |
20110078582 | Christianson et al. | Mar 2011 | A1 |
20110087966 | Leviathan | Apr 2011 | A1 |
20110106436 | Bill | May 2011 | A1 |
20110131077 | Tan | Jun 2011 | A1 |
20110179154 | Ravichandran et al. | Jul 2011 | A1 |
20110184945 | Das et al. | Jul 2011 | A1 |
20110246906 | Caitlin et al. | Oct 2011 | A1 |
20110258556 | Kiciman | Oct 2011 | A1 |
20110270947 | Cok et al. | Nov 2011 | A1 |
20110282867 | Palermiti et al. | Nov 2011 | A1 |
20120023081 | Nayak et al. | Jan 2012 | A1 |
20120084248 | Gavrilescu | Apr 2012 | A1 |
20120109749 | Subramanian | May 2012 | A1 |
20120143859 | Lymperopoulos et al. | Jun 2012 | A1 |
20120158289 | Bernheim et al. | Jun 2012 | A1 |
20120159289 | Brush et al. | Jun 2012 | A1 |
20120295640 | Mei et al. | Nov 2012 | A1 |
20130046717 | Grigg et al. | Feb 2013 | A1 |
20130054698 | Lee | Feb 2013 | A1 |
20130080911 | Klemm | Mar 2013 | A1 |
20130097153 | Barbieri | Apr 2013 | A1 |
20130117208 | Dousse et al. | May 2013 | A1 |
20130122937 | Meyer et al. | May 2013 | A1 |
20130159110 | Rajaram et al. | Jun 2013 | A1 |
20130173398 | Wang et al. | Jul 2013 | A1 |
20130238432 | Bai | Sep 2013 | A1 |
20130260795 | Papakipos et al. | Oct 2013 | A1 |
20130275223 | Brelig et al. | Oct 2013 | A1 |
20130290827 | Smith et al. | Oct 2013 | A1 |
20130290862 | Chand et al. | Oct 2013 | A1 |
20130297688 | Zheng | Nov 2013 | A1 |
20130337838 | Kolodziej | Dec 2013 | A1 |
20140012909 | Sankar | Jan 2014 | A1 |
20140019441 | Shieh et al. | Jan 2014 | A1 |
20140025296 | Shimizu et al. | Jan 2014 | A1 |
20140025490 | Shekar | Jan 2014 | A1 |
20140025660 | Mohammed | Jan 2014 | A1 |
20140032325 | Weiss | Jan 2014 | A1 |
20140081913 | Peri | Mar 2014 | A1 |
20140223575 | Nandi | Aug 2014 | A1 |
20140279196 | Wilson et al. | Sep 2014 | A1 |
20140330769 | Nguyen et al. | Nov 2014 | A1 |
20140358427 | Fuhrman | Dec 2014 | A1 |
20140379521 | Novotny et al. | Dec 2014 | A1 |
20150052121 | Sharifi | Feb 2015 | A1 |
20150088904 | Chakrabarti | Mar 2015 | A1 |
20150106349 | Kitamorn et al. | Apr 2015 | A1 |
20150262282 | Walti | Sep 2015 | A1 |
20150269152 | Rekhi | Sep 2015 | A1 |
20160092695 | Novotny et al. | Mar 2016 | A1 |
20170083964 | Novotny et al. | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
2708197 | Dec 2011 | CA |
WO 2009146087 | Dec 2009 | WO |
Entry |
---|
Jan. 2012, Available at: http://www.locationaware.usf.edu/ongoing-research/projects/dynamic-travel-information-personalized-and-delivered-to-your-cell-phone/, 2 pages. |
“Google Now, The Right Information at Just the Right Time”, http://www.google.com/landing/now/, Sep. 17, 2013, 4 pages. |
“Transit Trip Planner & Route Information System”, Retrieved on: Dec. 9, 2013, Available at: http://www.transittripplanner.co.in/about.html, 2 pages. |
3rd Party Application Integration, Published on: Jan. 27, 2010, Available at:http://www.ecommercepartners.net/Services/Ecommerce-Solutions/3rd-Party-ApplicationInteqration.shtml, 3 pages. |
Ashbrook, et al., “Using GPS to Learn Significant Locations and Predict Movement Across Multiple Users”, In the Journal of Personal and Ubiquitous Computing, vol. 7, Issue 5, Sep., 2003, 15 pages. |
Bao, et al., “Helping Mobile Apps Bootstrap with Fewer Users”, In Proceedings of the ACM Conference on Ubiquitous Computing, Sep. 5, 2012, 10 pages. |
Bao, et al., “Location-Based and Preference-Aware Recommendation Using Sparse Geo-Social Networking Data”, In Proceedings of the 20th International Conference on Advances in Geographic Information Systems, Nov. 6, 2012, 10 pages. |
Bradley, Steven, “Progressive Disclosure: Presenting Information on a Need to Know Basis”, Published on: Jun. 14, 2010, Available at: http://www.vanseodesign.com/web-design/progressivediscolosure/, 15 pages. |
Brosso, et al., “Known User Continuous Authentication System for Consumer Application Software”, In Proceedings of the 7th IEEE Conference on Consumer Communications and Networking Conference, Jan. 9, 2010, 2 pages. |
Carousel, Published on: Jul. 15, 2009, Available at: http://developer.yahoo.com/ypatterns/selection/carousel.html, 4 pgs. |
Chakraborty, et al., “Allowing Finer Control Over Privacy Using Trust as a Benchmark”, In Proceedings of the IEEE Information Assurance Workshop, Jun. 21, 2006, 8 pages. |
Custom Website Design and Coding of Small Business Website Solutions, Retrieved on Mar. 1, 2012, available at: http://www.usgbit.com/services.html, 4 pages. |
Epelde, Gorka et al., “TV as a human interface for Ambient Intelligence environments”, 2011 IEEE Int'l. Conference on Multimedia and Expo (ICME), Jul. 11, 2011, 6 pages. |
Google Now, Published on: Jul. 9, 2012, Available at: http://en.wikipedia.org/wiki/Google_Now, 4 pages. |
Gordon, Whitson, “Net Vibes is a Super Customizable Start Page for RSS Geeks”, Published on: May 7, 2012, Available at: http://lifehacker.com/5923751/two-excellent-customizable-start-pagesworth-trvinq-now-that-iqooqles-qoinq-away, 5 pages. |
Gotz, et al., “Privacy-Aware Personalization for Mobile Advertising”, in Proceedings of the ACM Conference on Computer and Communications Security, Aug. 2011, 14 pages. |
Hochleitner, et al., “Making Devices Trustworthy: Security and Trust Feedback in the Internet of Things”, In Proceedings of the Fourth International Workshop on Security and Privacy in Spontaneous Interaction and Mobile Phone Use, Jun. 18, 2012, 6 pages. |
Horozov, et al., “Using Location for Personalized POI Recommendations in Mobile Environments”, In Proceedings of the International Symposium on Applications on Internet, Jan. 23, 2006, 7 pages. |
iGoogle, Published on: May 2005, Available at: http://en .wikipedia.org/wiki/Igoogle, 4 pages. |
Jan-Erik Ekberg (Saxena), Secure Device Pairing based on a Visual Channel; Year: 2011; Nokia Research Center, Helsinki, 17 pages. |
Lawler, Ryan, “Location-Based Mobile App Alike Recommends nearby Venues that are Just like Your Favorites”, Published on: Oct. 9, 2012 Available at: http://techcrunch.com/2012/10/09/alike/, 8 pages. |
Miluzzo, et al., “Darwin Phones: the Evolution of Sensing and Inference on Mobile Phones”, In Proceedings of the 8th International Conference on Mobile Systems, Applications, and Services, Jun. 15, 2010, 16 pages. |
Pageflakes, Published on: Dec. 11, 2005, Available at: http://www.crunchbase.com/company/pageflakes, 2 pages. |
PCT 2nd Written Opinion in PCT/US2014/059986, dated Sep. 15, 2015, 6 pages. |
PCT 2nd Written Opinion in PCT/US2015/020312, dated Feb. 22, 2016, 7 pages. |
PCT International Search Report in PCT/US2013/037871, dated Oct. 17, 2013, 8 pages. |
PCT International Search Report in PCT/US2014/059986, dated Jan. 30, 2015, 9 pages. |
PCT International Search Report in PCT/US2014/069172, dated Jun. 23, 2015, 8 pages. |
PCT International Search Report in PCT/US2015/020312, dated May 11, 2015, 11 pages. |
Roggen, et al., “Recognition of Crowd Behavior from Mobile Sensors with Pattern Analysis and Graph Clustering Methods”, In Journal of Networks and Heterogeneous Media, vol. 6, No. 3, Sep. 2011, 24 pages. |
Santos, et al., “Context Inference for Mobile Applications in the UPCASE Project”, In: Proceeding of 2nd International Conference on Mobile Wireless Middleware, Operating Systems, and Applications, Apr. 28, 2009, 14 pages. |
U.S. Appl. No. 13/458,515, Amendment and Response filed Oct. 3, 2014, 13 pages. |
U.S. Appl. No. 13/458,515, Office Action dated Jul. 15, 2014, 13 pages. |
U.S. Appl. No. 13/458,515, Office Action dated Jan. 5, 2015, 16 pages. |
U.S. Appl. No. 13/536,603, Amendment and Response filed Jun. 24, 2014, 21 pages. |
U.S. Appl. No. 13/536,603, Amendment and Response filed Jan. 23, 2015, 19 pages. |
U.S. Appl. No. 13/536,603, Amendment and Response filed Feb. 5, 2016, 20 pages. |
U.S. Appl. No. 13/536,603, Office Action dated Jan. 31, 2014, 21 pages. |
U.S. Appl. No. 13/536,603, Office Action dated Oct. 1, 2014, 26 pages. |
U.S. Appl. No. 13/536,603, Office Action dated Sep. 16, 2015, 23 pages. |
U.S. Appl. No. 13/536,603, Office Action dated May 4, 2016, 28 pages. |
U.S. Appl. No. 13/920,866, filed May 18, 2013, 44 pages. |
U.S. Appl. No. 14/052,763, Amendment and Response filed Jun. 10, 2016, 14 pages. |
U.S. Appl. No. 14/052,763, Office Action dated Dec. 10, 2015, 10 pages. |
U.S. Appl. No. 14/052,763, Office Action dated Sep. 8, 2016, 12 pages. |
U.S. Appl. No. 14/105,095, Amendment and Response filed May 19, 2015, 12 pages. |
U.S. Appl. No. 14/105,095, Amendment and Response filed Nov. 6, 2015, 12 pages. |
U.S. Appl. No. 14/105,095, Notice of Allowance dated Jul. 19, 2016, 8 pages. |
U.S. Appl. No. 14/105,095, Office Action dated Jul. 6, 2015, 14 pages. |
U.S. Appl. No. 14/105,095, Office Action dated Feb. 19, 2016, 18 pages. |
U.S. Appl. No. 14/217,643, Amendment and Response filed Mar. 7, 2016, 12 pages. |
U.S. Appl. No. 14/217,643, Amendment and Response filed Jul. 25, 2016, 14 pages. |
U.S. Appl. No. 14/217,643, Office Action dated Nov. 5, 2015, 10 pages. |
U.S. Appl. No. 14/217,643, Office Action dated Apr. 25, 2016, 11 pages. |
U.S. Appl. No. 14/498,846, Amendment and Response filed Apr. 25, 2016, 15 pages. |
U.S. Appl. No. 14/498,846, Office Action dated Jan. 15, 2016, 12 pages. |
U.S. Appl. No. 14/498,846, Office Action dated Aug. 10, 2016, 11 pages. |
U.S. Appl. No. 14/498,946, Notice of Allowance dated Sep. 30, 2016, 12 pages. |
U.S. Appl. No. 14/498,946, Office Action dated Sep. 22, 2016, 12 pages. |
Web Hosting Features, Published on: Jun. 24, 2011, Available at: http://smallbusiness.yahoo.com/webhostinq/features#.uni, 3 pages. |
Web Integration Services, Published on: Aug. 14, 2010, Available at: htto://www.deversus.com/services/web-intearation/, 3 pages. |
Word Press Development, Retrieved on Mar. 1, 2012, available at:http://www.intearatedweb.com.au/our-services/wordoress-develooment/, 3 pages. |
Zerkouk, et al., “A User Profile Based Access Control Model and Architecture”, In International Journal of Computer Networks & Communications, vol. 5, Issue 1, Jan. 2013, 11 pages. |
U.S. Appl. No. 14/217,643, Office Action dated Oct. 20, 2016, 12 pages. |
U.S. Appl. No. 14/105,095, Notice of Allowance dated Dec. 9, 2016, 7 pages. |
U.S. Appl. No. 14/105,095, Notice of Allowance dated Jan. 30, 2017, 2 pages. |
U.S. Appl. No. 14/217,643, Amendment and Response filed Mar. 20, 2017, 16 pages. |
U.S. Appl. No. 14/217,643, Office Action dated Jun. 13, 2017, 20 pages. |
Guy, Ido et al., “Social Media Recommendation based on People and Tags”, IBM, 1995, pp. 194-201. |
U.S. Appl. No. 15/365,153, Office Action dated Sep. 29, 2017, 13 pages. |
Mathew, et al., “Predicting Future Locations with Hidden Markov Models”, In Proceeding of the ACM International Joint Conference on Pervasive and Ubiquitous Computing, Sep. 5, 2012, 8 Pages. |
U.S. Appl. No. 14/217,643, Amendment and Response filed Nov. 13, 2017, 16 pages. |
U.S. Appl. No. 15/365,153, Amendment and Response filed Nov. 30, 2017, 15 pages. |
U.S. Appl. No. 15/365,153, Office Action dated Jan. 16, 2018, 12 pages. |
U.S. Appl. No. 14/217,643, Office Action dated Dec. 28, 2017, 17 pages. |
Number | Date | Country | |
---|---|---|---|
20170211945 A1 | Jul 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14105095 | Dec 2013 | US |
Child | 15482185 | US |