PATENT DOCUMENT

Publication Number: US-10854008-B2
Application Number: US-201916240655-A
Country: US
Kind Code: B2

Title: Synchronized, interactive augmented reality displays for multifunction devices

Abstract:
A device can receive live video of a real-world, physical environment on a touch sensitive surface. One or more objects can be identified in the live video. An information layer can be generated related to the objects. In some implementations, the information layer can include annotations made by a user through the touch sensitive surface. The information layer and live video can be combined in a display of the device. Data can be received from one or more onboard sensors indicating that the device is in motion. The sensor data can be used to synchronize the live video and the information layer as the perspective of video camera view changes due to the motion. The live video and information layer can be shared with other devices over a communication link.

Claims:
What is claimed is: 
     
       1. A system, comprising:
 one or more sensors; 
 a camera; 
 one or more processors; and 
 a memory storing instructions that, when executed by the one or more processors, cause the one or more processors to:
 generate computer-generated imagery based on video captured from the camera; 
 determine a current location based on sensor data from the one or more sensors; 
 establish a communication link with another device; 
 send, to the other device via the communication link, the video, the computer-generated imagery and information indicating the current location, and 
 in response to receiving, from the other device, an indication of a location of the other device, update the computer-generated imagery to indicate the location of the other device. 
 
 
     
     
       2. The system of  claim 1 , further comprising:
 a display configured to display the video and the computer-generated imagery, wherein the computer-generated imagery includes an indication of the current location. 
 
     
     
       3. The system of  claim 1 , wherein the memory further comprises instructions that further cause the one or more processors to:
 in response to receiving user input indicating one or more annotations, generate additional computer-generated imagery based on the one or more annotations. 
 
     
     
       4. The system of  claim 1 , wherein the memory further comprises instructions that further cause the one or more processors to:
 determine a route between the current location and the location of the other device; and 
 overlay a representation of the route on the computer-generated imagery. 
 
     
     
       5. The system of  claim 1 , wherein the memory further comprises instructions that further cause the one or more processors to:
 receive an indication that motion is detected by the one or more sensors according to updated sensor data; and 
 update the computer-generated imagery according to the updated sensor data. 
 
     
     
       6. The system of  claim 5 , wherein the memory further comprises instructions that further cause the one or more processors to:
 send the updated computer-generated imagery to the other device via the communication link. 
 
     
     
       7. The system of  claim 1 , wherein the memory further comprises instructions that further cause the one or more processors to:
 identify an object in the video; 
 generate an information layer including information about the object; and 
 overlay the information layer onto the computer-generated imagery. 
 
     
     
       8. A method, comprising:
 generating computer-generated imagery based on video captured from a camera of a device; 
 determining a current location of the device based on sensor data from one or more sensors of the device; 
 establishing a communication link with another device; 
 sending, from the device to the other device via the communication link, the video, the computer-generated imagery and information indicating the current location, and 
 receiving, from the other device, an indication of a location of the other device, wherein the computer-generated imagery indicates the location of the other device. 
 
     
     
       9. The method of  claim 8 , further comprising:
 receiving user input indicating one or more annotations; and 
 generating additional computer-generated imagery based on the one or more annotations. 
 
     
     
       10. The method of  claim 8 , further comprising:
 determining a route between the current location and the location of the other device; and 
 overlaying a representation of the route on the computer-generated imagery. 
 
     
     
       11. The method of  claim 8 , further comprising:
 receiving an indication that motion is detected by the one or more sensors according to updated sensor data; and 
 updating the computer-generated imagery according to the updated sensor data. 
 
     
     
       12. The method of  claim 11 , further comprising:
 sending the updated computer-generated imagery to the other device via the communication link. 
 
     
     
       13. The method of  claim 8 , further comprising:
 identifying an object in the video; 
 generating an information layer including information about the object; and 
 overlaying the information layer onto the computer-generated imagery. 
 
     
     
       14. One or more non-transitory, computer-readable storage media storing instructions that, when executed on or across one or more processors, cause the one or more processors to:
 generate computer-generated imagery based on video captured from a camera; 
 determine a current location based on sensor data from the one or more sensors; 
 establish a communication link with another device; 
 send, to the other device via the communication link, the video, the computer-generated imagery and information indicating the current location, and 
 receive, from the other device, an indication of a location of the other device, wherein the computer-generated imagery indicates the location of the other device. 
 
     
     
       15. The one or more non-transitory, computer-readable storage media of  claim 14 , further comprising instructions that cause the one or more processors to:
 display, via a display device, the video and the computer-generated imagery, wherein the computer-generated imagery includes an indication of the current location. 
 
     
     
       16. The one or more non-transitory, computer-readable storage media of  claim 14 , further comprising instructions that cause the one or more processors to:
 in response to receiving user input indicating one or more annotations, generate additional computer-generated imagery based on the one or more annotations. 
 
     
     
       17. The one or more non-transitory, computer-readable storage media of  claim 14 , further comprising instructions that cause the one or more processors to:
 determine a route between the current location and the location of the other device; and 
 overlay a representation of the route on the computer-generated imagery. 
 
     
     
       18. The one or more non-transitory, computer-readable storage media of  claim 14 , further comprising instructions that cause the one or more processors to:
 receive an indication that motion is detected by the one or more sensors according to updated sensor data; and 
 update the computer-generated imagery according to the updated sensor data. 
 
     
     
       19. The one or more non-transitory, computer-readable storage media of  claim 18 , further comprising instructions that cause the one or more processors to:
 send the updated computer-generated imagery to the other device via the communication link. 
 
     
     
       20. The one or more non-transitory, computer-readable storage media of  claim 14 , further comprising instructions that cause the one or more processors to:
 identify an object in the video; 
 generate an information layer including information about the object; and 
 overlay the information layer onto the computer-generated imagery.

Description:
This application is a continuation of U.S. patent application Ser. No. 15/081,145, filed on Mar. 25, 2016, which is a continuation of U.S. patent application Ser. No. 14/146,419, filed Jan. 2, 2014, now U.S. Pat. No. 9,305,402, which is a continuation of U.S. patent application Ser. No. 13/768,072, filed on Feb. 15, 2013, now U.S. Pat. No. 8,625,018, which is a continuation of U.S. Ser. No. 12/652,725, filed Jan. 5, 2010, and now U.S. Pat. No. 8,400,548, which are hereby incorporated by reference herein in their entirety. 
    
    
     TECHNICAL FIELD 
     This is related generally to augmented reality applications on multifunction devices. 
     BACKGROUND 
     Augmented Reality (AR) technology combines a live view of a real-world, physical environment with computer-generated imagery. Information about the real world environment can be stored and retrieved as an information layer which can be overlaid on the live view and interacted with by a user. Despite strong academic and commercial interest in AR systems, many existing AR systems are complex and expensive making such systems unsuitable for general use by the average consumer. 
     SUMMARY 
     A device can receive images and/or live video of a real-world, physical environment on a touch sensitive surface. One or more objects can be identified in the live video. One or more information layers can be generated related to the objects. In some implementations, an information layer can include annotations made by a user through the touch sensitive surface. The information layer and live video can be combined in a display of the device. Data can be received from one or more onboard sensors indicating that the device is in motion. The sensor data can be used to synchronize the live video and the information layer as the perspective of video camera view changes due to the motion. The live video and information layer can be shared with other devices over a communication link. 
     In one embodiment, a device can provide a split screen display that can include a first display area for displaying the live video combined with the information layer and a second display area for displaying computer-generated imagery representing objects in the live video. The computer-generated imagery can be combined with the information layer in the second display area. A navigation control for allowing the user to navigate the computer-generated imagery can be provided with the split screen display. Alternatively, the user can navigate the computer-generated imagery by physically moving the device. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1A  illustrates an exemplary device for receiving live video of a real-world, physical environment. 
         FIG. 1B  illustrates the exemplary device of  FIG. 1A  displaying the live video combined with an information layer. 
         FIG. 1C  illustrates the exemplary device of  FIG. 1B  displaying a three-dimensional (3D) perspective view of the live video combined with the information layer. 
         FIG. 1D  illustrates an exemplary method of synchronizing live video displays on first and second devices and sharing changes to the information layer. 
         FIG. 2A  illustrates an exemplary device having a split screen display with computer-generated imagery. 
         FIG. 2B  illustrates synchronizing split screen displays of exemplary first and second devices. 
         FIG. 3  is a flow diagram of an exemplary process for synchronizing interactive AR displays. 
         FIG. 4  is a block diagram of exemplary device architecture for implementing synchronized, interactive AR displays. 
         FIG. 5  is a block diagram of an exemplary network operating environment for devices implementing synchronized, interactive AR displays. 
     
    
    
     DETAILED DESCRIPTION 
     AR Display Overview 
       FIG. 1A  illustrates example device  100  for receiving live video of a real-world, physical environment. Device  100  can be any device capable of supporting AR displays, including but not limited to personal computers, mobile phones, electronic tablets, game consoles, media players, etc. In some implementations, device  100  can be an electronic tablet having a touch sensitive surface  102 . In one embodiment, device  100  can include a video camera on a back surface (not shown). Other device configurations are possible including devices having video cameras on one or more surfaces. 
     In the example shown, the user is holding device  100  over a circuit board. A live video  104  of the circuit board is shown on surface  102 . Various objects are shown in live video  104 . For example, the circuit board shown includes processor chip  106 , capacitor  108 , memory cards  110  and other components. The circuit board also includes bar code  112  and markers  114   a ,  114   b . Virtual button  115  can be used to capture one or more frames of live video. 
     Example Information Layer 
       FIG. 1B  illustrates example device  100  of  FIG. 1A  displaying live video  104  combined with an information layer. Components  106 ,  110  and  108  can be been outlined (e.g., with dashed or colored lines), highlighted or otherwise annotated by the information layer (hereafter referred to collectively as “annotations”). For example, memory cards  110  are shown outlined with dashed line  130  and processor  106  and capacitor  108  are shown with thick outlines. Generally, any visual attribute that can set off an object from other objects in live video  104  can be an annotation. 
     Annotations can include text, images or references to other information (e.g., links). The annotations can be displayed proximate to their corresponding objects in live video  104 . Annotations can describe or otherwise provide useful information about the objects to a user (e.g., a computer technician). In the example shown, balloon call out  120  identifies memory cards  110 , balloon callout  122  identifies capacitor  108 , balloon callout  126  identifies processor  106  and balloon call out  128  identifies the circuit board. Additional related information, such as the manufacturer and part number can be included in the balloon callouts. Information layer can display annotations automatically or in response to trigger events. For example, the balloon call outs may only appear in live video  104  when the user is touching the corresponding annotated component. 
     Before an information layer can be generated, the objects to be annotated can be identified. The identification of objects in live video  104  can occur manually or automatically. If automatically, a frame of live video  104  can be “snapped” (e.g., by pressing button  115 ) and processed using known object recognition techniques, including but not limited to: edge detection, Scale-invariant Feature Transform (SIFT), template matching, gradient histograms, intraclass transfer learning, explicit and implicit 3D object models, global scene representations, shading, reflectance, texture, grammars, topic models, window-based detection, 3D cues, context, leveraging Internet data, unsupervised learning and fast indexing. The object recognition can be performed on device  100  or by a network resource (e.g., AR service  570  of  FIG. 5 ). 
     To assist in identification, barcode  112  can be identified by an image processor and used to retrieve a predefined information layer. To assist in overlaying the information layer onto live video  104 , and to align the annotations to the correct components, the image processor can identify marker  114   a  as indicating the top left corner of the circuit board. One or more markers can be used for an object. A location of a given annotation (e.g., dashed line  130 ) in live video  104  can be a fixed distance and orientation with respect to marker  114   a.    
     The information layer can include a variety of information from a variety of local or network information sources. Some examples of information include without limitation specifications, directions, recipes, data sheets, images, video clips, audio files, schemas, user interface elements, thumbnails, text, references or links, telephone numbers, blog or journal entries, notes, part numbers, dictionary definitions, catalog data, serial numbers, order forms, marketing or advertising and any other information that may be useful to a user. Some examples of information resources include without limitation: local databases or cache memory, network databases, Websites, online technical libraries, other devices, or any other information resource that can be accessed by device  100  either locally or remotely through a communication link. In the example shown, balloon call out  124  includes a manufacturer (“Acme”), name of component  108  (“Capacitor”) and part number (“# C  10361 ”). 
     Magnifying glass tool  116  can be manipulated by a user to magnify or zoom an object in live video  104 . For example, if the user wanted to see a detail of processor  106 , the user could move the magnifying glass tool  116  over processor  106  and live video  104  would zoom on processor  106  resulting in more detail. The view of the magnifying glass tool  116  can be sized using, for example, pinch gestures. 
       FIG. 1C  illustrates the example device of  FIG. 1B  displaying a three-dimensional (3D) perspective view of the live video combined with the information layer. In this example, the user is pointing the video camera of device  100  at a different location to obtain a 3D perspective view of the circuit board. The information layer can be overlaid on the perspective view and aligned without having to re-perform object recognition using data output from onboard motion sensors. For example, outputs from onboard gyros, magnetometers or other motion sensors can be used to determine current video camera view angles relative to a reference coordinate frame and then use the view angles to redraw the information layer over the perspective view such that annotations remain properly aligned with their respective objects. In the example shown, annotation  130  (the dashed line) has been relocated to surround memory cards  110  without re-performing manual or automatic object recognition. Using onboard sensors is advantageous in that a user can maneuver device around a collection of objects and have annotations appear without incurring delays associated with object recognition processing. Object recognition can be performed once on a collection of objects and the sensor data can be use to update annotations for the objects. 
     In some implementations, current video camera view angles can be used to index a look-up table of information layer data (e.g., annotations) for generating overlays that align correctly with objects in the live video. The video camera view angles can be represented by yaw, pitch and roll angles in a reference coordinate frame. For example, if we assume the yaw, pitch and roll angles are all zero when the video camera is pointing directly over the circuit board as shown in  FIG. 1A , then the angle set (0,0,0) can be associated with the particular annotations shown in  FIG. 1A . If the user pitches the video camera up by +90 degrees, then the angle set (0, 90, 0) can be associated with the annotations shown in  FIG. 1C . The look up table can be stored on the device or provided by a network resource. 
       FIG. 1D  illustrates synchronizing live video displays on first and second devices and sharing changes to the information layer. In the example shown, first device  100   a  is displaying live video  104   a , which is capturing a perspective view of the circuit board. Live video  104   a  can be fed to second device  100   b  through a communication link (e.g., unidirectional or bidirectional) so that second device  100   b  displays live video  104   b  of the circuit board. The information layer generated for live video  104   a  on device  100   a  can also shared with device  100   b  by sending the information layer data with the live video feed over the communication link. The communication link can be wired or wireless (e.g., Bluetooth, WiFi). 
     In some implementations, the sensor output data (e.g., video camera view angles) can be communicated to device  100   b  over the communication link so that the current orientation of the video camera on device  100   a  relative to the object is known to device  100   b . This sensor data can be used by device  100   b  to regenerate the information overlay on device  100   b  without sending device  100   b  the actual information layer data. 
     In some implementations, the user of either device  100   a  or device  100   b  can use touch input or gestures to generate new annotations (e.g., a draw a circle around a component) and those annotations can be shared with the other device through the communication link. In some implementations, a gesture itself can indicate desired information. For example, drawing a circle around processor  106  in live video  104  can indicate that the user wants more information about processor  106 . As a user draws annotations on live video  104   a  those annotations can be reflected to live video  104   b . This feature allows users of devices  100   a ,  100   b  to interact and collaborate through the information layer. In some implementations, if devices  100   a ,  100   b  have telephony capability the users can speak to each other while observing live video  104   a ,  104   b  and the information layer. 
     Other Example Applications 
     In one example application, device  100  can capture images or live video of a document and the text of the document can be recognized in the images or the live video. An information layer (e.g., an answer sheet) can be generated and combined with the live video. For example, a teacher can hold device  100  over a student&#39;s exam paper and an outline showing incorrect answers to exam questions can be displayed in the live video to assist the teach in grading the exam paper. 
     In another example, device  100  can capture a live video of an engine of a car or other vehicle and the parts of the engine can be recognized from the live video. An information layer (e.g., a manual excerpt) can be generated and combined with the live video. For example, a car mechanic can hold device  100  over a car engine and an outline identifying parts and providing excerpts from a repair manual or schematics can be displayed in the live video to assist the mechanic in repairing the engine. 
     Device  100  can be used in a variety of medical applications. In some implementations, a doctor can use device  100  to capture a live video of the patient&#39;s face. Using pattern recognition and/or other information (e.g., a bar code or other patient identifier), information related to the patient (e.g., medical history, drug prescriptions) can be displayed on device  100 . In other implementations, a live video of a body part that needs medical attention can be captured and augmented with annotations that can help the doctor make a diagnosis. The video can be shared with other doctors who can generate annotations on their respective devices to assist the doctor in a diagnosis. Pattern matching or other image processing can be used to identify problems with the injured body part based on its visual appearance (e.g., color). In one example application, an x-ray or MRI video can be displayed with the live video. 
     Example Split Screen Display with Computer-Generated Imagery 
       FIG. 2A  illustrates example device  200  having a split screen display with computer-generated imagery. In some implementations, a split screen display can be used to display an object or other subject matter on one side of the split, and computer-generated imagery (e.g., in either two or three dimensions) on the other side of the split. In the example shown, a user is viewing a live video of the skyline of downtown San Francisco in first display area  202 . Object recognition has been performed on a captured frame of video and an information layer has been generated. Specifically, balloon call outs have been displayed proximate to their respective buildings or structures in the live video. The user can interact with the information layer as described in reference to  FIGS. 1A-I  D. 
     In some implementations, the live video scene can be determined and object recognition assisted by using an onboard positioning system (e.g., GPS, WiFi, Cell ID). For example, a frame of captured video of downtown San Francisco can be transmitted to a network resource, together with the current geographic coordinates of device  200  received from the onboard positioning system. Additionally, motion sensor data (e.g., angle data) can be sent to the network service that defines the current view of the onboard video camera capturing the live video. The motion sensor can be used to select a subset of pre-computed computer-generated imagery of downtown San Francisco that is relevant to the current view of the onboard video camera. 
     Second display area  204  of the split screen display can show computer-generated imagery of the objects (e.g., buildings) in the images (e.g., live video) of display area  202 . In some implementations, the computer-generated imagery can be created on the fly or can be retrieved from a repository. For example, once the live video has been identified as downtown San Francisco, computer-generated imagery of downtown San Francisco can be downloaded from a network resource. Alternatively, known real-time rendering techniques can be used to generate 3D computer-generated imagery that can be navigated by the user. For example, 3D models of recognized objects of downtown San Francisco can be constructed out of geometrical vertices, faces, and edges in a 3D coordinate system. The models can be rendered using known real-time rendering techniques (e.g., orthographic or perspective projection, clipping, screen mapping, rasterizing) and transformed into the current view space of the live video camera. Transforming models into the current view space can be accomplished using sensor output from onboard sensors. For example, gyroscopes, magnetometers and other motion sensors can provide angular displacements, angular rates and magnetic readings with respect to a reference coordinate frame, and that data can be used by a real-time onboard rendering engine to generate 3D imagery of downtown San Francisco. If the user physically moves device  200 , resulting in a change of the video camera view, the information layer and computer-generated imagery can be updated accordingly using the sensor data. In some implementations, the user can manipulate navigation control  212  to navigate the 3D imagery (e.g., tilting, zooming, panning, moving). 
     In some implementations, the current location of device  200  can be used to compute a route for display in the 3D computer-generated imagery. In the example shown, marker  206  (e.g., a pushpin) can be used to identify the current location of device  200  (in this example indicated as “You”), and second marker  210  can be used to identify a destination or another device (in this example indicated by “Joe”). A route can then be computed and overlaid on the 3D computer-generated imagery as shown in  FIG. 2A . Touching markers  206 ,  210  can invoke various applications on device  200 , such as a communication application (e.g., text messaging, chat session, email, telephony) for allowing communication between device  200   a  and device  200   b.    
     Example Synchronization of Split Screen Displays 
       FIG. 2B  illustrates synchronizing split screen displays of first and second devices  200   a ,  200   b . In the example shown, device  200   a  has established communication with device  200   b . The image (e.g., live video) scene of downtown San Francisco captured by the video camera on device  200   a  can be displayed in display area  202   b  of device  200   b . Also, computer-generated imagery shown in display area  204   a  can be shown in display area  204   b  of device  200   b . Note that in display area  204   b , the location of device  200   b  is indicated by “You” and the destination or device  200   a  is indicated by the marker “Mark,” i.e., the user of device  200   a . The communication link can be a direct communication link or an indirect communication link using wireless network access points (e.g., WiFi access points). The communication link can also include a wide area network, such as the Internet. 
     When a user moves device  200   a , resulting in a change in the video camera view, motion sensor data can be used to update the computer-generated imagery in display areas  204   a ,  204   b , thus maintaining synchronization between display areas  202   a ,  204   a  and display areas  202   b ,  204   b . In some implementations, share button  214  can be used to initiate sharing of live video, the information layer and computer-generated imagery with another device. 
     Example Process for Synchronizing Displays 
       FIG. 3  is a flow diagram of an example process  300  for synchronizing, interactive AR displays. Process  300  can be described in reference to devices  100 ,  200 . 
     In some implementations, process  300  can begin on a device (e.g., device  100  or  200 ) by capturing live video of a real-world, physical environment ( 302 ). One or more objects in the live video can be identified ( 304 ). The objects can be identified manually (e.g., by user selection using touch input) or automatically using known object recognition techniques. An information layer related to the one or more objects is generated and can include one or more annotations ( 306 ). The information layer and live video are combined in a display ( 308 ). Sensor data generated by one or more onboard sensors is received ( 310 ). The data can be angle data from a gyro, for example. The live video and information layer are synchronized using the sensor data ( 312 ). Optionally, computer imagery can be generated representing objects in the live video ( 314 ). The computer imagery can be pre-computed and retrieved from a repository or generated on the fly using known real-time rendering techniques. Optionally, the annotated live video, computer-generated imagery and information layer can be displayed in a split screen display ( 316 ), as described in reference to  FIG. 2A . Optionally, the annotated live video, computer-generated imagery and information layer can be shared ( 318 ) with one or more other devices, and the AR displays of the devices can be synchronized to account for changes in video views. 
     Example Device Architecture 
       FIG. 4  is a block diagram of an example architecture for a device  400  implementing synchronized, interactive AR displays. Device  400  can include memory interface  402 , one or more data processors, image processors and/or central processing units  404 , and peripherals interface  406 . Memory interface  402 , one or more processors  404  and/or peripherals interface  406  can be separate components or can be integrated in one or more integrated circuits. The various components in device  400  can be coupled by one or more communication buses or signal lines. 
     Sensors, devices, and subsystems can be coupled to peripherals interface  406  to facilitate multiple functionalities. For example, motion sensor  410 , light sensor  412 , and proximity sensor  414  can be coupled to peripherals interface  406  to facilitate various orientation, lighting, and proximity functions. For example, in some implementations, light sensor  412  can be utilized to facilitate adjusting the brightness of touch screen  446 . In some implementations, motion sensor  411  can be utilized to detect movement of the device. Accordingly, display objects and/or media can be presented according to a detected orientation, e.g., portrait or landscape. 
     Other sensors  416  can also be connected to peripherals interface  406 , such as a temperature sensor, a biometric sensor, a gyroscope, magnetometer or other sensing device, to facilitate related functionalities. 
     For example, positioning information can be received by device  400  from positioning system  432 . Positioning system  432 , in various implementations, can be a component internal to device  400 , or can be an external component coupled to device  400  (e.g., using a wired connection or a wireless connection). In some implementations, positioning system  432  can include a GPS receiver and a positioning engine operable to derive positioning information from received GPS satellite signals. In other implementations, positioning system  432  can include a compass (e.g., a magnetic compass) and an accelerometer, as well as a positioning engine operable to derive positioning information based on dead reckoning techniques. In still further implementations, positioning system  432  can use wireless signals (e.g., cellular signals, IEEE 802.11 signals) to determine location information associated with the device Hybrid positioning systems using a combination of satellite and television signals. 
     Broadcast reception functions can be facilitated through one or more radio frequency (RF) receiver(s)  418 . An RF receiver can receive, for example, AM/FM broadcasts or satellite broadcasts (e.g., XM® or Sirius® radio broadcast). An RF receiver can also be a TV tuner. In some implementations, RF receiver  418  is built into wireless communication subsystems  424 . In other implementations, RF receiver  418  is an independent subsystem coupled to device  400  (e.g., using a wired connection or a wireless connection). RF receiver  418  can receive simulcasts. In some implementations, RF receiver  418  can include a Radio Data System (RDS) processor, which can process broadcast content and simulcast data (e.g., RDS data). In some implementations, RF receiver  418  can be digitally tuned to receive broadcasts at various frequencies. In addition, RF receiver  418  can include a scanning function which tunes up or down and pauses at a next frequency where broadcast content is available. 
     Camera subsystem  420  and optical sensor  422 , 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 communication subsystems  424 . Communication subsystem(s) can include one or more wireless communication subsystems and one or more wired communication subsystems. Wireless communication subsystems can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. Wired communication system can include a port device, e.g., a Universal Serial Bus (USB) port or some other wired port connection that can be used to establish a wired connection to other computing devices, such as other communication devices, network access devices, a personal computer, a printer, a display screen, or other processing devices capable of receiving and/or transmitting data. The specific design and implementation of communication subsystem  424  can depend on the communication network(s) or medium(s) over which device  400  is intended to operate. For example, device  400  may include wireless communication subsystems designed to operate over a global system for mobile communications (GSM) network, a GPRS network, an enhanced data GSM environment (EDGE) network, 802.x communication networks (e.g., WiFi, WiMax, or 3G networks), code division multiple access (CDMA) networks, and a Bluetooth™ network. Communication subsystems  424  may include hosting protocols such that Device  400  may be configured as a base station for other wireless devices. As another example, the communication subsystems can allow the device to synchronize with a host device using one or more protocols, such as, for example, the TCP/IP protocol, HTTP protocol, UDP protocol, and any other known protocol. 
     Audio subsystem  426  can be coupled to speaker  428  and one or more microphones  430 . One or more microphones  430  can be used, for example, to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions. 
     I/O subsystem  440  can include touch screen controller  442  and/or other input controller(s)  444 . Touch-screen controller  442  can be coupled to touch screen  446 . Touch screen  446  and touch screen controller  442  can, for example, detect contact and movement or break thereof using any of a number 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 touch screen  446  or proximity to touch screen  446 . 
     Other input controller(s)  444  can be coupled to other input/control devices  448 , such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, 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 speaker  428  and/or microphone  430 . 
     In one implementation, a pressing of the button for a first duration may disengage a lock of touch screen  446 ; and a pressing of the button for a second duration that is longer than the first duration may turn power to device  400  on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen  446  can, for example, also be used to implement virtual or soft buttons and/or a keyboard. 
     In some implementations, device  400  can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, device  400  can include the functionality of an MP3 player, such as an iPhone™. 
     Memory interface  402  can be coupled to memory  450 . Memory  450  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). Memory  450  can store operating system  452 , such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks. Operating system  452  may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, operating system  452  can be a kernel (e.g., UNIX kernel). 
     Memory  450  may also store communication instructions  454  to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. Communication instructions  454  can also be used to select an operational mode or communication medium for use by the device, based on a geographic location (obtained by GPS/Navigation instructions  468 ) of the device. Memory  450  may include graphical user interface instructions  456  to facilitate graphic user interface processing; sensor processing instructions  458  to facilitate sensor-related processing and functions; phone instructions  460  to facilitate phone-related processes and functions; electronic messaging instructions  462  to facilitate electronic-messaging related processes and functions; web browsing instructions  464  to facilitate web browsing-related processes and functions; media processing instructions  466  to facilitate media processing-related processes and functions; GPS/Navigation instructions  468  to facilitate GPS and navigation-related processes and instructions, e.g., mapping a target location; camera instructions  470  to facilitate camera-related processes and functions (e.g., live video); and augmented reality instructions  472  to facilitate the processes and features described in reference to  FIGS. 1-3 . Memory  450  may also store other software instructions (not shown), such as web video instructions to facilitate web video-related processes and functions; and/or web shopping instructions to facilitate web shopping-related processes and functions. In some implementations, media processing instructions  466  are divided into audio processing instructions and video processing instructions to facilitate audio processing-related processes and functions and video processing-related processes and functions, respectively. 
     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 applications, procedures, or modules. Memory  450  can include additional instructions or fewer instructions. Furthermore, various functions of device  400  may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits. 
     Example Network Operating Environment 
       FIG. 5  is a block diagram of an example network operating environment for devices implementing synchronized, interactive augmented reality displays. Devices  502   a  and  502   b  can, for example, communicate over one or more wired and/or wireless networks  510  in data communication. For example, wireless network  512 , e.g., a cellular network, can communicate with a wide area network (WAN)  514 , such as the Internet, by use of gateway  516 . Likewise, access device  518 , such as an 802.11g wireless access device, can provide communication access to wide area network  514 . In some implementations, both voice and data communications can be established over wireless network  512  and access device  518 . For example, device  502   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 or streams, such as Web pages, photographs, and videos, over wireless network  512 , gateway  516 , and wide area network  514  (e.g., using TCP/IP or UDP protocols). Likewise, in some implementations, device  502   b  can place and receive phone calls, send and receive e-mail messages, and retrieve electronic documents over access device  1218  and wide area network  514 . In some implementations, devices  502   a  or  502   b  can be physically connected to access device  518  using one or more cables and access device  518  can be a personal computer. In this configuration, device  502   a  or  502   b  can be referred to as a “tethered” device. 
     Devices  502   a  and  502   b  can also establish communications by other means. For example, wireless device  502   a  can communicate with other wireless devices, e.g., other devices  502   a  or  502   b , cell phones, etc., over wireless network  512 . Likewise, devices  502   a  and  502   b  can establish peer-to-peer communications  520 , e.g., a personal area network, by use of one or more communication subsystems, such as a Bluetooth™ communication device. Other communication protocols and topologies can also be implemented. 
     Devices  502   a  or  502   b  can, for example, communicate with one or more services over one or more wired and/or wireless networks  510 . These services can include, for example, navigation services  530 , messaging services  540 , media services  550 , location based services  580 , syncing services  560  and AR services  570 . Syncing services  560  can support over network syncing of AR displays on two or more devices. AR services  570  can provide services to support the AR features and processes described in reference to  FIGS. 1-3 . 
     Device  502   a  or  502   b  can also access other data and content over one or more wired and/or wireless networks  510 . For example, content publishers, such as news sites, RSS feeds, web sites, blogs, social networking sites, developer networks, etc., can be accessed by Device  502   a  or  502   b . Such access can be provided by invocation of a web browsing function or application (e.g., a browser) in response to a user touching, for example, a Web object. 
     The features described can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The features can be implemented in a computer program product tangibly embodied in an information carrier, e.g., in a machine-readable storage device, for execution by a programmable processor, and method steps can be performed by a programmable processor executing a program of instructions to perform functions of the described implementations by operating on input data and generating output. Alternatively or addition, the program instructions can be encoded on a propagated signal that is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information fro transmission to suitable receiver apparatus for execution by a programmable processor. 
     The described features can be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. A computer program is a set of instructions that can be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result. A computer program can be written in any form of programming language (e.g., Objective-C, Java), including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. 
     Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors or cores, of any kind of computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer will also include, or be operatively coupled to communicate with, one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, ASICs (application-specific integrated circuits). 
     To provide for interaction with a user, the features can be implemented on a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user and a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer. 
     The features can be implemented in a computer system that includes a back-end component, such as a data server, or that includes a middleware component, such as an application server or an Internet server, or that includes a front-end component, such as a client computer having a graphical user interface or an Internet browser, or any combination of them. The components of the system can be connected by any form or medium of digital data communication such as a communication network. Examples of communication networks include, e.g., a LAN, a WAN, and the computers and networks forming the Internet. 
     The computer system can include clients and servers. A client and server are generally remote from each other and typically interact through a network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. 
     One or more features or steps of the disclosed embodiments can be implemented using an Application Programming Interface (API). An API can define on or more parameters that are passed between a calling application and other software code (e.g., an operating system, library routine, function) that provides a service, that provides data, or that performs an operation or a computation. 
     The API can be implemented as one or more calls in program code that send or receive one or more parameters through a parameter list or other structure based on a call convention defined in an API specification document. A parameter can be a constant, a key, a data structure, an object, an object class, a variable, a data type, a pointer, an array, a list, or another call. API calls and parameters can be implemented in any programming language. The programming language can define the vocabulary and calling convention that a programmer will employ to access functions supporting the API. 
     In some implementations, an API call can report to an application the capabilities of a device running the application, such as input capability, output capability, processing capability, power capability, communications capability, etc. 
     A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. For example, elements of one or more implementations may be combined, deleted, modified, or supplemented to form further implementations. As yet another example, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. In addition, other steps may be provided, or steps may be eliminated, from the described flows, and other components may be added to, or removed from, the described systems. Accordingly, other implementations are within the scope of the following claims.

Metadata:
Filing Date: 20190104
Publication Date: 20201201
Grant Date: 20201201
Priority Date: 20100105
Inventors: BILBREY, BRETT C.
KING, NICHOLAS V.
PANCE, ALEKSANDAR
Assignee: APPLE INC
CPC Classifications: [{"code": "H04N23/632", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N23/661", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N23/632", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N23/661", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F1/1694", "inventive": true, "first": true, "tree": "[]"}, {"code": "H04N5/272", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G09G2340/12", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04N21/8133", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T19/006", "inventive": true, "first": true, "tree": "[]"}, {"code": "G09G5/377", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/4312", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/42202", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F1/1694", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/011", "inventive": true, "first": false, "tree": "[]"}, {"code": "G09G2354/00", "inventive": false, "first": false, "tree": "[]"}, {"code": "G09G2340/125", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F2203/04803", "inventive": false, "first": false, "tree": "[]"}, {"code": "G09G2354/00", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04N21/4788", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N1/00323", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/42202", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/4312", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/2187", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/2187", "inventive": true, "first": false, "tree": "[]"}, {"code": "G09G2340/12", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/011", "inventive": true, "first": false, "tree": "[]"}, {"code": "G09G2340/14", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04N21/472", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/8133", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N1/00323", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/4314", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/472", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T19/20", "inventive": true, "first": false, "tree": "[]"}, {"code": "G09G2340/14", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04N21/4788", "inventive": true, "first": false, "tree": "[]"}, {"code": "G09G2340/125", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F2203/04803", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T2219/004", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04N21/4314", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N5/222", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/0488", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N5/23293", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N5/222", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/472", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F3/011", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06F2203/04803", "inventive": false, "first": false, "tree": "[]"}, {"code": "G09G5/377", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/4314", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T2219/004", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04N21/4312", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/8133", "inventive": true, "first": false, "tree": "[]"}, {"code": "G09G2354/00", "inventive": false, "first": false, "tree": "[]"}, {"code": "G09G2340/125", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06T19/006", "inventive": true, "first": true, "tree": "[]"}, {"code": "G09G2340/14", "inventive": false, "first": false, "tree": "[]"}, {"code": "H04N1/00323", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/42202", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/4788", "inventive": true, "first": false, "tree": "[]"}, {"code": "G09G2340/12", "inventive": false, "first": false, "tree": "[]"}, {"code": "G06F1/1694", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N5/272", "inventive": true, "first": false, "tree": "[]"}, {"code": "H04N21/2187", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T19/20", "inventive": true, "first": false, "tree": "[]"}, {"code": "G06T19/006", "inventive": true, "first": false, "tree": "[]"}]
Family ID: 44224511