Patent Grant
11417066
Miniaturization of consumer electronics with sophisticated graphics capabilities and expansive computing power has augmented the activities one can engage in via consumer electronics and in particular, portable electronics such as smart phones, tablets, and the like. The advancements in technologies also have brought science fiction into reality.
Further, portable electronics or other electronics devices now generally include a large variety of sensing capabilities. These capabilities can be utilized to further enhance the users' augmented reality experiences.
The present embodiments are illustrated by way of example and are not intended to be limited by the figures of the accompanying drawings. In the drawings:
The same reference numbers and any acronyms identify elements or acts with the same or similar structure or functionality throughout the drawings and specification for ease of understanding and convenience.
Techniques are disclosed for facilitating electronic commerce in an augmented reality environment. In some embodiments, a method comprises detecting, by a mobile device, presence of the physical product or the real life service; and presenting, on the mobile device, information to conduct the transaction of a physical product or a real life service via an augmented reality environment. The mobile device facilitates the augmented reality environment. In some embodiments, a method comprises detecting one or more targets in the augmented reality platform using a select area in a perspective of a user, the perspective being captured by a mobile device; and prompting the user to choose an object of interest from the one or more detected targets. Among other advantages, embodiments disclosed herein provide an intuitive and integrated user experience in shopping using augmented reality devices, thereby reducing the consumer user's effort in conducting such activities, reducing necessary sales personnel and their working hours, and increasing sales.
Reference in this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.
The terms used in this specification generally have their ordinary meanings in the art, within the context of the disclosure, and in the specific context where each term is used. Certain terms that are used to describe the disclosure are discussed below, or elsewhere in the specification, to provide additional guidance to the practitioner regarding the description of the disclosure. For convenience, certain terms may be highlighted, for example using italics and/or quotation marks. The use of highlighting has no influence on the scope and meaning of a term; the scope and meaning of a term is the same, in the same context, whether or not it is highlighted. It will be appreciated that same thing can be said in more than one way.
Consequently, alternative language and synonyms may be used for any one or more of the terms discussed herein, nor is any special significance to be placed upon whether or not a term is elaborated or discussed herein. Synonyms for certain terms are provided. A recital of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification including examples of any terms discussed herein is illustrative only, and is not intended to further limit the scope and meaning of the disclosure or of any exemplified term. Likewise, the disclosure is not limited to various embodiments given in this specification.
Without intent to further limit the scope of the disclosure, examples of instruments, apparatus, methods and their related results according to the embodiments of the present disclosure are given below. Note that titles or subtitles may be used in the examples for convenience of a reader, which in no way should limit the scope of the disclosure. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. In the case of conflict, the present document, including definitions will control.
Mobile devices, especially the wearable ones which may be in forms of eyewear, mobile-enabled wrist watches, head-mounted displays, are now available to provide augmented reality experiences to users. Embodiments of the present disclosure include systems and methods for facilitating transactions of a physical product or real life service via an augmented reality environment. Additionally, embodiments of the present disclosure include systems and methods for enabling selection of a physical product or a real life service in an augmented reality platform via a mobile device.
The mobile devices 102A-N can be any system and/or device, and/or any combination of devices/systems that is able to establish a connection with another device, a server and/or other systems. The mobile devices 102A-N typically include a display and/or other output functionalities to present information and data exchanged between/among the devices 102A-N and the host server 124. For example, the mobile devices 102A-N can be any of, but are not limited to, a server desktop, a desktop computer, a computer cluster, or portable devices including, a notebook, a laptop computer, a handheld computer, a palmtop computer, a mobile phone, a cell phone, a smart phone, a PDA, a Blackberry device, a Treo, an iPhone, cover headsets, heads-up displays, helmet mounted display, head-mounted display, scanned-beam display, wearable computer such as mobile enabled watches, and/or any other mobile interfaces and viewing devices, etc. Additional examples of mobile devices 102A-N can include a Google Glass, smart glasses/goggles, a smart phone, or other suitable mobile computing devices that are configured to facilitate or enable an augmented reality environment or platform. The mobile devices 102A-N may be location-aware devices that are able to determine their own location or identify location information from an external source. In one embodiment, the mobile devices 102A-N are coupled to a network 106. In some embodiments, the devices 102A-N and host server 124 may be directly connected to one another.
In one embodiment, the host server 124 is operable to provide simulated objects (e.g., objects, computer-controlled objects, or simulated objects) that correspond to real world physical locations to be presented to users on mobile devices 102A-N. The simulated objects are typically software entities or occurrences that are controlled by computer programs and can be generated upon request when certain criteria are met. The host server 124 also processes interactions of simulated object with one another and actions on simulated objects caused by stimulus from a real user and/or the real world environment.
In some embodiments, the host server 124 is operable, in conjunction with the mobile devices 102A-N, to facilitate electronic commercial transactions in an augmented reality environment or platform, such as an augmented reality marketplace. Services and functions provided by the host server 124 and the components therein are described in detail with further references to the examples of
The mobile devices 102A-N are generally operable to provide access (e.g., visible access, audible access) to the simulated objects to users, for example via user interface 104A-N displayed on the display units. The devices 102A-N may be able to detect simulated objects based on location and/or timing data and provide those objects authorized by the user for access via the devices. In some embodiments, the mobile devices 102A-N can facilitate electronic commercial transactions in an augmented reality environment. In some embodiments, the devices 102A-N communicate with the host server 124 in facilitating the transactions. Services and functions provided by the mobile devices 102A-N and the components therein are described in detail with further references to the examples of
The network 106, over which the mobile devices 102A-N and the host server 124 communicate, may be a telephonic network, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. For example, the Internet can provide file transfer, remote log in, email, news, RSS, and other services through any known or convenient protocol, such as, but is not limited to the TCP/IP protocol, Open System Interconnections (OSI), FTP, UPnP, iSCSI, NSF, ISDN, PDH, RS-232, SDH, SONET, etc.
The network 106 can be any collection of distinct networks operating wholly or partially in conjunction to provide connectivity to the mobile devices 102A-N and the host server 124 and may appear as one or more networks to the serviced systems and devices. In one embodiment, communications to and from the mobile devices 102A-N can be achieved by, an open network, such as the Internet, or a private network, such as an intranet and/or the extranet. In one embodiment, communications can be achieved by a secure communications protocol, such as secure sockets layer (SSL), or transport layer security (TLS).
In addition, communications can be achieved via one or more wireless networks, such as, but is not limited to, one or more of a Local Area Network (LAN), Wireless Local Area Network (WLAN), a Personal area network (PAN), a Campus area network (CAN), a Metropolitan area network (MAN), a Wide area network (WAN), a Wireless wide area network (WWAN), Global System for Mobile Communications (GSM), Personal Communications Service (PCS), Digital Advanced Mobile Phone Service (D-Amps), Bluetooth, Wi-Fi, Fixed Wireless Data, 2G, 2.5G, 3G (e.g., WCDMA/UTMS based 3G networks), 3.5G, 4G, !MT-Advanced, pre-4G, LTE Advanced, mobile WiMax, WiMax 2, WirelessMAN-Advanced networks, enhanced data rates for GSM evolution (EDGE), General packet radio service (GPRS), enhanced GPRS, iBurst, UMTS, HSPDA, HSPA, HSPA+, UMTS-TDD, lxRTT, EV-DO, messaging protocols such as, TCP/IP, SMS, MMS, extensible messaging and presence protocol (XMPP), real time messaging protocol (RTMP), instant messaging and presence protocol (IMPP), instant messaging, USSD, IRC, or any other wireless data networks or messaging protocols.
The host server 124 may include or be coupled to a user repository 128 and/or a simulated object repository 130 and or a merchandise object repository 132. The data repositories 128, 130, 132 can store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server 124 and/or any other servers for operation. The data repositories 128, 130, 132 may be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc.
The repositories 128, 130, 132 can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOinstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.
In some embodiments, the host server 124 is able to provide data to be stored in the user data repository 128, the simulated object repository 130, the merchandise object repository 132, and/or the can retrieve data stored in the user data repository 128 and/or the simulated object repository 130 and/or the merchandise object repository 132.
The user data repository 128 can store user information, user preferences, user profile, user list of interest, user favorite, user bookmark, user annotation, user tags, access permissions associated with the users, device information, hardware information, etc. The simulated object repository 130 can store software entities (e.g., computer programs) that control simulated objects and the simulated environments in which they are presented for visual/audible access or control/manipulation.
The simulated object repository 130 may further include simulated objects and their associated data structures with metadata defining the simulated object including its associated access permission.
The merchandise object repository 132 can store merchandise information including, for example, merchandise name, alias, attributes, shape, size, dimension, or other physical characteristics or recognition patterns or augmented reality markers, location (if suitable), vendor(s), price, SKU code, QR code, I-dimensional or 2-dimensional or multi-dimensional barcode, RFID code, metadata, tags, annotations, sales contact information.
In the example of
In the example of
The firewall 204, can, in some embodiments, govern and/or manage permission to access/proxy data in a computer network, and track varying levels of trust between different machines and/or applications. The firewall 204 can be any number of modules having any combination of hardware and/or software components able to enforce a predetermined set of access rights between a particular set of machines and applications, machines and machines, and/or applications and applications, for example, to regulate the flow of traffic and resource sharing between these varying entities. The firewall 204 may additionally manage and/or have access to an access control list which details permissions including for example, the access and operation rights of an object by an individual, a machine, and/or an application, and the circumstances under which the permission rights stand.
Other network security functions can be performed or included in the functions of the firewall 204, can be, for example, but are not limited to, intrusion-prevention, intrusion detection, next-generation firewall, personal firewall, etc. without deviating from the novel art of this disclosure. In some embodiments, the functionalities of the network controller 202 and the firewall 204 are partially or wholly combined and the functions of which can be implemented in any combination of software and/or hardware, in part or in whole.
In the example of
In addition, the multimedia server 206 can facilitate transmission/receipt of streaming data such as streaming images, audio, and/or video. The multimedia server 206 can be configured separately or together with the web application server 212, depending on a desired scalability of the host server 224. Examples of graphics file formats that can be managed by the multimedia server 206 include but are not limited to, ADRG, ADRI, AI, GIF, IMA, GS, JPG, JP2, PNG, PSD, PSP, TIFF, and/or BMP, etc.
The web application server 212 can include any combination of software agents and/or hardware modules for accepting Hypertext Transfer Protocol (HTTP) requests from end users, external systems, and/or external mobile devices and responding to the request by providing the requestors with web pages, such as HTML documents and objects that can include static and/or dynamic content (e.g., via one or more supported interfaces, such as the Common Gateway Interface (CGI), Simple CGI (SCGI), PHP, JavaServer Pages (JSP), Active Server Pages (ASP), ASP.NET, etc.). In addition, a secure connection, SSL and/or TLS can be established by the web application server 212.
The e-commerce server 213 can include any combination of software agents and/or hardware modules for facilitating electronic commercial transactions to be initiated, processed, and completed with mobile devices (e.g., devices 102A-N, FIG. 1). The e-commerce server 213 typically includes at least one processor and a memory, and may be further connected to one or more computers (not shown in
In general, the host server 224 assists, by interactively or proactively providing relevant information, mobile devices such as device 102A-N to generate the augmented reality user interfaces, which facilitate the augmented reality marketplace disclosed herein, as shown in the example screenshots of
The databases 216, 218 can store software, descriptive data, images, system information, drivers, and/or any other data item utilized by other components of the host server for operation. The databases 216, 218 may be managed by a database management system (DBMS), for example but not limited to, Oracle, DB2, Microsoft Access, Microsoft SQL Server, PostgreSQL, MySQL, FileMaker, etc. The databases 216,218 can be implemented via object-oriented technology and/or via text files, and can be managed by a distributed database management system, an object-oriented database management system (OODBMS) (e.g., ConceptBase, FastDB Main Memory Database Management System, JDOinstruments, ObjectDB, etc.), an object-relational database management system (ORDBMS) (e.g., Informix, OpenLink Virtuoso, VMDS, etc.), a file system, and/or any other convenient or known database management package.
In the example of
The host server 324 includes a network interface 302, a repository manager 304, and/or a search engine 322. The host server 324 is also coupled to a user data repository 328 and/or a merchandise object repository 332. The user data repository 328 and merchandise object repository 332 are described with further reference to the example of
Additional or less modules can be included without deviating from the techniques discussed in this disclosure. In addition, each module in the example of
The host server 324, although illustrated as comprised of distributed components (physically distributed and/or functionally distributed), could be implemented as a collective element. In some embodiments, some or all of the modules, and/or the functions represented by each of the modules can be combined in any convenient or known manner. Furthermore, the functions represented by the modules can be implemented individually or in any combination thereof, partially or wholly, in hardware, software, or a combination of hardware and software.
In the example of
The merchandise object repository 332 can be a database that comprises any combination of software agents and/or hardware modules able to store, modify, update, adjust, edit, and/or delete various physical as well as other attributes of a merchandise object (e.g., a physical product, or a real life service). The management functions of these physical and other attributes of merchandise objects can be performed by the repository manager 304.
A merchandise object can include a physical entity or goods (such as a store, a merchant, commercial product, a living object, an inanimate object, etc.) or a real life service (such as a restaurant, a spa, a beauty salon, a medical doctor, an art performance, etc.). In some embodiments, merchandise objects can be identified/recognized/detected using the various physical and/or other characteristics of the objects, and information relevant to commercial transactions of the physical product or real life service can be presented/displayed/projected in the augmented reality environment so as to enable the user to conduct such transactions.
Characteristics and attributes of merchandise objects that help the identification/recognition/detection can include what can be perceived by users in the augmented reality via a physical device (e.g., a mobile device or device 102 in the example of
One embodiment of the host server 324 includes a search engine 322. The search engine 322 can be any combination of software agents and/or hardware modules able to search, detect, and/or identify merchandise objects.
More specifically, attributes/clues/characteristics observed by the mobile device can be sent to the search engine 322. The search engine 322 can perform textual or imagery or other suitable types of search to identify the merchandise object. The search engine 322 can search or detect objects either automatically or in response to user request. For example, the user can request access to merchandise objects' information by perform a search request. The search request parameters can include, one or more of, at least a partial name input of the merchandise object from the user, the user's location, the current time or a time period. The search that is performed can automatically detect the merchandise object(s) being viewing by or otherwise available for access to the user in the augmented reality. In one embodiment, the merchandise objects are further filtered based on preferences or profiles or interest of the user.
The search engine 322 can further utilize the recognition/disambiguation process module 323 to prompt the user to assist in disambiguation of the merchandise object. For example, the module 323 can generate a plurality of choices in forms of name, picture, locational information, and/or description that can help the recognition. For another example, the module 323 can prompt the user to enter a partial or a full name. For yet another example, the module 323 can ask the user to take a plurality of pictures of the merchandise object.
Once identified or detected the presence of the merchandise object or product, the host server 324 can access relevant information including, for example, purchase information of the product, price from the vendor of the exact product that the user is viewing in the augmented reality, price from another vendor of the same or similar product, availability of the product, any metadata or tags of the product, annotations or reviews of the product added by another user of the augmented reality environment, images or video clips that are shared by other users or the merchant, and/or sales contact information. These information can be generated, maintained and updated using the modules 312-320 coupled to the repository manager 304 (e.g., by the merchant, by the user, by another user, or by an administrator of the host server 324).
In some embodiments, the merchandise object is stored in the merchandise object repository 332 using a data structure having metadata. The metadata can properties of the simulated object, location and/or timing parameters (e.g., sale event, availability, store hours, etc.) The location data can be specified with longitude and latitude coordinates, GPS coordinates, and/or relative position. In one embodiment, the object is associated with a unique identifier or augmented reality (AR) markers. The unique identifier or markers may be further associated with a location data structure having a set of location data that includes the qualifying location data for the merchandise object. In one embodiment, the metadata includes a link to data from an external source (e.g., the store's or merchant's website on the Internet).
In one embodiment, this information is automatically provided to the user when he or she arrives at or near the merchandise object's location (e.g., implicit request) via the device. Alternatively, the information is provided upon request by the user (e.g., explicit request). For example, merchandise objects associated with various attractions, for example, in a shopping mall or a tourist location in the real world, can be selected by the user (e.g., via input to the device).
Additionally, an advertisement (e.g., an electronic advertisement) that is relevant to the merchandise object is delivered by the advertisement/coupon management module 320 to the user that qualifies one or more criteria. The user may qualify on a basis of a location, identity, and/or a timing parameter. For example, the user may be provided with advertisements of local pizza shops or other late night dining options when the user is driving around town during late night hours when other dining options may not be available. In another example, an electronic coupon can be presented to a user using the device based on the merchandise object identification result, for example, when the device is located at the location during a certain period of time that satisfies the criteria. The electronic coupon may be redeemed by the user for conducting transactions of the physical product or the real life service.
In one embodiment, host server 334 includes a network interface 302, a processing unit 334, a memory unit 336, a storage unit 338, a location sensor 340, and/or a timing module 342. Additional or less units or modules may be included. The host server 324 can be any combination of hardware components and/or software agents for generating information for merchandise objects in facilitating transactions in an augmented reality marketplace environment. The network interface 302 has been described in the example of
One embodiment of the host server 324 further includes a processing unit 334. The data received from the network interface 302, location sensor 340, and/or the timing module 342 can be input to a processing unit 334. The location sensor 340 can include GPS receivers, RF transceiver, an optical rangefinder, etc. The timing module 342 can include an internal clock, a connection to a time server (via NTP), an atomic clock, a GPS master clock, etc.
The processing unit 334 can include one or more processors, CPUs, microcontrollers, FPGAs, ASICs, DSPs, or any combination of the above. Data that is input to the host server 334 can be processed by the processing unit 334 and output to a display and/or output via a wired or wireless connection to an external device, such as a mobile phone, a portable device, a host or server computer by way of a communications component.
One embodiment of the host server 324 further includes a memory unit 336 and a storage unit 338. The memory unit 335 and a storage unit 338 are, in some embodiments, coupled to the processing unit 334. The memory unit can include volatile and/or non-volatile memory. In receiving characteristics of and generating relevant information for the merchandise objects, the processing unit 334 may perform one or more processes related to identifying/recognizing/detecting the merchandise objects and/or generating information for conducting transactions of such objects.
In some embodiments, any portion of or all of the functions described of the various example modules in the host server 324 of the example of
The mobile device 402 includes a network interface 404, a timing module 406, an RF sensor 407, a location sensor 408, an image sensor 409, an object identifier module 412, a user selection module 414, a user stimulus sensor 416, a motion/gesture sensor 418, an environmental stimulus sensor 420, an audio/video output module 422, and/or other sensors 410. The mobile device 402 may be any electronic device such as the devices described in conjunction with the mobile devices 102A-N in the example of
In one embodiment, the mobile device 402 is coupled to a merchandise object repository 431 for identifying/detecting/recognizing merchandise objects (e.g., physical product or real life service) in the augmented reality environment. The merchandise object repository 431 may be internal to or coupled to the mobile device 402 but the contents stored therein can be illustrated with reference to the example of a merchandise object repository 132 described in the example of
Additional or less modules can be included without deviating from the novel art of this disclosure. In addition, each module in the example of
The mobile device 402, although illustrated as comprised of distributed components (physically distributed and/or functionally distributed), could be implemented as a collective element. In some embodiments, some or all of the modules, and/or the functions represented by each of the modules can be combined in any convenient or known manner. Furthermore, the functions represented by the modules can be implemented individually or in any combination thereof, partially or wholly, in hardware, software, or a combination of hardware and software.
In the example of
According to the embodiments disclosed herein, the mobile device 402 can facilitate transactions (e.g., e-commerce transactions) of a merchandise object (e.g., a physical product or a real life service) via an augmented reality environment provided by the mobile device 402. The mobile device 402 can detect presence of the physical product or the real life service when the product or service is seen/viewed/looked at by the user or in vicinity of the user. In some embodiments, the mobile device 402 automatically identifies the product or service from a perspective of a user. The perspective can be captured or sensed by the mobile device 402 via, for example, a camera or an image sensor.
After detecting/identifying/recognizing the merchandise object, the mobile device 402 can access information relevant to the transaction of the merchandise object(s) from a merchandise object repository (e.g., repository 431 in mobile device 402 and/or repository 332 in host server 324), and can present the relevant information to the user to conduct the transaction of the product or service via the augmented reality environment. For example, the mobile device 402 can render on a display of the device 402
More specifically, one embodiment of the mobile device 402 includes a timing module 406. The timing module 406 can be any combination of software agents and/or hardware modules able to identify, detect, transmit, compute, a current time, a time range, and/or a relative time of a request related to simulated objects/environments.
The timing module 406 can include a local clock, timer, or a connection to a remote time server to determine time. The timing module 406 can be implemented via any known and/or convenient manner including but not limited to, electronic oscillator, clock oscillator, or various types of crystal oscillators. According to some embodiments, the timing module 406 can provide time data which may be used to assist identification, recognition or detection by the mobile device 402 of the merchandise object. Examples that the mobile device 402 can consider include the time of day of a request, the date of the request, a relative time to another event, the time of year of the request, and/or the time span of a request or activity pertaining to merchandise objects.
One embodiment of the mobile device 402 includes a radio frequency (RF) or other types of wireless sensor 407. The RF sensor 407 can be any combination of software agents and/or hardware modules able to detect or identify an RF identification chip or other similar wireless identification tags.
One embodiment of the mobile device 402 includes a location sensor 408. The location sensor 408 can be any combination of software agents and/or hardware modules able to identify, detect, transmit, compute, a current location, a previous location, a range of locations, a location at or in a certain time period, and/or a relative location of the mobile device 402. The location sensor 408 can include a local sensor (e.g., GPS sensor) or a connection to an external entity (e.g., a base station) to determine the location information. The location sensor 408 can determine location or relative location of the mobile device 402 via any known or convenient manner including but not limited to, GPS, cell phone tower triangulation, mesh network triangulation, relative distance from another location or device, RF signals, RF fields, optical range finders or grids, etc. The location sensor 408 can identify location data and determine whether the location data satisfies the location parameter of a certain criteria. In some embodiments, the location sensor 408 provides location data to the host server (e.g., host server 324 of
One embodiment of the mobile device 402 includes a camera or an image sensor 409. The image sensor 409 can be any combination of software agents and/or hardware modules able to record or capture still images such as photographs or moving images such as video clips or movies.
It is noted that a person having ordinary skills in the art will understand that sensor modules 407-409 are exemplary, as the mobile device 402 can include other sensors 410 including, for example, accelerometers, gyroscopic gauges, proximity sensors, light sensors, microphones, temperature sensors, heart beat sensors, touch sensitive sensors including touch-screens, fingerprint sensors, and so forth.
The mobile device 402 utilizes suitable sensors to detect presence of the physical product or the real life service in the augmented reality environment or platform. In some embodiments, the mobile device automatically identifies or detects the product(s) or service(s) that falls within a perspective of the user, that is, being viewed/looked at/seen by the user. The product is recognized/identified/detected by using one of several mechanisms as employed by the object identifier module 412, and by querying the merchandise object repository 431.
More specifically, mobile device 402 includes the object identifier module 412. The object identifier module 412 can be any combination of software agents and/or hardware modules able to identify, detect, and/or recognize, merchandise objects for presentation to a user. The object identifier module 412, in one embodiment, is coupled to the timing module 406, the RF sensor 407, the location sensor 408, the image sensor 409, and/or other sensors 410. The identifier module 412 can also receive data signals from the motion/gesture sensor 418, the user stimulus sensor 416, the environmental stimulus sensor 420, and is coupled to the merchandise object repository 431 via the network interface 404. The object identifier module 412 is operable to identify the merchandise objects available for access using the device 402.
In some embodiments, the presence of the product is detected or identified in the augmented reality environment by a shape or other physical characteristics for presentation via the mobile device to facilitate transactions. For example, the product or service can have an unique combination of shape, size, color, or other physical dimension or characteristics (as registered in the merchandise object repository 431) so that the object identifier module 412 can recognize it. Such shape or physical characteristics can be detected from, for example, the image sensor 409. As previously mentioned, the entries in the repository 431 can also include recognition patterns or photos or videos or metadata that may help identifying the product.
In some embodiments, the presence of the product or service is detected or identified in the augmented reality environment by a geographic location of the product or service. For example, the location of the mobile device 402 can assist in identifying (e.g., by pinpointing or ruling out) certain product or service that is only available in that location. Such location data can be detected from, for example, the location sensor 408.
In some embodiments, the presence of the product is detected or identified in the augmented reality environment by one or more of: (i) a visual marker; (ii) a marker or tag; (iii) a one-dimensional barcode; or (iv) a multi-dimensional barcode, on the product. For example, a marker on the object such as a QR code or other augmented reality marker can be presented for identification or detection (e.g., via the image sensor 409). In another example, a barcode representing a stock-keeping unit number (SKU) may be present. The barcode can be one-dimensional or multi-dimensional.
In some embodiments, the presence of the product is detected or identified in the augmented reality environment by a radio frequency identification (RFID) chip coupled to the product. For example, the RFID chip can be embedded in the product, or on a label attached to the product, or attached on a surface or a nearby location of the product. The RFID chip can be detected and read, for example, via the RF sensor/RFID reader 407.
In some embodiments, the presence of the product is detected or identified in the augmented reality environment by optical character recognition (OCR) of written materials on or nearby the product. For example, the image sensor 409 can capture text on labels or other marketing materials on or near the product, and the object identifier module 412 can use well-known OCR techniques to convert the written materials into text for identification (e.g., via a search using the search engine 322 to search merchandise repositories 332, 431).
Further, as an additional or an alternative embodiment, the object identifier module 412 can receive input from the user to disambiguate an identity of the product or service. For example, the user's input can include at least partially a name of the product or service. The user can be prompted to name the product in assisting the disambiguation process proactively or interactively. Such user input can be received from, for example, the motion/gesture sensor 418 or the user stimulus sensor 416.
Some embodiments of the object identifier module 412 can also receive advisory data associated with the product or service to assist the identifying/recognizing/detecting the product or service. The advisory data being added by another user of the augmented reality environment, or by an administrator or merchant of the augmented reality marketplace. The advisory data can include one or more of: (i) metadata or tags relevant to the product or service, or (ii) an annotation that is descriptive of the product or service. The metadata about the product can be added by another previous user who already identified the product, and/or tagged the product at the location that the mobile device 402 is currently situated.
After identifying/detecting/recognizing merchandise objects, external actions can be performed by the user in the real world to interact with the detected merchandise objects. In one embodiment, such actions or requests from the user to perform a requested action on a merchandise object can be received by the user stimulus sensor 416. In one embodiment, the motion/gesture sensor 418 is operable to detect motion of the device 402. The detected motion is used by the user selection module 414 to perform actions responsive to the presented information according to the detected motion of the device. Motion detecting can include detecting velocity and/or acceleration of the device 402 or a gesture of the user handling the device 402. The motion/gesture sensor 418 can include for example, an accelerometer.
More specifically, with the merchandise object(s) identified, the mobile device 402 can present (e.g., using the user selection module 414 and/or audio/video output module 422) information relevant to the merchandise product or service to the user so that the user can initiate various actions responsive to the presented information, for example, initiating the transaction of the product or service via the mobile device 402. Other example actions can include, for example, get price, compare price, read reviews, get availability, add to shopping cart, call a sales representative (e.g., a local sales person or a virtual one) for assistance, buy the product, tag the product or add metadata for the product, share the product with another user, or bookmark the product for later consideration. The relevant information, including transaction information, can be transmitted from the repository 431, which may be local or may be hosted by an online server (e.g., host server 324,224, which may also include or be coupled to e-commerce server 213) that enables electronic commerce.
In some embodiments, a user interface generator in the user selection module 414 can be used to create buttons/links/etc. that are selectable by the user. The interactions or actions from the user can be detected or determined using the user selection module 414 (e.g., via interpreting signals generated from the motion/gesture sensor 418, user stimulus sensor 416, and/or the environmental stimulus sensor 420).
Any response to the user's selection or action can be reflected (e.g., highlighting a selected merchandise, blinking of a selected button, displaying an annotation or review by another user, or displaying a short video clip of the selected merchandise) in the augmented reality environment via the audio/video output module 422.
In some embodiments, the information is rendered translucently and disposed adjacently or partially overlaid with the product or service depicted in the augmented reality environment on the mobile device 402. In some embodiments, the information includes advisory data associated with the product or service. Examples of advisory data can include metadata or tags that are deemed (either automatically by the object identifier module 412, or by another user, or by a merchant or an administrator) relevant to the product or service, or (ii) an annotation that is descriptive of the product or service.
The mobile device 402 can also prompt the user to enter an advisory data for the product or service by, for example, operating a virtual keyboard using the user stimulus sensor 416 and/or motion/gesture sensor 418. Then, the user can select to share (e.g., via network interface 404) the entry to another user of the augmented reality environment.
The content of the interactions can also be decided based on environmental factors including, for example, physical location of the user and/or the merchandise, user action, user feedback/annotation/review/tags/etc. as provided by the user of the device 402 or another user of the augmented reality platform using another device and/or at another physical location, motion/movement of the device 402, gesture of the user using the device 402.
In some embodiments, an advertisement relevant to the product or service can be identified and displayed in the augmented reality environment via the mobile device 402. The advertisement is identified or detected based on one or more of: (i) location, (ii) time, (iii) interest or profile of a user of the mobile device 402. For example, the environmental stimulus sensor 420 can detect environmental factors or changes in environmental factors surrounding the real environment in which the device 402 is located, and the advertisement can be provided based on these factors or changes. Environmental factors can include, weather, temperature, topographical characters, density, surrounding businesses, buildings, living objects, etc. These factors or changes in them can also affect the positioning and/or characters of the presented information for the merchandise objects in the augmented reality in which they are presented to a user via the device 402.
In some embodiments, the advertisement is identified or detected based on a pointing direction of the mobile device 402. In some embodiments, the advertisement is identified or detected based on velocity or speed of movement of the mobile device, or based on an ambient temperature in which the mobile device physically resides, or based on a plurality of sensors (e.g., sensors 407-410) on the mobile device 402. Further, the advertisement is identified or detected (e.g., by a combined reading and interpretation of data signals from the location sensor 408, the image sensor 409, and a directional sensor which may be included among other sensors 410) based on a landmark which the mobile device is pointed at or in a vicinity of.
In some embodiments, the information includes a contact information of a sales representative of the product or service, and the mobile device 402 prompts the user to contact the sale representative based on the contact information.
Additionally, in some embodiments, the mobile device 402 allows the user to bookmark the product or service, and in some embodiments, the mobile device 402 allows the user to share the bookmark with another user of the augmented reality environment.
According to some additional or alternative embodiments, the mobile device 402, in providing the augmented reality environment, can enable the user to select a physical product or service that is in the augmented reality. The mobile device 402 can detect one or more targets in the augmented reality platform using a select area on a perspective of a user. The perspective can be captured, for example, by a camera of the mobile device 402. After the targets are detected, the mobile device 402 prompts the user to choose an object of interest from the one or more detected targets.
More specifically, the mobile device 402 can detect one or more targets in the augmented reality platform using a select area in a perspective of a user, and prompt the user to choose an object of interest from the one or more detected targets. As previously mentioned, the perspective can be captured by the mobile device 402 (e.g., via the image sensor 409. For example, just as a user using a mouse to select items on a personal computer's screen, some embodiments disclosed herein enable selection of real and/or virtual items in an augmented reality environment/platform/marketplace, which in turn enables actions to be taken in relation to the selected items (e.g., the aforementioned transactions of or interactions with the merchandise objects).
The detection of targets can be performed, for example, by object identifier module 412 of the mobile device 402. According to some embodiments, the detection of targets in the augmented reality environment can be performed by pointing the device 402 at the target(s). In some embodiments, the detection of targets can be performed by moving a pointer or a select area on the display of the device 402 to point at or frame the object in a reticle or a circular or rectangular frame (e.g., select area 520, 525, described below with respect to
In some instances, for example, when target is not recognized automatically or when the user so desires, the mobile device 402 can prompt the user, or the user can select, to enter a learning mode in which the mobile device 402 can receive assistance from the user to perform the detection or recognition of the target. The assistance can include one or more of (i) entering at least partially a name, (ii) entering metadata, (iii) defining a boundary via a pointer, or (iv) taking snapshots from a plurality of views to develop a recognition pattern, for a respective target. For example, the teaching can be done by aiming at the target or circling around the target with the interface (e.g., using the select area or the lasso tool, provided by the interface generator module in the user selection module 414) on the device 402, and then by selecting a “learn” function or button on the interface in the augmented reality environment. Then, the mobile device 402 can ask the user for a name or other metadata for the target, and may ask for assistance in defining the boundaries of the object (e.g., via the lasso tool). The device 402 can also ask the user to take a series of snapshot views (e.g., via camera or image sensor 409) of the target to develop a pattern recognition database for it, as well as potentially a series of tests to improve recognition.
After targets are recognized, they can then be selected by the user for actions or interactions. The mobile device 402 can receive the user's choice of the object of interest by detecting movement and selection by a selection tool or a pointer, or movement and selection represented by a gesture (e.g., via the motion/gesture sensor 418, user stimulus sensor 416, and/or hand/finger/other gestures captured by the image sensor 409).
More specifically, in detecting the user's gesture to move a pointer or targeting or selection tool, and/or to select an object, the mobile device 402 can perform capturing, via its various sensors, the gesture from one or more of: (i) movements or non-movements of an eye of the user, (ii) locations of a focal point of an eye of the user, or (iii) movements of an eye lid of the user. Additionally, the mobile device 402 can capture the gesture from one or more of: (i) movements of hand or finger as recognized by a camera of the mobile device, (ii) movements of a virtual pointer controlled by a wireless peripheral device, (iv) movements of a virtual pointer controlled by a touch-sensitive display of the mobile device, (v) movements of the mobile device itself, or (vi) movements of the user's head, limbs, or torso. The capturing can be further based on a speed or velocity of the movements. As such, in light of the above, the present embodiments can capture or identify gestures from, for example, winking of the user and/or an eye focus or eye foci of the user. Another example of gesture controlling can include finger or arm gesturing as captured by camera and/or distance detector/proximity detectors, so that the user can perform “spatial” or “virtual” gesturing in the air or other detectable spaces with similar gestures as those well-known gestures applicable to a mobile phone's touch screen. Yet another example of gesture controlling can include eye ball motion tracking and/or eye focal point tracking. In this way, the user of mobile device 402 may operate various selection mechanisms, for example, using his or her eyes (e.g., via eye movement tracking) or by moving his or her hands/arms/fingers in the perspective to make specific gestures such as pointing or tracing the outline of some object, or by operating a virtual pointer in the scene using a handheld peripheral such as a wireless pointing device or a mouse equivalent, or by touching a touch-sensitive display on a mobile device and gesturing on it to indicate actions and selections, or by moving the device itself with specific gestures and velocities to use the device as a pointer or selection tool. Additional gestures may include eye tracking and determining a focus of the eye for targeting things, and/or blinking to select a target that is in the focal point, to take a photo, or to select a button, etc.
After receiving the user's selection or choice of the object of interest, the mobile device 402 can optionally confirm with the user of the choice of the object of interest. The confirmation can include highlighting or outlining the target in the augmented reality platform by employing, for example, the audio/video output module 422.
In one embodiment, mobile device 402 includes a network interface 432, a processing unit 434, a memory unit 436, a storage unit 438, a location sensor 440, an accelerometer/motion sensor 442, an audio output unit/speakers 446, a display unit 450, an image capture unit 452, a pointing device/sensor 454, a input device 456, and/or a touch screen sensor 458. Additional or less units or modules may be included. The mobile device 402 can be any combination of hardware components and/or software agents for that presenting information with respect to merchandise objects to a user and facilitating user interactions with the merchandise objects. The network interface 432 has been described in the example of
One embodiment of the mobile device 402 further includes a processing unit 434. The location sensor 440, accelerometer/motion sensor 442, and timer 444 have been described with reference to the example of
The processing unit 434 can include one or more processors, CPUs, microcontrollers, FPGAs, ASICs, DSPs, or any combination of the above. Data that is input to the mobile device 402 for example, via the image capture unit 452, pointing device/sensor 554, input device 456 (e.g., keyboard), and/or the touch screen sensor 458 can be processed by the processing unit 434 and output to the display unit 450, audio output unit/speakers 446 and/or output via a wired or wireless connection to an external device, such as a host or server computer that generates and controls access to simulated objects by way of a communications component.
One embodiment of the mobile device 402 further includes a memory unit 436 and a storage unit 438. The memory unit 436 and a storage unit 438 are, in some embodiments, coupled to the processing unit 434. The memory unit can include volatile and/or non-volatile memory. In generating and controlling access to the simulated objects, the processing unit 434 may perform one or more processes related to presenting information with respect to merchandise objects to a user and/or facilitating user interactions with the merchandise objects based on the presented information.
In some embodiments, any portion of or all of the functions described of the various example modules in the mobile device 402 of the example of
With the embodiments disclosed herein, for example, when the user is doing “window shopping,” that is, when the user is looking at a merchandise product in a store window, or on a shelf, or when the user is near a physical store, the user can utilize the mobile devices 502A, 502B to access information 504A, 504B regarding the identified/detected/recognized merchandise objects. The merchandise objects can be selected using select areas 520, 525 in ways that are discussed above. Then, the user can select to perform actions 506 (including transactions) to the merchandise objects in ways that are discussed above. Thus, for example, through the perspective interface 510, 515 in the augmented reality environment, the user can get price of, add comments/annotations/tags for, read reviews of, get availability of, or select to purchase the selected merchandise object. The objects can be identified by ways discussed above including, for example, a barcode 508 attached to the merchandise object. Written materials for identifying objects and/or other relevant information (such as sales event information 530 as illustrated in
Other example augmented information can be provided to the user to inform the user if the store is now open, what is on sale now, etc. Similarly, other sales information including advertisement, video clips, images, or sales representative's contact information can be presented or otherwise made accessible to the user. The information can also include entries from other users of the augmented reality, including but not limited to, their names and profiles, recent blog or microblog posts, recent photos or videos or links or documents added or annotated by them, their recent locations, their professions, etc.
As aforementioned, augmented reality environment 520 reflects a perspective of the user as captured by the mobile device 502 (e.g., via a camera of the device 502). As such, the display and movement of the object 522 in the augmented reality environment 520 corresponds to the display and movement of the physical object 526 (e.g., car) in the real world 524.
In augmented reality environment 502, relevant information regarding the physical object 526 can be rendered or presented with the object 522 so as to “augment” the object 522. Such information or data can be about the people or entities that are in or near a particular geographical location. Further, the mobile device 502 can facilitate transactions of the real physical product or service 526 based on the information, so that transactions can be conducted by users via devices when the user is physically near or at the physical product or the real life service.
First, a mobile device (e.g., devices 102A-102N,
Then, the mobile device 102,402, 502 can query a merchandise object repository (e.g., repository 132,
Next, in some embodiments, the mobile device 102,402, 502 can receive (630) input from the user to disambiguate an identity of the product or service. Further, in some embodiments, the mobile device 102,402, 502 can receive (640) advisory data associated with the product or service. The advisory data can be added, for example, by another user of the augmented reality environment.
After the information is presented, the mobile device 102,402, 502 can initiate (650) the transaction of the product or service via the mobile device based on responses to the presented information (e.g., as detected via various sensors 406-410, 416,418,420 of device 402 and determined by the user selection module 414,
First, a mobile device (e.g., devices 102A-102N,
After detecting the targets, the mobile device 102,402, 502 prompts (720) the user to choose an object of interest from the one or more detected targets. Then, the mobile device 102,402,502 receives (730) the user's choice of the object of interest (e.g., via motion/gesture sensor 418, user stimulus sensor 416, and/or other gestures captured by image sensor 409, as determined by the user selection module 414,
In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in a client-server network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.
The machine may be a server computer, a client computer, a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
While the machine-readable medium is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present disclosure.
In general, the routines executed to implement the embodiments of the disclosure, may be implemented as part of an operating system or a specific application, component, program, object, module or sequence of instructions referred to as “computer programs.” The computer programs typically comprise one or more instructions set at various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause the computer to perform operations to execute elements involving the various aspects of the disclosure.
Moreover, while embodiments have been described in the context of fully functioning computers and computer systems, those skilled in the art will appreciate that the various embodiments are capable of being distributed as a program product in a variety of forms, and that the disclosure applies equally regardless of the particular type of machine or computer-readable media used to actually effect the distribution.
Further examples of machine or computer-readable media include but are not limited to recordable type media such as volatile and non-volatile memory devices, floppy and other removable disks, hard disk drives, optical disks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital Versatile Disks, (DVDs), etc.), among others, and transmission type media such as digital and analog communication links.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense, as opposed to an exclusive or exhaustive sense; that is to say, in the sense of “including, but not limited to.” As used herein, the terms “connected,” “coupled,” or any variant thereof, means any connection or coupling, either direct or indirect, between two or more elements; the coupling of connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The above detailed description of embodiments of the disclosure is not intended to be exhaustive or to limit the teachings to the precise form disclosed above. While specific embodiments of, and examples for, the disclosure are described above for illustrative purposes, various equivalent modifications are possible within the scope of the disclosure, as those skilled in the relevant art will recognize. For example, while processes or blocks are presented in a given order, alternative embodiments may perform routines having steps, or employ systems having blocks, in a different order, and some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or subcombinations. Each of these processes or blocks may be implemented in a variety of different ways. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples: alternative implementations may employ differing values or ranges.
The teachings of the disclosure provided herein can be applied to other systems, not necessarily the system described above. The elements and acts of the various embodiments described above can be combined to provide further embodiments.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the disclosure can be modified, if necessary, to employ the systems, functions, and concepts of the various references described above to provide yet further embodiments of the disclosure.
These and other changes can be made to the disclosure in light of the above Detailed Description. While the above description describes certain embodiments of the disclosure, and describes the best mode contemplated, no matter how detailed the above appears in text, the teachings can be practiced in many ways. Details of the system may vary considerably in its implementation details, while still being encompassed by the subject matter disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the disclosure should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the disclosure with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the disclosure to the specific embodiments disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the disclosure encompasses not only the disclosed embodiments, but also all equivalent ways of practicing or implementing the disclosure under the claims.
While certain aspects of the disclosure are presented below in certain claim forms, the inventors contemplate the various aspects of the disclosure in any number of claim forms. For example, while only one aspect of the disclosure is recited as a means-plus-function claim under 35 U.S.C. § 112, 6, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. § 112, 6 begins with the words “means for”.) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the disclosure.
This application is a continuation application of prior application Ser. No. 16/543,011, filed on Aug. 16, 2019, which is a continuation application of prior application Ser. No. 14/939,889, filed on Nov. 12, 2015, which has issued as U.S. Pat. No. 10,388,070 on Aug. 20, 2019, which is continuation of prior application Ser. No. 13/874,421, filed on Apr. 30, 2013, which was based on and claimed priority under 35 U.S.C. § 119(e) of a U.S. Provisional application Ser. No. 61/640,856, filed on May 1, 2012, in the U.S. Patent and Trademark Office, the disclosure of which is incorporated by reference herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4519490 | White | May 1985 | A |
| 4829899 | Wiker et al. | May 1989 | A |
| 5009598 | Bennington | Apr 1991 | A |
| 5450590 | Elko et al. | Sep 1995 | A |
| 5600777 | Wang et al. | Feb 1997 | A |
| 5604907 | Conner et al. | Feb 1997 | A |
| 5616030 | Watson | Apr 1997 | A |
| 5623657 | Conner et al. | Apr 1997 | A |
| 6023270 | Brush, II et al. | Feb 2000 | A |
| 6028593 | Rosenberg et al. | Feb 2000 | A |
| 6050898 | Vange et al. | Apr 2000 | A |
| 6080063 | Khosla | Jun 2000 | A |
| 6241609 | Rutgers | Jun 2001 | B1 |
| 6292798 | Dockter et al. | Sep 2001 | B1 |
| 6302941 | Oya et al. | Oct 2001 | B1 |
| 6314167 | Johnson et al. | Nov 2001 | B1 |
| 6549893 | Lannert et al. | Apr 2003 | B1 |
| 6572380 | Buckley et al. | Jun 2003 | B1 |
| 6680909 | Bansal et al. | Jan 2004 | B1 |
| 6842175 | Schmalstieg et al. | Jan 2005 | B1 |
| 6983232 | Nguyen et al. | Jan 2006 | B2 |
| 7054848 | Lannert et al. | May 2006 | B1 |
| 7065553 | Chesley et al. | Jun 2006 | B1 |
| 7072919 | Sexton et al. | Jul 2006 | B2 |
| 7155496 | Froyd et al. | Dec 2006 | B2 |
| 7349840 | Budzinski | Mar 2008 | B2 |
| 7353160 | Voigt | Apr 2008 | B2 |
| 7487177 | Kilian-Kehr et al. | Feb 2009 | B2 |
| 7516052 | Hatcherson et al. | Apr 2009 | B2 |
| 7543238 | Alcazar et al. | Jun 2009 | B2 |
| 7545225 | Beccue | Jun 2009 | B2 |
| 7570261 | Edecker et al. | Aug 2009 | B1 |
| 7685508 | Froyd et al. | Mar 2010 | B2 |
| 7702693 | Aiyagari et al. | Apr 2010 | B1 |
| 7739479 | Bordes et al. | Jun 2010 | B2 |
| 7797168 | Kusumoto et al. | Sep 2010 | B2 |
| 7824268 | Harvey et al. | Nov 2010 | B2 |
| 7859551 | Bulman et al. | Dec 2010 | B2 |
| 7890419 | Jung et al. | Feb 2011 | B2 |
| 7955168 | Mendelsohn et al. | Jun 2011 | B2 |
| 7991706 | Mattern | Aug 2011 | B2 |
| 7996264 | Kusumoto et al. | Aug 2011 | B2 |
| 8046338 | Basso et al. | Oct 2011 | B2 |
| 8138930 | Heath et al. | Mar 2012 | B1 |
| 8181152 | Choi et al. | May 2012 | B2 |
| 8191121 | Ruppert et al. | May 2012 | B2 |
| 8192283 | Ruppert et al. | Jun 2012 | B2 |
| 8201229 | Ruppert et al. | Jun 2012 | B2 |
| 8205092 | Stokes | Jun 2012 | B2 |
| 8246467 | Huang et al. | Aug 2012 | B2 |
| 8279862 | Sbisa et al. | Oct 2012 | B2 |
| 8287383 | Etter et al. | Oct 2012 | B1 |
| 8303387 | Spivack | Nov 2012 | B2 |
| 8307273 | Pea et al. | Nov 2012 | B2 |
| 8494498 | Kwon | Jul 2013 | B2 |
| 8532340 | Kruglick | Sep 2013 | B2 |
| 8566786 | Choi et al. | Oct 2013 | B2 |
| 8610771 | Leung et al. | Dec 2013 | B2 |
| 8630620 | Cha et al. | Jan 2014 | B2 |
| 8660679 | Kurabayashi et al. | Feb 2014 | B2 |
| 8682879 | Kim et al. | Mar 2014 | B2 |
| 8719077 | Titus et al. | May 2014 | B2 |
| 8732025 | Gokturk et al. | May 2014 | B2 |
| 8745494 | Spivack | Jun 2014 | B2 |
| 8805110 | Rhoads et al. | Aug 2014 | B2 |
| 8866847 | Bedi et al. | Oct 2014 | B2 |
| 8947455 | Friesen | Feb 2015 | B2 |
| 8947456 | Chen et al. | Feb 2015 | B2 |
| 8957835 | Hoellwarth et al. | Feb 2015 | B2 |
| 9001252 | Hannaford | Apr 2015 | B2 |
| 9031809 | Kumar et al. | May 2015 | B1 |
| 9047700 | Ur | Jun 2015 | B2 |
| 9077771 | Kruglick | Jul 2015 | B2 |
| 9105207 | Leung | Aug 2015 | B2 |
| 9196094 | Ur | Nov 2015 | B2 |
| 9215530 | Kurabayashi et al. | Dec 2015 | B2 |
| 9257089 | Ur | Feb 2016 | B2 |
| 9280853 | Ur | Mar 2016 | B2 |
| 9390503 | Leung et al. | Jul 2016 | B2 |
| 9486707 | Kruglick | Nov 2016 | B2 |
| 11170286 | Dolignon | Nov 2021 | B2 |
| 20010053968 | Galitsky et al. | Dec 2001 | A1 |
| 20020010734 | Ebersole et al. | Jan 2002 | A1 |
| 20020029298 | Wilson | Mar 2002 | A1 |
| 20020133325 | Hoare, II et al. | Sep 2002 | A1 |
| 20020184516 | Hale et al. | Dec 2002 | A1 |
| 20030064712 | Gaston et al. | Apr 2003 | A1 |
| 20030217122 | Roese et al. | Nov 2003 | A1 |
| 20030221022 | Sexton et al. | Nov 2003 | A1 |
| 20030224855 | Cunningham | Dec 2003 | A1 |
| 20040002843 | Robarts et al. | Jan 2004 | A1 |
| 20040027258 | Pechatnikov et al. | Feb 2004 | A1 |
| 20040053686 | Pacey et al. | Mar 2004 | A1 |
| 20040095311 | Tarlton et al. | May 2004 | A1 |
| 20040158455 | Spivack et al. | Aug 2004 | A1 |
| 20040248632 | French et al. | Dec 2004 | A1 |
| 20050009608 | Robarts et al. | Jan 2005 | A1 |
| 20050091118 | Fano | Apr 2005 | A1 |
| 20050172018 | Devine et al. | Aug 2005 | A1 |
| 20050246275 | Nelson | Nov 2005 | A1 |
| 20050267731 | Hatcherson et al. | Dec 2005 | A1 |
| 20050286421 | Janacek | Dec 2005 | A1 |
| 20060092170 | Bathiche et al. | May 2006 | A1 |
| 20060189386 | Rosenberg | Aug 2006 | A1 |
| 20060192852 | Rosenthal et al. | Aug 2006 | A1 |
| 20060223635 | Rosenberg | Oct 2006 | A1 |
| 20060230073 | Gopalakrishnan | Oct 2006 | A1 |
| 20060235674 | Voigt | Oct 2006 | A1 |
| 20060287815 | Gluck | Dec 2006 | A1 |
| 20060293110 | Mendelsohn | Dec 2006 | A1 |
| 20070024644 | Bailey | Feb 2007 | A1 |
| 20070097832 | Koivisto et al. | May 2007 | A1 |
| 20070117576 | Huston | May 2007 | A1 |
| 20070214449 | Choi et al. | Sep 2007 | A1 |
| 20070223675 | Surin et al. | Sep 2007 | A1 |
| 20070265089 | Robarts et al. | Nov 2007 | A1 |
| 20070299559 | Janssen et al. | Dec 2007 | A1 |
| 20080026838 | Dunstan et al. | Jan 2008 | A1 |
| 20080031234 | Sbisa et al. | Feb 2008 | A1 |
| 20080036653 | Huston | Feb 2008 | A1 |
| 20080070696 | Kim et al. | Mar 2008 | A1 |
| 20080133189 | Criswell et al. | Jun 2008 | A1 |
| 20080146342 | Harvey et al. | Jun 2008 | A1 |
| 20080162498 | Omoigui | Jul 2008 | A1 |
| 20080162707 | Beck et al. | Jul 2008 | A1 |
| 20080177650 | Jung et al. | Jul 2008 | A1 |
| 20080182592 | Cha et al. | Jul 2008 | A1 |
| 20080184138 | Krzanowski et al. | Jul 2008 | A1 |
| 20080189360 | Kiley et al. | Aug 2008 | A1 |
| 20080220397 | Capone et al. | Sep 2008 | A1 |
| 20080247636 | Davis et al. | Oct 2008 | A1 |
| 20080261564 | Logan | Oct 2008 | A1 |
| 20080320419 | Matas et al. | Dec 2008 | A1 |
| 20090005018 | Forstall et al. | Jan 2009 | A1 |
| 20090005140 | Rose et al. | Jan 2009 | A1 |
| 20090005167 | Arrasvuori et al. | Jan 2009 | A1 |
| 20090007229 | Stokes | Jan 2009 | A1 |
| 20090024629 | Miyauchi | Jan 2009 | A1 |
| 20090036186 | Benco et al. | Feb 2009 | A1 |
| 20090061901 | Arrasvuori et al. | Mar 2009 | A1 |
| 20090061974 | Lutnick et al. | Mar 2009 | A1 |
| 20090069033 | Karstens et al. | Mar 2009 | A1 |
| 20090089825 | Coldwell | Apr 2009 | A1 |
| 20090102616 | Stone et al. | Apr 2009 | A1 |
| 20090125823 | Moll et al. | May 2009 | A1 |
| 20090150802 | Do et al. | Jun 2009 | A1 |
| 20090199302 | So et al. | Aug 2009 | A1 |
| 20090237546 | Bloebaum et al. | Sep 2009 | A1 |
| 20090265257 | Klinger et al. | Oct 2009 | A1 |
| 20090291750 | Herrmann | Nov 2009 | A1 |
| 20090293011 | Nassar | Nov 2009 | A1 |
| 20090304283 | Predovic et al. | Dec 2009 | A1 |
| 20100017820 | Thevathasan et al. | Jan 2010 | A1 |
| 20100050100 | Dettinger et al. | Feb 2010 | A1 |
| 20100125362 | Canora et al. | May 2010 | A1 |
| 20100199193 | Hamilton, II et al. | Aug 2010 | A1 |
| 20100217573 | Hatcherson et al. | Aug 2010 | A1 |
| 20100260426 | Huang | Oct 2010 | A1 |
| 20100302143 | Spivack | Dec 2010 | A1 |
| 20100304804 | Spivack | Dec 2010 | A1 |
| 20100331041 | Liao et al. | Dec 2010 | A1 |
| 20110055049 | Harper et al. | Mar 2011 | A1 |
| 20110138317 | Kang et al. | Jun 2011 | A1 |
| 20110184972 | Ard et al. | Jul 2011 | A1 |
| 20110213664 | Osterhout et al. | Sep 2011 | A1 |
| 20110214082 | Osterhout et al. | Sep 2011 | A1 |
| 20110225069 | Cramer et al. | Sep 2011 | A1 |
| 20110310227 | Konertz et al. | Dec 2011 | A1 |
| 20120011142 | Baheti et al. | Jan 2012 | A1 |
| 20120038670 | Choi et al. | Feb 2012 | A1 |
| 20120050324 | Jeong et al. | Mar 2012 | A1 |
| 20120062596 | Bedi et al. | Mar 2012 | A1 |
| 20120095853 | Von Bose et al. | Apr 2012 | A1 |
| 20120143361 | Kurabayashi et al. | Jun 2012 | A1 |
| 20120174062 | Choi et al. | Jul 2012 | A1 |
| 20120230538 | Calman et al. | Sep 2012 | A1 |
| 20120239469 | Steinberg et al. | Sep 2012 | A1 |
| 20120249586 | Wither et al. | Oct 2012 | A1 |
| 20120253825 | Di Fabbrizio et al. | Oct 2012 | A1 |
| 20120323938 | Skeen et al. | Dec 2012 | A1 |
| 20120326966 | Rauber | Dec 2012 | A1 |
| 20130030903 | Spivack | Jan 2013 | A1 |
| 20130033522 | Calman et al. | Feb 2013 | A1 |
| 20130042296 | Hastings et al. | Feb 2013 | A1 |
| 20130050258 | Liu et al. | Feb 2013 | A1 |
| 20130147836 | Small | Jun 2013 | A1 |
| 20130147837 | Stroila | Jun 2013 | A1 |
| 20130155105 | Boldyrev et al. | Jun 2013 | A1 |
| 20130174268 | Wang et al. | Jul 2013 | A1 |
| 20130179303 | Petrou et al. | Jul 2013 | A1 |
| 20130239019 | Pike et al. | Sep 2013 | A1 |
| 20130293580 | Spivack | Nov 2013 | A1 |
| 20130297460 | Spivack | Nov 2013 | A1 |
| 20140009494 | Kasahara | Jan 2014 | A1 |
| 20140222558 | Spivack | Aug 2014 | A1 |
| 20140306866 | Miller et al. | Oct 2014 | A1 |
| 20150015459 | Cho et al. | Jan 2015 | A1 |
| 20150302517 | Spivack | Oct 2015 | A1 |
| 20150350223 | Spivack | Dec 2015 | A1 |
| 20150367233 | Hicks et al. | Dec 2015 | A1 |
| 20160071326 | Spivack | Mar 2016 | A1 |
| 20160299569 | Fisher et al. | Oct 2016 | A1 |
| 20190102946 | Spivack | Apr 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 926 614 | Jun 1999 | EP |
| 10-2011-0133655 | Dec 2011 | KR |
| 2006024866 | Mar 2006 | WO |
| 2009002879 | Dec 2008 | WO |
| Entry |
|---|
| International Search Report PCT/US2010/035282 dated Feb. 1, 2001; pp. 1-3. |
| Written Opinion PCT/US2010/035282 dated Feb. 1, 2011; pp. 1-6. |
| “Object-Oriented Programming,” as shown in http://en.wikipedia.org/wiki/Object-oriented_programming, dated Apr. 22, 2009, last accessed Nov. 4, 2013; pp. 1-9. |
| Hughes, N., “Apple Envisions Interactive, Augmented Reality iPhone Multiplayer Games,” http://appleinsider.com/articles/10/11/2014, Nov. 4, 2010, 6 pages. |
| Kaiser, E. Mutual disambiguation of 3 D multimodal interaction in augmented and virtual reality, Proceedings of the 5th international conference on multimodal interfaces (ICMI'03: Fifth International Conference on Multimodal Interfaces), pp. 12-19. |
| Number | Date | Country | |
|---|---|---|---|
| 20210104101 A1 | Apr 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61640856 | May 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16543011 | Aug 2019 | US |
| Child | 17101429 | US | |
| Parent | 14939889 | Nov 2015 | US |
| Child | 16543011 | US | |
| Parent | 13874421 | Apr 2013 | US |
| Child | 14939889 | US |
