PATENT DOCUMENT

Publication Number: US-8332402-B2
Application Number: US-2020208-A
Country: US
Kind Code: B2

Title: Location based media items

Abstract:
Media items can be distributed to mobile devices based on the location of the media device. The media items can be associated with location information, which can be examined and distributed to those devices whose proximate area includes the location information associated with the media items.

Claims:
1. A method comprising:
 determining, at a mobile device, boundary information defining a geographic area depicted by a current map display associated with the mobile device; 
 communicating location information associated with the mobile device to a server, the location information including the boundary information; 
 receiving, at the mobile device, media item abstracts representing content comprising photos, videos, audio, routes, commercial content, or tours, the media item abstracts being associated with a location within the geographical area defined by the boundary information; 
 associating the received media item abstracts with two or more groups by category; 
 displaying two or more groups of the received media item abstracts on the current map display; 
 receiving, at the mobile device, input selecting one of the displayed groups of received media item abstracts; 
 determining that at least one item of content associated with the selected group of media item abstracts is not stored on the mobile device; 
 based on determining that the at least one item of content is not stored on the mobile device, requesting the at least one item of content from the server; 
 receiving, at the mobile device, the at least one item of content associated with the selected group of media item abstracts; and 
 providing access to content associated with the selected group of media item abstracts, including the at least one item of content, on the mobile device. 
 
     
     
       2. The method of  claim 1 , wherein the received content comprises images of locations associated with the geographical area within a proximate distance to the mobile device based on the location information. 
     
     
       3. The method of  claim 1 , wherein the received content comprises videos associated with the geographical area within a proximate distance to the mobile device based on the location information. 
     
     
       4. The method of  claim 1 , wherein the received content comprises routes associated with the geographical area within a proximate distance to the mobile device based on the location information. 
     
     
       5. The method of  claim 1 , wherein the received content comprises a multimedia tour presentation associated with the geographical area within a proximate distance to the mobile device based on the location information. 
     
     
       6. The method of  claim 1 , wherein the received content comprises music associated with the geographical area within a proximate distance to the mobile device based on the location information. 
     
     
       7. The method of  claim 1 , further comprising receiving location information from a positioning system. 
     
     
       8. The method of  claim 7 , wherein the positioning system derives location information from satellite data received from a plurality of satellites. 
     
     
       9. The method of  claim 7 , wherein the positioning system uses dead reckoning to derive location information associated with the user. 
     
     
       10. The method of  claim 7 , wherein the positioning system uses a wireless signal strength of a mobile device associated with the user to derive location information associated with the user. 
     
     
       11. The method of  claim 1 , further comprising presenting the received content in a multi-touch environment. 
     
     
       12. The method of  claim 1 , further comprising:
 receiving at the mobile device from a user a scale request; 
 determining a boundary information delta based on the scale request; and 
 retrieving only those media item abstracts associated with the boundary information delta. 
 
     
     
       13. The method of  claim 1 , further comprising:
 deriving new location information; 
 determining a boundary information delta based on the scale request; and 
 retrieving only those media item abstracts associated with the boundary information delta. 
 
     
     
       14. The method of  claim 1 , further comprising:
 transmitting preference data associated with the user of the mobile device to the server, and wherein the received media item abstracts are identified based on the transmitted preference data. 
 
     
     
       15. The method of  claim 1 , wherein determining that at least one item of content associated with the selected group of media item abstracts is not stored on the mobile device comprises:
 comparing the group of media item abstracts to media items currently stored on the mobile device; and 
 determining that the at least one of the group of media item abstracts does not have a corresponding media item stored on the mobile device. 
 
     
     
       16. A computer-implemented method comprising:
 receiving, from a mobile device, current location information associated with a current location of the mobile device, the current location information including boundary information determined at the mobile device, the boundary information defining a geographic area depicted by a current map display associated with the mobile device; 
 identifying a plurality of media item abstracts representing content comprising photos, videos, audio, routes, commercial content, or tours, the media item abstracts being associated with a location within the geographical area defined by the boundary information; 
 grouping the identified media item abstracts into two or more groups by category; 
 transmitting the grouped media item abstracts to the mobile device; 
 receiving, from the mobile device, information identifying content associated with one of the groups of transmitted media item abstracts that was selected by a user of the mobile device and that was determined to not be currently stored on the mobile device; and 
 transmitting, to the mobile device, the content associated with the selected group of media item abstracts that is not currently stored on the mobile device. 
 
     
     
       17. The method of  claim 16 , further comprising:
 retrieving one or more user preferences associated with a user of the mobile device; and 
 filtering the plurality of grouped media item abstracts based on the one or more user preferences and based upon the location within the geographical area defined by the boundary information, the media item abstracts representing content identified by user preferences and associated with the geographic area. 
 
     
     
       18. The method of  claim 16 , wherein the content comprises one or more of a music item, a video item, a multi-media tour presentation item, a picture item, or a route item. 
     
     
       19. The method of  claim 16 , wherein the content comprises traffic information. 
     
     
       20. The method of  claim 16 , further comprising:
 receiving user-defined content; and 
 adding media item abstracts representing the user-defined content to the plurality of media item abstracts. 
 
     
     
       21. The method of  claim 20 , wherein the user-defined content is received using a web interface. 
     
     
       22. The method of  claim 16 , further comprising:
 retrieving content from third party content providers; and 
 adding media item abstracts representing the retrieved content to the plurality of media item abstracts. 
 
     
     
       23. A system comprising:
 a processor; and 
 a computer-readable medium coupled to the processor and having instructions stored thereon, which, when executed by the processor, causes the processor to perform operations comprising:
 obtaining location information associated with a mobile device, the location information including boundary information defining a geographic area depicted by a current map display associated with the mobile device; 
 receiving and storing preferences associated with one or more categories of content comprising photos, videos, audio, routes, commercial content, or tours; 
 communicating the preferences and the location information associated with the mobile device to a server; 
 receiving media item abstracts from the server based on the preferences and the location information, wherein the media item abstracts represent content associated with a location within the geographical area defined by the boundary information; 
 associating the received media item abstracts with two or more groups by category; 
 overlaying the two or more groups of the received media item abstracts onto the map display; 
 receiving, at the mobile device, input selecting one of the overlaid groups of received media item abstracts; 
 determining that at least one item of content associated with the selected group of media item abstracts is not stored on the mobile device; 
 based on determining that the at least one item of content is not stored on the mobile device, requesting the at least one item of content from the server; 
 receiving, at the mobile device, the at least one item of content associated with the selected group of media item abstracts; and 
 providing access to content associated with the selected group of media item abstracts, including the at least one item of content, on the mobile device. 
 
 
     
     
       24. The system of  claim 23 , wherein the received content comprises one or more of video content, picture content, audio content, multimedia content or routing content associated with the geographical area within a proximate distance to the mobile device based on the location information. 
     
     
       25. The system of  claim 23 , wherein the received content comprises user contributed content associated with the geographical area within a proximate distance to the mobile device based on the location information. 
     
     
       26. The system of  claim 23 , wherein the received content comprises commercial content associated with the geographical area within a proximate distance to the user based on the location information. 
     
     
       27. The system of  claim 26 , wherein the operations further comprise:
 adjusting an account associated with the user based on receiving a request for commercial content; and 
 adjusting an account associated with a provider of the commercial content. 
 
     
     
       28. The system of  claim 23 , wherein the location information is derived from satellite data received from a plurality of satellites. 
     
     
       29. The system of  claim 23 , wherein the positioning system uses dead reckoning to derive location information associated with the user. 
     
     
       30. The system of  claim 23 , wherein the positioning system uses a wireless signal strength associated with the mobile device to derive location information associated with the mobile device. 
     
     
       31. A system comprising:
 a processor; and 
 a computer-readable medium coupled to the processor and having instructions stored thereon, which, when executed by the processor, causes the processor to perform operations comprising:
 receiving location information associated with a current location of a mobile device and user preferences associated with the user of the mobile device, the location information including boundary information defining a geographic area depicted by a current map display associated with the mobile device, the boundary information determined at the device; 
 identifying one or more media item abstracts representing content comprising photos, videos, audio, routes, commercial content, or tours, the media item abstracts being associated with a location within the geographical area defined by the boundary information, wherein the one or more media item abstracts are identified based on the one or more user preferences; 
 associating the received media item abstracts with two or more groups by category; 
 generating an overlay of the two or more groups of the received media item abstracts; 
 communicating the generated overlay to the mobile device for presentation on the map display associated with the mobile device; 
 receiving, from the mobile device, information identifying content associated with one of the overlaid groups of received media item abstracts that was selected by a user of the mobile device and that was determined to not be currently stored on the mobile device; and 
 transmitting, to the mobile device, the content associated with the selected group of media item abstracts that is not currently stored on the mobile device. 
 
 
     
     
       32. The system of  claim 31 , wherein the content comprises one or more of a music item, a video item, a multi-media tour presentation item, a picture item, or a route item. 
     
     
       33. The system of  claim 31 , wherein the content comprises one or more of user contributed content or commercial content. 
     
     
       34. The system of  claim 31 , wherein the content comprises traffic information associated with roads proximate to the location identified by the location information. 
     
     
       35. The system of  claim 31 , wherein the operations further comprise:
 adjusting an account associated with the user based on receiving a request for commercial content; and 
 adjusting an account associated with a provider of requested commercial content. 
 
     
     
       36. The system of  claim 31 , wherein the operations further comprise:
 storing the user preferences associated with the user of the mobile device. 
 
     
     
       37. The system of  claim 31 , wherein the location information comprises a route and the one or more media item abstracts are identified based upon being associated with a geographic location proximate to the route. 
     
     
       38. A method comprising:
 communicating route information associated with a mobile device to a server, the route information comprising an origin and a destination, the route information determined at the mobile device; 
 receiving at the mobile device media item abstracts from the server, the media item abstracts representing content comprising photos, videos, audio, routes, commercial content, or tours, the media item abstracts being associated with vicinity content related to the route information, the vicinity content comprising content associated with a geographical area proximate to a route associated with the route information; 
 associating the received media item abstracts with two or more groups by category; 
 presenting two or more groups of the received media item abstracts received at the mobile device on a map display; 
 receiving, at the mobile device, input selecting one of the displayed groups of media item abstracts; 
 determining that at least one item of content associated with the selected group of media item abstracts is not stored on the mobile device; 
 based on determining that the at least one item of content is not stored on the mobile device, requesting the at least one item of content from the server; 
 receiving, at the mobile device, the at least one item of content associated with the selected group of media item abstracts; and 
 presenting content associated with the selected group of media item abstracts, including the at least one item of content, on the mobile device. 
 
     
     
       39. The method of  claim 38 , further comprising:
 receiving the route associated with the route information from the server; and 
 presenting the route received at the mobile device on the map display, wherein presenting the media item abstracts comprises overlaying symbols associated with the content on a map associated with the route. 
 
     
     
       40. The method of  claim 38 , wherein the content comprises user contributed content, wherein the user contributed content is contributed by other users and associated with a location.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application claims priority to U.S. Provisional Patent Application Ser. No. 60/946,840 filed Jun. 28, 2007, and entitled “LOCATION BASED MEDIA ITEMS” the contents of which are incorporated herein by reference. 
    
    
     BACKGROUND 
     This disclosure relates to navigation using a mobile device. 
     Navigation systems provide little intelligence other than the ability to navigate from an origination point to a destination point. Often such navigation systems are implemented on hand-held devices, and a user may utilize such a system in unfamiliar surroundings, e.g., while walking through a city the user is visiting during a vacation. Because most navigation interfaces on the hand-held device typically provide only a map and/or directions to the user, the user may not experience interesting locations nearby; e.g., the user may walk past a historical location, unaware of the significance. 
     Some navigation systems can provide data related to locations nearby a user. However, the provisioning of such location data can result in a cluttered navigation interface, e.g., a user may have a navigation interface set to display several city blocks, but the interface may be cluttered by multiple alerts related to interesting locations outside the boundary displayed on the navigation interface. Furthermore, the location data that is received may be of little interest to the user, e.g., a user may be interested in historical locations, but may receive data related to non-historical locations that are not of immediate interest to the user. The provision of such data can result in a poor user experience. 
     SUMMARY 
     In one aspect, systems, methods, apparatuses and computer program products are provided. In one aspect, methods are disclosed, which include steps such as: communicating location information associated with a device to a server, the location information including boundary information defining a geographic area depicted by a current map display associated with the device; receiving at the device media items from the server, the media items comprising vicinity content associated with the location information, the vicinity content comprising content associated with the geographical area defined by the boundary information; and, presenting the media items received at the device to a user. 
     In another aspect, methods are disclosed, which include steps such as: receiving current location information associated with a current location of a mobile device, the current location information including boundary information defining a geographic area depicted by a current map display associated with the device; filtering a plurality of media items based on a geographic area defined by the boundary information identified by the location information, the media items comprising content associated with the geographic area defined by the boundary information; and, transmitting the media items to the mobile device for presentation. 
     Systems can include a positioning system, a preferences engine, a communications interface, and a user interface. The positioning system derives location information associated with an associated device, while the preferences engine can receive and store preferences associated with a user of the device. The communications interface can communicate preferences and location information associated with the device to a server. The communications interface can also receive media items including content based on the preferences and based on location information. The user interface can present the media items to a user associated with the device. 
     Other systems can include a communications interface and a location based media engine. The communications interface receives location information associated with a current location of a mobile device and to receive user preferences, while the location based media engine identifies media items based on user preferences and on a geographic area proximate to the mobile device, the media items including content associated with the geographic area and identified by the user preferences. The communications interface can then communicate the media items to the mobile device for presentation to a user associated with the mobile device. 
     Systems and methods as described can enhance the data provided by a mobile navigation system. Location based media items can provide multimedia tours for sightseers. Location based media can also provide route, photo and video sharing among users, and can provide media of local interest to users enhancing their understanding of local life and culture. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a block diagram of an example mobile device. 
         FIG. 2  is a block diagram of an example network operating environment for the mobile device of  FIG. 1 . 
         FIG. 3  is a block diagram of an example implementation of the mobile device of  FIG. 1 . 
         FIG. 4  is a block diagram illustrating an example media service including location based media items. 
         FIG. 5  is a block diagram of an example mobile device using a location based media service. 
         FIG. 6  is a block diagram of another example mobile device using a location based media service. 
         FIG. 7  is a flowchart illustrating an example method for retrieving location based media items. 
         FIG. 8  is a flowchart illustrating another example method for distributing location based media items. 
     
    
    
     DETAILED DESCRIPTION 
       FIG. 1  is a block diagram of an example mobile device  100 . The mobile device  100  can be, for example, a handheld computer, a personal digital assistant, a cellular telephone, a network appliance, a camera, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a network base station, a media player, a navigation device, an email device, a game console, or a combination of any two or more of these data processing devices or other data processing devices. 
     Mobile Device Overview 
     In some implementations, the mobile device  100  includes a touch-sensitive display  102 . The touch-sensitive display  102  can implement liquid crystal display (LCD) technology, light emitting polymer display (LPD) technology, or some other display technology. The touch-sensitive display  102  can be sensitive to haptic and/or tactile contact with a user. 
     In some implementations, the touch-sensitive display  102  can comprise a multi-touch-sensitive display  102 . A multi-touch-sensitive display  102  can, for example, process multiple simultaneous touch points, including processing data related to the pressure, degree and/or position of each touch point. Such processing facilitates gestures and interactions with multiple fingers, chording, and other interactions. Other touch-sensitive display technologies can also be used, e.g., a display in which contact is made using a stylus or other pointing device. Some examples of multi-touch-sensitive display technology are described in U.S. Pat. Nos. 6,323,846, 6,570,557, 6,677,932, and U.S. Patent Publication 2002/0015024A1, each of which is incorporated by reference herein in its entirety. 
     In some implementations, the mobile device  100  can display one or more graphical user interfaces on the touch-sensitive display  102  for providing the user access to various system objects and for conveying information to the user. In some implementations, the graphical user interface can include one or more display objects  104 ,  106 . In the example shown, the display objects  104 ,  106 , are graphic representations of system objects. Some examples of system objects include device functions, applications, windows, files, alerts, events, or other identifiable system objects. 
     Exemplary Mobile Device Functionality 
     In some implementations, the mobile device  100  can implement multiple device functionalities, such as a telephony device, as indicated by a phone object  110 ; an e-mail device, as indicated by the e-mail object  112 ; a network data communication device, as indicated by the Web object  114 ; a Wi-Fi base station device (not shown); and a media processing device, as indicated by the media player object  116 . In some implementations, particular display objects  104 , e.g., the phone object  110 , the e-mail object  112 , the Web object  114 , and the media player object  116 , can be displayed in a menu bar  118 . In some implementations, device functionalities can be accessed from a top-level graphical user interface, such as the graphical user interface illustrated in  FIG. 1 . Touching one of the objects  110 ,  112 ,  114  or  116  can, for example, invoke corresponding functionality. 
     In some implementations, the mobile device  100  can implement network distribution functionality. For example, the functionality can enable the user to take the mobile device  100  and its associated network while traveling. In particular, the mobile device  100  can extend Internet access (e.g., Wi-Fi) to other wireless devices in the vicinity. For example, mobile device  100  can be configured as a base station for one or more devices. As such, mobile device  100  can grant or deny network access to other wireless devices. 
     In some implementations, upon invocation of device functionality, the graphical user interface of the mobile device  100  changes, or is augmented or replaced with another user interface or user interface elements, to facilitate user access to particular functions associated with the corresponding device functionality. For example, in response to a user touching the phone object  110 , the graphical user interface of the touch-sensitive display  102  may present display objects related to various phone functions; likewise, touching of the email object  112  may cause the graphical user interface to present display objects related to various e-mail functions; touching the Web object  114  may cause the graphical user interface to present display objects related to various Web-surfing functions; and touching the media player object  116  may cause the graphical user interface to present display objects related to various media processing functions. 
     In some implementations, the top-level graphical user interface environment or state of  FIG. 1  can be restored by pressing a button  120  located near the bottom of the mobile device  100 . In some implementations, each corresponding device functionality may have corresponding “home” display objects displayed on the touch-sensitive display  102 , and the graphical user interface environment of  FIG. 1  can be restored by pressing the “home” display object. 
     In some implementations, the top-level graphical user interface can include additional display objects  106 , such as a short messaging service (SMS) object  130 , a calendar object  132 , a photos object  134 , a camera object  136 , a calculator object  138 , a stocks object  140 , a weather object  142 , a maps object  144 , a notes object  146 , a clock object  148 , an address book object  150 , and a settings object  152 . Touching the SMS display object  130  can, for example, invoke an SMS messaging environment and supporting functionality; likewise, each selection of a display object  132 ,  134 ,  136 ,  138 ,  140 ,  142 ,  144 ,  146 ,  148 ,  150  and  152  can invoke a corresponding object environment and functionality. 
     Additional and/or different display objects can also be displayed in the graphical user interface of  FIG. 1 . For example, if the device  100  is functioning as a base station for other devices, one or more “connection” objects may appear in the graphical user interface to indicate the connection. In some implementations, the display objects  106  can be configured by a user, e.g., a user may specify which display objects  106  are displayed, and/or may download additional applications or other software that provides other functionalities and corresponding display objects. 
     In some implementations, the mobile device  100  can include one or more input/output (I/O) devices and/or sensor devices. For example, a speaker  160  and a microphone  162  can be included to facilitate voice-enabled functionalities, such as phone and voice mail functions. In some implementations, a loud speaker  164  can be included to facilitate hands-free voice functionalities, such as speaker phone functions. An audio jack  166  can also be included for use of headphones and/or a microphone. 
     In some implementations, a proximity sensor  168  can be included to facilitate the detection of the user positioning the mobile device  100  proximate to the user&#39;s ear and, in response, to disengage the touch-sensitive display  102  to prevent accidental function invocations. In some implementations, the touch-sensitive display  102  can be turned off to conserve additional power when the mobile device  100  is proximate to the user&#39;s ear. 
     Other sensors can also be used. For example, in some implementations, an ambient light sensor  170  can be utilized to facilitate adjusting the brightness of the touch-sensitive display  102 . In some implementations, an accelerometer  172  can be utilized to detect movement of the mobile device  100 , as indicated by the directional arrow  174 . Accordingly, display objects and/or media can be presented according to a detected orientation, e.g., portrait or landscape. In some implementations, the mobile device  100  may include circuitry and sensors for supporting a location determining capability, such as that provided by the global positioning system (GPS) or other positioning systems (e.g., systems using Wi-Fi access points, television signals, cellular grids, Uniform Resource Locators (URLs)). In some implementations, a positioning system (e.g., a GPS receiver) can be integrated into the mobile device  100  or provided as a separate device that can be coupled to the mobile device  100  through an interface (e.g., port device  190 ) to provide access to location-based services. 
     The mobile device  100  can also include a camera lens and sensor  180 . In some implementations, the camera lens and sensor  180  can be located on the back surface of the mobile device  100 . The camera can capture still images and/or video. 
     The mobile device  100  can also include one or more wireless communication subsystems, such as a 802.11b/g communication device  186 , and/or a Bluetooth™ communication device  188 . Other communication protocols can also be supported, including other 802.x communication protocols (e.g., WiMax, Wi-Fi, 3G), code division multiple access (CDMA), global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), etc. 
     In some implementations, a port device  190 , e.g., a Universal Serial Bus (USB) port, or a docking port, or some other wired port connection, can be included. The port device  190  can, for example, be utilized to establish a wired connection to other computing devices, such as other communication devices  100 , network access devices, a personal computer, a printer, or other processing devices capable of receiving and/or transmitting data. In some implementations, the port device  190  allows the mobile device  100  to synchronize with a host device using one or more protocols, such as, for example, the TCP/IP, HTTP, UDP and any other known protocol. In some implementations, a TCP/IP over USB protocol can be used. 
     Network Operating Environment 
       FIG. 2  is a block diagram of an example network operating environment  200  for the mobile device  100  of  FIG. 1 . The mobile device  100  of  FIG. 1  can, for example, communicate over one or more wired and/or wireless networks  210  in data communication. For example, a wireless network  212 , e.g., a cellular network, can communicate with a wide area network (WAN)  214 , such as the Internet, by use of a gateway  216 . Likewise, an access point device  218 , such as an 802.11g wireless access point device, can provide communication access to the wide area network  214 . In some implementations, both voice and data communications can be established over the wireless network  212  and the access point device  218 . For example, the mobile device  100   a  can place and receive phone calls (e.g., using VoIP protocols), send and receive e-mail messages (e.g., using POP3 protocol), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over the wireless network  212 , gateway  216 , and wide area network  214  (e.g., using TCP/IP or UDP protocols). Likewise, the mobile device  100   b  can place and receive phone calls, send and receive e-mail messages, and retrieve electronic documents over the access point device  218  and the wide area network  214 . In some implementations, the mobile device  100  can be physically connected to the access point device  218  using one or more cables and the access point device  218  can be a personal computer. In this configuration, the mobile device  100  can be referred to as a “tethered” device. 
     The mobile devices  100   a  and  100   b  can also establish communications by other means. For example, the wireless device  100   a  can communicate with other wireless devices, e.g., other wireless devices  100 , cell phones, etc., over the wireless network  212 . Likewise, the mobile devices  100   a  and  100   b  can establish peer-to-peer communications  220 , e.g., a personal area network, by use of one or more communication subsystems, such as the Bluetooth™ communication device  188  shown in  FIG. 1 . Other communication protocols and topologies can also be implemented. 
     The mobile device  100  can, for example, communicate with one or more services  230 ,  240 ,  250 , and  260  and/or one or more content publishers  270  over the one or more wired and/or wireless networks  210 . For example, a navigation service  230  can provide navigation information, e.g., map information, location information, route information, and other information, to the mobile device  100 . In the example shown, a user of the mobile device  100   b  has invoked a map functionality, e.g., by pressing the maps object  144  on the top-level graphical user interface shown in  FIG. 1 , and has requested and received a map for the location “1 Infinite Loop, Cupertino, Calif.” 
     A messaging service  240  can, for example, provide e-mail and/or other messaging services. A media service  250  can, for example, provide access to media files, such as song files, movie files, video clips, and other media data. One or more other services  260  can also be utilized by the mobile device  100 . 
     The mobile device  100  can also access other data and content over the one or more wired and/or wireless networks  210 . For example, content publishers  270 , such as news sites, RSS feeds, web sites, blogs, social networking sites, developer networks, etc., can be accessed by the mobile device  100 . Such access can be provided by invocation of a web browsing function or application (e.g., a browser) in response to a user touching the Web object  114 . 
     Exemplary Mobile Device Architecture 
       FIG. 3  is a block diagram  300  of an example implementation of the mobile device  100  of  FIG. 1 . The mobile device  100  can include a memory interface  302 , one or more data processors, image processors and/or central processing units  304 , and a peripherals interface  306 . The memory interface  302 , the one or more processors  304  and/or the peripherals interface  306  can be separate components or can be integrated in one or more integrated circuits. The various components in the mobile device  100  can be coupled by one or more communication buses or signal lines. 
     Sensors, devices and subsystems can be coupled to the peripherals interface  306  to facilitate multiple functionalities. For example, a motion sensor  310 , a light sensor  312 , and a proximity sensor  314  can be coupled to the peripherals interface  306  to facilitate the orientation, lighting and proximity functions described with respect to  FIG. 1 . Other sensors  316  can also be connected to the peripherals interface  306 , such as a positioning system (e.g., GPS receiver), a temperature sensor, a biometric sensor, or other sensing device, to facilitate related functionalities. 
     In some implementations, the mobile device can receive positioning information from a positioning system  318 . The positioning system  318 , in various implementations, can be located on the mobile device, or can be coupled to the mobile device (e.g., using a wired connection or a wireless connection). In some implementations, the positioning system  318  can include a global positioning system (GPS) receiver and a positioning engine operable to derive positioning information from received GPS satellite signals. In other implementations, the positioning system  318  can include a compass and an accelerometer, as well as a positioning engine operable to derive positioning information based on dead reckoning techniques. In still further implementations, the positioning system  318  can use wireless signals (e.g., cellular signals, IEEE 802.11 signals, etc) to determine location information associated with the mobile device, such as those provided by Skyhook Wireless, Inc. of Boston, Mass. Hybrid positioning systems using a combination of satellite and television signals, such as those provided by Rosum Corporation of Mountain View, Calif., can also be used. Other positioning systems are possible. 
     A camera subsystem  320  and an optical sensor  322 , e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips. 
     Communication functions can be facilitated through one or more wireless communication subsystems  324 , which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem  324  can depend on the communication network(s) over which the mobile device  100  is intended to operate. For example, a mobile device  100  may include communication subsystems  324  designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a Bluetooth™ network. In particular, the wireless communication subsystems  324  may include hosting protocols such that the device  100  may be configured as a base station for other wireless devices. 
     An audio subsystem  326  can be coupled to a speaker  328  and a microphone  330  to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions. 
     The I/O subsystem  340  can include a touch screen controller  342  and/or other input controller(s)  344 . The touch-screen controller  342  can be coupled to a touch screen  346 . The touch screen  346  and touch screen controller  342  can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen  346 . 
     The other input controller(s)  344  can be coupled to other input/control devices  348 , such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of the speaker  328  and/or the microphone  330 . 
     In one implementation, a pressing of the button for a first duration may disengage a lock of the touch screen  346 ; and a pressing of the button for a second duration that is longer than the first duration may turn power to the mobile device  100  on or off. The user may be able to customize a functionality of one or more of the buttons. The touch screen  346  can, for example, also be used to implement virtual or soft buttons and/or a keyboard. 
     In some embodiments, the mobile device  100  can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, the mobile device  100  can include the functionality of an MP3 player, such as an iPod™. The mobile device  100  may, therefore, include a 36-pin connector that is compatible with the iPod. Other input/output and control devices can also be used. 
     The memory interface  302  can be coupled to memory  350 . The memory  350  can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). The memory  350  can store an operating system  352 , such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks. The operating system  352  may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, the operating system  352  can be a kernel (e.g., UNIX kernel). 
     The memory  350  may also store communication instructions  354  to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. The memory  350  may include graphical user interface instructions  356  to facilitate graphic user interface processing; sensor processing instructions  358  to facilitate sensor-related processing and functions; phone instructions  360  to facilitate phone-related processes and functions; electronic messaging instructions  362  to facilitate electronic-messaging related processes and functions; web browsing instructions  364  to facilitate web browsing-related processes and functions; media processing instructions  366  to facilitate media processing-related processes and functions; GPS/Navigation instructions  368  to facilitate GPS and navigation-related processes and instructions; camera instructions  370  to facilitate camera-related processes and functions; and/or other software instructions  372  to facilitate other processes and functions. 
     The memory  350  can also include a preferences engine  374 . The preferences engine  374  can be operable to receive user preferences as to the sorts of media items the user is interested. In some implementations, the preferences can be used to filter the sorts of information that is sent to the mobile device  100 . For example, the user might indicate a preference for local music. Thus, when local music is available the mobile device  100  can retrieve available local music. In another example, the user might indicate a preference not to receive video, route or image content when in a specified area (e.g., hometown, familiar city, etc.), but to receive route and image content when outside of their specified area. These preferences can be communicated to a media service (e.g., media service  250  of  FIG. 2 ), and can be used by the media service to provide relevant media content based on location and/or preferences. 
     Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures or modules. The memory  350  can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device  100  may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits. 
       FIG. 4  is a block diagram illustrating an example media service  250 . In some implementations, the media service can include a communications interface  400  and a location based media engine  410 . In an implementation, the communications interface  400  can receive position information from a mobile device  100 . 
     Upon receiving position information from the communications interface, the location based media engine  410  can retrieve candidate media items associated with the position information received from the mobile device  100 . These candidate media items can be retrieved from a media item store  420 . In some implementations, the media items can be retrieved based upon tagging information associated with the media items. The tagging information can identify a location associated with the media items, and determine whether the tagging information defines a location within a proximate area  430  to the mobile device. For example, media items  450   a - 450   h  might be available on the media items store  420 . Media items  450   c - 450   h  are associated with locations outside of the proximate area  430  to the mobile device  100 . Thus, these media items  450   c - 450   h  are not served to the mobile device  100 . However, media items  450   a ,  450   b  are associated with locations inside of the proximate area  430 . Thus, these media items  450   a ,  450   b  are served to the mobile device  100 . 
     Although a circular proximate area  430  is shown, other proximate areas can also be defined. In some implementations, the proximate area  430  can correspond to a current display boundary displayed on the mobile device  100 . In other implementations, the proximate area  430  can be user defined. 
     In other implementations, the device  100  can retrieve a list of media items associated with the proximate area  430  from the media service  250 . The device  100  can then compare the list of media items with media items already present on the device. For example, the device may be located at the Statue of Liberty, and other users may have associated certain patriotic songs, including “Stars and Stripes Forever” with the location. The device can review its local storage for the song before downloading the song from the server. In another example, the map can display a location associated with a calendar appointment from one or more calendars stored locally or remotely and associated with one or more users of the device. 
     In further implementations, the media service  250  might send particular genre or local character/sights information to the device. The device can then use the genre or local character/sights information to identify whether the device includes any locally stored media items which correspond to the genre or local character/sights information. For example, the device can store pictures. The pictures might be tagged with a location, genre or characteristic associated with the subject of the picture. So, if the user were standing at the Statue of Liberty, the device can receive genre, character, sights information that might include keywords like “Statue of Liberty,” “New York City,” etc. The device could then search the local date store to identify local media items associated with the keywords, such as an old picture of the Statue of Liberty taken during a previous trip to New York City. In other implementations, the device might include the ability to compare locally stored photos with a characteristic photo associated with a location to determine whether the local device includes any locally stored media items associated with the current location. 
     In various implementations, the user can cause the mobile device  100  to enter a state in which the mobile device  100  alerts the media service  250  that the user would like to receive local media content, or notification of available local media content (e.g., such as when the user is sightseeing, hiking, on vacation, etc.). The user can also cause the mobile device  100  to enter a state in which the mobile device  100  alerts the media service  250  that the user does not want to receive local media content, or notification of available local media content (e.g., such as when the user is driving to/from work, in the grocery store, etc.). 
     In some implementations, the media content  450   a - h  can be supplied by other users. For example, a user might be standing at the Washington Monument taking a picture of the monument and decide that they would like to share the picture with other users. The picture can be automatically tagged with the location information and uploaded to the media service  250  for storage in the media item store  250 . Similarly, a local band that often performs at a venue location might decide to make their music available to users that are within the proximate area  430  of the venue location and upload their songs to the media service  250 . 
     In other implementations, the media content  450   a - h  can be commercial content supplied by vendors (e.g., content providers). In such implementations, the media service  250  can include a payment engine operable to collect payment from users and distribute payment to vendors. For example, a tour company might decide to make audio walking tours available for sale to users by uploading tour data to the media service  250 . The user can be alerted to the price of the tour, and the mobile device  100  can provide account information, which can be used by the payment engine to collect payment from the user. For example, a user walking through downtown Boston may be alerted that an audio walking tour starting at a location within the proximate area  430  is available for $0.99. If the user decides to purchase the tour, an account associated with the user can be charged a $0.99 fee. 
     In some implementations, the media content  450   a - h  can be overlaid onto a map provided by a navigation service (e.g., navigation service  230 ), such as shown in  FIG. 5 . Such overlay can provide notification to the user of available media items. The location of media items can be marked by pushpin, for example. Thus, as the user is navigating using the navigation service, the user can be notified when a media item is available in a proximate area. In some implementations, the notification can provide an indication of what sorts of media items are available (e.g., photos, videos, music, routes, multimedia tours, etc.), whether the media items are user contributed or commercial, and/or how many media items are available, among others. 
     In some implementations, media content  450  can be provided based on a user preference. For example, a user may set a preference on the mobile device  100  to indicate the user is interested in historical subjects. Accordingly, the mobile device  100  might only display media content  450  that relates only to historical subjects, e.g., the media content  450   a  may be displayed if it relates to a historical monument, while the media item  450   b  might not be displayed if it relates to another user&#39;s review of a nearby restaurant. Subject matter relations can, for example, be stored in the media item store  420 . 
     In further implementations, the media service  250  can include a preference engine  440  operable to store user preferences in a user preference store  445 . Preferences can be stored such that when a user requests media, the media service  250  provides the user with media that is relevant to the user&#39;s interests. Thus, in some implementations, the mobile device sends preference information only when there is a change to existing preference information, and the media service  250  stores the preference information for any subsequent communication of media items. 
       FIG. 5  is a block diagram of an example mobile device using a location based media service. The mobile device  100  can receive a map representation  500  from a navigation service (e.g., navigation service  230  of  FIG. 2 ). The media service  250  can cause a pushpin representation  510  to be overlaid onto the map representation  500  by the mobile device  100 . The pushpin representation  510  can be used to notify the user that local media is available. In some implementations, a proximate area (e.g., proximate area  430  of  FIG. 4 ) can be adjusted based on the zoom level associated with the map representation  500  currently displayed to the user. For example, the proximate area  430  may be defined by the display boundary of the map representation  500 . 
       FIG. 6  is a block diagram of another example mobile device  100  using a location based media service. The mobile device  100 , upon selection of a pushpin, for example, can cause available media item abstracts (e.g., icons) to be presented to the user. In some implementations, the media item abstracts can be grouped by category. For example, photo item abstracts  605   a - c , music item abstracts  610   a - d , video item abstracts  620   a - c , tours  625   a , and routes  630   a - d  can be respectively grouped together. In some implementations, a user can select from among the media item abstracts by touching a desired media item abstract. The mobile device  100  can then retrieve the content associated with the media item abstract from a media service (e.g., media service  250 ) and display the content of the media item to the user. 
     Other presentations of the media item abstracts can also be used. For example, the abstracts can be grouped by subject matter, e.g., history, entertainment, dining, etc., or can be grouped by date, e.g., added today, added within the last week, etc.; or can be grouped by users or entities, etc. 
       FIG. 7  is a flowchart illustrating an example method for retrieving location based media items. At stage  700 , location information is communicated. The location information can be communicated, for example, by a mobile device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with a positioning system (e.g., positioning system  318  of  FIG. 3 ) and communication instructions (e.g., communication instructions  354  of  FIG. 3 ) operating in conjunction with a wireless communication system (e.g., wireless communication subsystem  324  of  FIG. 3 ). The location information can be communicated to a server (e.g., media services  250  of  FIG. 2 ), for use in locating location based media items. The location information can include boundary information associated with the mobile device. The boundary information can define a geographic area depicted by a current map display associated with the mobile device. The location based media items can be filtered, for example, based on the location information associated with the location information. 
     At optional stage  710 , user preferences can be communicated. The user preferences can be communicated, for example, by a mobile device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with a preferences engine (e.g., preferences engine  374  of  FIG. 3 ) operating in conjunction with a wireless communication system (e.g., wireless communication subsystem  324  of  FIG. 3 ). In some implementations, the preference information can include information such as what types of media a user associated with the mobile device is interested in receiving. Thus, the user can set up the mobile device to receive only certain kinds of media content. 
     At stage  720 , media items are received. Media items can be received, for example, by the mobile device (e.g., mobile device  100 ) operating in conjunction with communication instructions (e.g., communication instructions  354  of  FIG. 3 ) and the wireless communication subsystem (e.g., wireless communication subsystem  324  of  FIG. 3 ). In some implementations, the media items can be those media items which are associated with an area proximate to the mobile device. In additional implementations, the mobile device can further filter the media items based on preferences of a user associated with the mobile device. 
     At stage  730 , the media items are presented. The media items can be presented, for example, by the mobile device (e.g., mobile device  100 ) operating in conjunction with graphical user interface instructions (e.g., GUI instructions  356  of  FIG. 3 ) along with a touch screen (e.g., touch screen  346  of  FIG. 3 ) and/or an audio subsystem (e.g., audio subsystem  326  of  FIG. 3 ). The presentation of the media items can be based upon user input received using the touch screen user interface. For example, a user might be prompted by the mobile device whether to present the media item(s). 
     In some implementations, the method can restart when the user selects to change the scale of the map or is moving such that the map window changes. For example, if a user instructs the mobile device to zoom out, the media items provided to the user based on the original boundaries will not include any media items added by the new zoom level. In some implementations, a mobile device can transmit a boundary delta to a media service. The media service can then identify only those additional media items which are implicated by the change in scale or movement of the map window. 
       FIG. 8  is a flowchart illustrating another example method for distributing location based media items. At stage  800 , location information is received. The location information can be received, for example, by a communications interface (e.g., communications interface  400  of  FIG. 4 ). In some implementations, the location information can include an exact location of a mobile device (e.g., mobile device  100  of  FIG. 1 ). In other implementations, the location information can include an approximate location of the mobile device. In still further implementations, the location information can include information about a currently viewed section of map. Other scales associated with location information are possible. 
     At optional stage  810 , user preferences can be received. The user preferences can be received, for example, by a communications interface (e.g., communications interface  400  of  FIG. 4 ). In some implementations, the preference information is associated with a user of a mobile device, and includes information such as what types of media a user associated with a mobile device is interested in receiving. 
     At stage  820 , the available media items are filtered based on the received location information. The available media items can be filtered, for example, using a location based media engine (e.g., location based media engine  410  of  FIG. 4 ) in conjunction with a media item store (e.g., media item store  420  of  FIG. 4 ). The media items stored in the media items store can include location tagging information, associating the media items with a location. If the location is within a proximate area to the location information associated with the mobile device, the media items are made available to the mobile device. The media items can include both commercial and non-commercial content. In some implementations, the non-commercial content can include content provided by users (e.g., peer contributed content). 
     In some implementations, the available media items can also be filtered based on preference information. For example, a user might indicate a preference to only receive media items during specified times, at specified locations, during route guidance, etc. A user might further indicate preferences based on the type of content available. For example, a user might only be interested in video content associated with current location information. 
     At stage  830 , the filtered media items are transmitted. The filtered media items can be transmitted, for example, by a communications interface (e.g., communications interface  400 ). In various implementations, the transmission can be wireless or wire based. The transmission of the media items, in some implementations, includes only transmission of abstract information associated with the media items (e.g., icons) to improve performance. Thus, the content associated with the media item might only be downloaded when the user requests the content. In other implementations, the entire content of each of the media items is transferred to the mobile device, and the mobile device provides the user with an interface to navigate the media items. 
     The systems and methods disclosed herein may use data signals conveyed using networks (e.g., local area network, wide area network, internet, etc.), fiber optic medium, carrier waves, wireless networks (e.g., wireless local area networks, wireless metropolitan area networks, cellular networks, etc.), etc. for communication with one or more data processing devices (e.g., mobile devices). The data signals can carry any or all of the data disclosed herein that is provided to or from a device. 
     The methods and systems described herein may be implemented on many different types of processing devices by program code comprising program instructions that are executable by one or more processors. The software program instructions may include source code, object code, machine code, or any other stored data that is operable to cause a processing system to perform methods described herein. 
     The systems and methods may be provided on many different types of computer-readable media including computer storage mechanisms (e.g., CD-ROM, diskette, RAM, flash memory, computer&#39;s hard drive, etc.) that contain instructions for use in execution by a processor to perform the methods&#39; operations and implement the systems described herein. 
     The computer components, software modules, functions and data structures described herein may be connected directly or indirectly to each other in order to allow the flow of data needed for their operations. It is also noted that software instructions or a module can be implemented for example as a subroutine unit of code, or as a software function unit of code, or as an object (as in an object-oriented paradigm), or as an applet, or in a computer script language, or as another type of computer code or firmware. The software components and/or functionality may be located on a single device or distributed across multiple devices depending upon the situation at hand. 
     This written description sets forth the best mode of the invention and provides examples to describe the invention and to enable a person of ordinary skill in the art to make and use the invention. This written description does not limit the invention to the precise terms set forth. Thus, while the invention has been described in detail with reference to the examples set forth above, those of ordinary skill in the art may effect alterations, modifications and variations to the examples without departing from the scope of the invention. 
     These and other implementations are within the scope of the following claims.

Metadata:
Filing Date: 20080125
Publication Date: 20121211
Grant Date: 20121211
Priority Date: 20070628
Inventors: FORSTALL SCOTT
CHRISTIE GREGORY N.
BORCHERS ROBERT E.
TIENE KEVIN
Assignee: APPLE INC
CPC Classifications: [{"code": "G06F16/9535", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F16/9535", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06Q30/00", "inventive": true, "first": true, "tree": "[]"}, {"code": "G06Q30/00", "inventive": true, "first": true, "tree": "[]"}]
Family ID: 40161817