Patent Grant
10158634
The present disclosure relates generally to performing operations using an augmented reality display device that overlays graphic objects with objects in a real scene.
Remotely executing documents causes several technical challenges. Executing documents remotely may require transferring information across a network, thus creating security risks. Further, transmitting information across a network may cause network bottlenecks. Thus, it is desirable to provide the ability to securely transfer information and resources among users across a network without causing transmission delays or failures.
In one embodiment, an augmented reality system includes a server, a first augmented reality user device for a signor, and a second augmented reality user device for a notary. The server includes a memory operable to store a virtual file folder, the virtual file folder comprising a virtual file document.
The first augmented reality user device for a signor includes a first head-mounted display, a first physical identification verification engine, and a first capture engine. The first head-mounted display overlays the virtual file document onto a tangible object in real-time. The first physical identification verification engine receives biometric data for the signor. The first physical identification verification engine confirms the signor's identity by comparing the received biometric data for the signor to predetermined biometric data for the signor. The first physical identification verification engine generates a signor identity confirmation token indicating the confirmation of the signor's identity. The first gesture capture engine captures a gesture motion from the signor, the gesture motion representing a signature on the virtual file document. The first gesture capture engine generates a signor digital signature based on the captured gesture from the signor. The first gesture capture engine generates a signor transfer token, the signor transfer token comprising the signor digital signature and the signor identity confirmation token.
A second augmented reality user device includes a second head-mounted display, a second physical identification verification engine, a gesture confirmation engine, and a second gesture capture engine. The second head-mounted display overlays the virtual file document onto a tangible object in real-time. The second physical identification verification engine receives biometric data for the notary and confirms the notary's identity by comparing the received biometric data for the notary to predetermined biometric data for the notary. The second physical identification verification engine generates a notary identity confirmation token indicating the confirmation of the notary's identity. The gesture confirmation engine receives the signor identity confirmation token, communicates the signor identity confirmation token to the notary, and displays, via the head-mounted display, the gesture motion from the signor, the gesture motion from the signor displayed on the virtual file document. The second gesture capture engine captures a gesture motion from the notary, the gesture motion from the notary representing a signature on the virtual file document. The second gesture capture engine generates a notary digital signature based on the captured gesture motion from the notary. The second gesture capture engine generates a notary transfer token, the notary transfer token comprising the notary digital signature based on the captured gesture from the notary and the notary identity confirmation token.
The server further includes an interface and a processor. The interface receives the signor transfer token and the notary transfer token. The processor generates an executed document using the signor transfer token, the notary transfer token, and the virtual file document and stores the executed document in the virtual file folder.
In another embodiment, the disclosure includes an augmented reality user device that includes a head-mounted display, a physical identification verification engine, a gesture confirmation engine, and an interface. The head-mounted display overlays a virtual file document onto a tangible object in real-time. The physical identification verification engine receives biometric data for a witness and confirms the witness's identity by comparing the received biometric data for the witness to predetermined biometric data for the witness. The physical identification verification engine generates a witness identity confirmation token indicating the confirmation of a witness's identity. The gesture confirmation engine receives a signor identity confirmation token and communicates the signor identity confirmation token to the witness. The head-mounted display displays a gesture motion from the signor, the gesture motion from the signor displayed on the virtual file document. The gesture capture engine captures a gesture motion from the witness, the gesture motion from the witness representing a signature on the virtual file document. The gesture capture engine generates a witness digital signature based on the captured gesture motion from the witness. The gesture capture engine generates a witness transfer token, the witness transfer token comprising the witness digital signature based on the captured gesture from the witness and the witness identity confirmation token. The interface communicates the witness transfer token to a server.
The present disclosure presents several technical advantages. In one embodiment, an augmented reality user device employs transfer tokens to allow data transfers to be executed using less information than other existing systems. By using less information to perform data transfers, the augmented reality user device reduces the amount of data that is communicated across the network. Reducing the amount of data that is communicated across the network improves the performance of the network by reducing the amount of time network resource are occupied.
The augmented reality user device generates transfer tokens based on biometric data which improves the performance of the augmented reality user device by reducing the amount of information required to identify a person, authenticate the person, and facilitate a data transfer.
Transfer tokens also provide another technical advantage by allowing a user to make a data transfer without prior knowledge about another user's network or network services by using transfer tokens. Additionally, transfer tokens are encoded or encrypted to obfuscate and mask information being communicated across a network. Masking the information being communicated protects users and their information in the event of unauthorized access to the network and/or data occurs.
Another technical advantage is the augmented reality user device uses a combination of facial recognition, voice recognition, and/or predetermined signal or code to perform a multistep authentication process to authenticate a user's identity prior to making a data transfer. This feature may be particularly useful if a user is vision impaired. The ability for the augmented reality user device to authenticate both the user and another person provides improved information security by controlling whom has access to sensitive information.
Another technical advantage is an augmented reality user device's ability to store details for a transfer and to delay the transfer until conditions for triggering a transfer are satisfied. The augmented reality user device stores details and triggering conditions to provides the user the ability to delay a transfer, for example, when resources are unavailable, without requiring the user to reenter details about the transfer. Also, the augmented reality user device allows transfers to be made automatically or spontaneously when resources are available without requiring the user to preschedule the transfer without knowledge of whether the resources will be available.
Certain embodiments of the present disclosure may include some, all, or none of these advantages. These advantages and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.
For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
Transferring data and information across a network causes several technical challenges. Networks are susceptible to attacks by unauthorized users trying to gain access to sensitive information being communicated across the network. Unauthorized access to a network may compromise the security of the data and information being communicated across the network. One technical solution for improving network security is the generation and usage of transfer tokens that allow a user to send only information that is pertinent to executing a transfer between multiple people. The transfer token may be encoded or encrypted to obfuscate the information being communicated by the transfer token. Using tokens to mask information that is communicated across the network may protect the users and their information in the event unauthorized access to the network and/or data occurs. The transfer tokens also allow for data transfers to be executed using less information than other existing systems, and thereby reduces the amount of data that is communicated across the network. Reducing the amount of data that is communicated across the network may improve the performance of the network by reducing the amount of time network resource are occupied.
Another technical challenge associated with transferring data and information across a network is that people may be a part of different institutions that are members of different networks and/or have access to different types of network services for sharing information and transferring resources with each other. Some networks may not support certain types of network resources which may cause challenges when transferring data and information across different networks. Transfer tokens provide a technical solution by allowing a user to make a transfer without prior knowledge about another user's network or network services by using transfer tokens.
Another technical challenge associated with transferring data and information across a network is the inability to authenticate both parties prior to making a transfer. Existing solutions may allow a user to identify themselves, but do not provide a mechanism that allows the user to identify and authenticate another person. The inability to identify and authenticate another person makes transferring data and information vulnerable to attacks such as identity theft. For example, someone can pose as another person to spoof a user and to request a transfer by the user. A technical solution to identity theft is the integration of one or more mechanisms that allow a user to identify and authenticate another person using verifiable information. For example, using a combination of facial recognition, voice recognition, and predetermined signal or codes allows a user to authenticate a person. The ability for the user to authenticate another user provides improved information security by controlling who access to sensitive information and ensuring that a document is properly executed by the correct parties.
Existing systems for remotely executing documents and verifying signor identity are limited to executing documents at a central geographical location at a specific time. For example, to execute a document before a notary public, a signor must be in the same geographical location as the notary public and both parties must be at the geographical location at the same time. Some existing systems allow a signor to remotely execute a document. However, in these instances, existing systems perform no or inadequate identity verification. Additionally, these systems do not allow parties to view other parties executing the documents in real time or at a later time. Thus, existing systems limit the user ability to accommodate executing documents remotely and transferring data about the document execution.
One technical solution is to provide a system that verifies a signor's identity, allows the user to execute the document remotely, and transfers data that can be used to verify the document execution through a network. For example, an augmented reality user device may verify a signor's identity. The augmented reality user device may virtually display a document for execution by the signor. The signor users the augmented reality user device to express a gesture motion that indicates that the signor executed the document. For example, the signor may perform a signing gesture motion using a stylus and/or a data glove. As another example, a signor may execute the document with a verbal command. The augmented reality user device captures the gesture motion. The augmented reality user device transfers the gesture motion and/or the identify verification via encrypted transfer tokens. A witnesses, such as a notary public, a witness, and/or any other suitable third party, may view the transfer tokens from the signor's augmented reality user device, confirm that the signor execute the document, and execute the document. The witnesses may execute the document in real time (e.g., substantially the same time as the signor) or at a later time. For example, a witness may execute the document in real-time and a notary may execute the document at a later time.
Once each party has executed the document, a server may generate an executed document that includes the original document and transfer tokens from each party that executed the document. For example, the server may combine each transfer token and the document to generate the executed document. In some embodiments, the executed document may include a visual representation of the document and each party's digital signature.
System 100 may be utilized by users 105a-n, where n is any suitable number. Users 105 generally execute documents using AR user device 110. For example, a user 105 may execute virtual file document 120 to facilitate creating executed document 170. User 105 may be any suitable person executing any suitable type of document. For example, users 105 may include a person required to execute a document. As another example, users 105 may include a witness. As yet another example, users 105 may include a notary public. In some embodiments, document 120 may be a document associated with a loan. For example, a first user 105 may request a loan and be required to execute a document 120 to receive the loan. A second user 105 may be a witness. For example, the witness may execute document 120 to indicate confirmation that the first user 105 executed the document. In some embodiments, a third user 105 may be a notary public that also executes document 120.
System 100 comprises AR user devices 110a-n, where n is any suitable number. For example, each user 105 may be associated with an AR user device 110. As yet another example, a plurality of users 105 may each use a single AR user device 110. In the illustrated embodiment, AR user device 110 is configured as a head-mounted wearable device. For example, a wearable device is integrated into an eyeglass structure, a visor structure, a helmet structure, a contact lens, or any other suitable structure. In some embodiments, AR user device 110 may be or may be integrated with a mobile user device. Examples of mobile user devices include, but are not limited to, a mobile phone, a computer, a tablet computer, and a laptop computer. Additional details about AR user device 110 are described in
AR user device 110 is configured to confirm one or more user's 105 identity. AR user device 110 may comprise one or more biometric scanners. For example, AR user device 110 may comprise a retinal scanner, a fingerprint scanner, a voice recorder, and/or a camera. AR user device 110 may comprise any suitable type of device to gather biometric measurements. AR user device 110 uses biometric measurements received from the one or more biometric scanners to confirm a user's 105 identity. For example, AR user device may compare the received biometric measures to predetermined biometric measurements for user 105. In some embodiments, AR user device 110 receives the predetermined biometric measures from biometric database 175. Once AR user device 110 confirms a user's 105 identity. AR user device 110 may generate an identification token 130 that indicates that the user's 105 identity has been confirmed.
Biometric database 175 generally stores biometric data for one or more users 105. For example, biometric database 175 may store biometric measurements for one or more users 105. Biometric measurements may include fingerprint measurements, retinal measurements, voice measurements, and or image measurements such as facial recognition measurements. Biometric database 175 may be a single database or any number of databases.
AR user device 110 is configured to display virtual file document 120. AR user device 110 may create a virtual overlay of virtual file document 120 that may be viewed by one or more users 105. For example, AR user device 110 creates a virtual overlay of virtual file document 120 onto a tangible object in a real scene. AR user device 110 may capture changes made to the virtual file document 120. For example, one or more users 105 may perform a gesture motion, such as signing motion. AR user device 110 may receive the gesture motion and generate digital signature 135 based on the gesture motion that indicates that a user 105 executed the virtual file document 120. AR user device 110 may comprise input devices such as a camera, a stylus, a data glove, and/or any other suitable type of device that may receive input from a user 105. The input device may capture a user's 105 gesture motion. For example, a user 105 may make a signing motion with their hand. As another example, a user 105 may verbally indicate that the user 105 is executing the document. The captured gesture motion is used to generate digital signature 135 that is transmitted to other components of system 100.
Other AR user devices 110 may display the captured gesture motion to one or more other user's 105, allowing other users 105 to view the first user execute virtual file document 120. For example, other AR user devices 110 may display the first user executing virtual file document 120 in real time. As another example, other AR user devices may display a recording of the first user executing virtual file document 120 at a previous time. The other AR user device's 110 may receive digital signature 135 and create a virtual overlay (or any other suitable type of recreation) of the gesture motion. This allows two users 105 to be located in geographically distinct locations and view virtual file document 120, and any changes to the document (such as signatures), in real time. In another embodiment, one or more users 105 may view and modify virtual file document 120 at a first time and one or more other users 105 may view the virtual file document 120 and changes made to the document at a second, later time. For example a first AR user device 110 associated with a first user 105 may record the first user 105 executing virtual file document 120. A second user, such as a notary or witness, may view the recording at a second, later time to confirm that the first user 105 executed virtual file document 120.
In particular embodiments, AR user device 110 generates a transfer token 125. Generally, a transfer token 125 includes both identification token 130 and digital signature 135. Transfer token 125 generally facilitates creating executed document 170. An AR user device 110 may transmit transfer token 125 to other user's 105. Users 105, such as a witness and/or a notary, may view transfer token 125 from a user 105 who is a signor. For example, a witness may utilize transfer token 125 to confirm the signor's identity. The witness may further utilize transfer token to view the signor execute virtual file document 120, either in real-time or at a later time. As another example, an AR user device 110 may transmit transfer token 125 to server 140. Server 140 may use one or more transfer tokens 125 to generate executed document 170. For example, server 140 may store virtual file document 120 and one or more transfer tokens 125 in a single file to generate executed document 170.
Network 115 facilitates communication between and amongst the various components of system 100. This disclosure contemplates network 115 being any suitable network operable to facilitate communication between the components of system 100. Network 115 may include any interconnecting system capable of transmitting audio, video, signals, data, messages, or any combination of the preceding. Network 115 may include all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network, such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof, operable to facilitate communication between the components.
Server 140 generally communicates virtual file document 120 to one or more users 105 and generates executed document 170. As illustrated, server 140 includes memory 140, processor 150, and interface 155. This disclosure contemplates memory 140, processor 150, and interface 155 being configured to perform any of the operations of server 140 described herein. In particular embodiments, server 140 may increase security and decrease network bandwidth bottlenecking associated with remote document execution.
Processor 150 is any electronic circuitry, including, but not limited to microprocessors, application specific integrated circuits (ASIC), application specific instruction set processor (ASIP), and/or state machines, that communicatively couples to memory 140 and interface 155 and controls the operation of server 140. Processor 150 may be 8-bit, 16-bit, 32-bit, 64-bit or of any other suitable architecture. Processor 150 may include an arithmetic logic unit (ALU) for performing arithmetic and logic operations, processor registers that supply operands to the ALU and store the results of ALU operations, and a control unit that fetches instructions from memory 140 and executes them by directing the coordinated operations of the ALU, registers and other components. Processor 150 may include other hardware and software that operates to control and process information. Processor 150 executes software stored on memory 140 to perform any of the functions described herein. Processor 150 controls the operation and administration of server 140 by processing information received from network 115, AR user device(s) 110, and memory 140. Processor 150 may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding. Processor 130 is not limited to a single processing device and may encompass multiple processing devices.
Interface 155 represents any suitable device operable to receive information from network 115, transmit information through network 115, perform suitable processing of the information, communicate to other devices, or any combination of the preceding. For example, interface 155 transmits data to server 140. As another example, interface 155 receives information from AR user devices 110. As a further example, interface 155 receives data from biometric database 175. Interface 155 represents any port or connection, real or virtual, including any suitable hardware and/or software, including protocol conversion and data processing capabilities, to communicate through a LAN, WAN, or other communication systems that allows server 140 to exchange information with AR user devices 110, biometric database 175, and/or other components of system 100 via network 115.
Memory 140 may store, either permanently or temporarily, data, operational software, or other information for processor 150. Memory 140 may include any one or a combination of volatile or non-volatile local or remote devices suitable for storing information. For example, memory 140 may include random access memory (RAM), read only memory (ROM), magnetic storage devices, optical storage devices, or any other suitable information storage device or a combination of these devices. The software represents any suitable set of instructions, logic, or code embodied in a computer-readable storage medium. For example, the software may be embodied in memory 140, a disk, a CD, or a flash drive. In particular embodiments, the software may include an application executable by processor 150 to perform one or more of the functions described herein. In particular embodiments, memory 140 may store virtual file folder 160. This disclosure contemplates memory 135 storing any of the elements stored in biometric database 175, server 140, and/or any other suitable components of system 100. In the illustrated embodiment, memory 140 comprises virtual file folder 160. Virtual file folder 160 may include virtual file document 120, executed document 170, and/or tokens 165.
Generally, server 140 sends virtual file document 120 to one or more AR user devices 110, receives tokens from one or more AR user devices 110, and uses the received tokens to generate executed document 170. For example, server 140 communicates virtual file document to a first user 105a who is a signor and a second user 105b who is a witness. AR user devices 110a and 110b create a virtual overlay of virtual file document 120 for the signor and the witness, respectively. AR user device 110a authenticates the signor's identity and receives a gesture motion from the signor (e.g., a signing motion) to indicate that the signor executed virtual file document 120 as previously discussed. AR user device 110a creates a transfer token 125a that includes identity token 130a and digital signature 135a. AR user device 110b receives transfer token 125a from AR user device 110a. The witness may verify the signor's identity using identification token 130. The witness may utilize transfer token 125a to verify that the witness executed virtual file document 120 (e.g., by viewing the signor execute virtual file document 120). Once the witness verifies the signor's identity and digital signature, AR user device 110b may generate transfer token 125b that includes identification token 130b and digital signature 135b for the witness as previously discussed.
Each AR user device 110 may communicate a transfer token 125 to server 140 where they are stored in memory 160 as tokens 165. Tokens 165 may include one or more identification tokens 130, one or more digital signatures 135, one or more transfer tokens 125, and/or any other suitable type of token. Server 140 utilizes tokens 165 and virtual file document 120 to create executed document 170. Executed document 170 is generally a virtual file document 120 that has been executed by one or more users 150. For example, executed document 170 is a document that is executed by all required users 105. Executed document 170 may include virtual file document 120 and a transfer token 125 for each user 105 that executes virtual file document 120. For example, server 140 may generate a single file comprising virtual file document 120 and one or more tokens 165 to generated executed document 170. As another example, server 140 may extract one or more digital signatures 135 from tokens 165 and overlay the digital signatures 135 onto virtual file document 120 to create executed document 170. Executed document 170 may indicate that all of the required parties to an agreement executed the agreement.
In an exemplary embodiment of operation, a first AR user device 110 confirms a first user's 105 identity and generates a first identification token 130. For example, the first AR user device 110 receives biometric data from the first user 105. The biometric data is compared to predetermined biometric data for the first user 105 to authenticate the first user's 105 identity. The first AR user device receives virtual file document 120 from server 140 and displays virtual file document 120 to the first user 105 by creating a virtual overlay of virtual file document 120 onto a tangible medium. The first user 105 executes the document using a gesture motion, such as a signing motion, that represent a signature on virtual file document 120. The first AR user device 110 captures the gesture motion and uses the gesture motion to generate digital signature 135. The first AR user device generates a first transfer token 125 using the first identification token 130 and the first digital signature 135. The first AR user device 110 transmits the first transfer token 125 to server 140.
In this exemplary embodiment, the first AR user device and/or server 140 may determine whether a second user 105 is available to witness the first user's 105 execution of virtual file document 120 in real time. For example, a witness could be a witness or a notary public. If a second user 105 is available to witness the first user's 105 execution of virtual file document 120, a second AR user device 110 confirms the second user's 105 identity and generates a second identification token 130. The second AR user device 110 communicates the first identification token 130. The second AR user device 110 may display the first user's 105 gesture motion in real time. After the second user 105 reviews the first identification token 130 to confirm the first user's 105 identity and witnesses the first user 105 execute virtual file document 120 in real time, the second user 105 may express a gesture motion, such as a signing motion, that represents the second user's 105 signature on virtual file document 120. The second AR user device 110 creates a second digital signature 135 based on the gesture motion. The second AR user device 110 generates a transfer token 125 that includes the second identification token 130 and the second digital signature 135 and transmits the second transfer token to server 140. Server 140 generates executed document 170 using virtual file document 120 and the first and second transfer tokens 125. For example, server 140 may generate a single file comprising virtual file document 120 and one or more tokens 165 to generated executed document 170. As another example, server 140 may extract one or more digital signatures 135 from tokens 165 and overlay the digital signatures 135 onto virtual file document 120 to create executed document 170.
In another exemplary embodiment, a second user 105 may not be available to witness the first user 105 execute the document in real time. In this embodiment, server 104, the first AR user device 110, the second AR user device 110, and/or any other suitable component of system 100 may store all or a portion of the first transfer token 125. When a second user 105 is available, the second AR user device 110 may receive and/or display information associated with the first transfer token 125 to the second user 105. The second user 105 may then execute virtual file document 120 as described above. System 100 may facilitate remote document signing by any number of users 105. This disclosure contemplates some users 105 signing the document in real time while other users 105 sign at a second, later time.
Modifications, additions, or omissions may be made to system 100 without departing from the scope of the invention. For example, system 100 may include any number of processors 150, memory 145, AR user devices 110, and/or biometric databases 175. As a further example, components of system 100 may be separated or combined. For example, server 140 and/or biometric database 175 may be combining with one or more AR user devices 110.
The second AR user device 110 displays virtual file document 120b for a second user 105. In some embodiments, the second user 105 is a witness. In particular embodiments, virtual file document 120b is identical to virtual file document 120a except that the second AR user device 110 displays the first user's 105 digital signature 135a on document 120b. The second user 105 confirms the first user's 105 identity (e.g., using identification token 130). The second user 105 confirms the first user's 105 digital signature 135a (e.g., by viewing the first user 105 execute virtual file document 120 in real-time or by viewing a recording of the first user 105 generating the digital signature). Once the second user 105 confirms the first user's 105 identity and digital signature 135a, the second user 105 may perform a gesture motion to execute virtual file document 120. The second AR user device 110 may generate a second digital signature 135b and communicate the second digital signature 135b to a third a third AR user device 110 and/or server 104.
The third AR user device 110 displays virtual file document 120c for a third user 105. In some embodiments, the third user 105 is a notary public. In particular embodiments, virtual file document 120c is identical to virtual file documents 120a and/or 120b except that the third AR user device 110 may display the first user's 105 digital signature 135a and/or the second user's 105 digital signature 135b on virtual file document 120c. The third user 105 confirms the first user's 105 identity and/or the second user's 105 identity (e.g., using identification token 130). The third user 105 confirms the first user's 105 digital signature 135a and/or the second user's 105 digital signature 135b (e.g., by viewing the first user 105 and/or the second user 105 generate the digital signatures 135 in real-time or by viewing a recording of the first user 105 and/or the second user 105 generating the digital signatures 135). Once the third user 105 confirms the identities and/or digital signatures 135, the third user 105 may execute a gesture motion to execute the virtual file document 120. The third AR user device 110 may generate a third digital signature 135c and communicate the third digital signature 135c to server 104.
Server 140 receives digital signatures for each party to the document. For example server 140 receives transfer tokens 125a, 125b, and 125c that include digital signatures 135a, 135b, and 135c, respectively. Server 140 may then combine the digital signatures and virtual file document 120 to create executed document 170. In some embodiments, executed document 170 may include additional information such as one or more identification tokens 130 and/or transfer tokens 125.
AR user device 110 comprises a processor 302, a memory 304, a camera 306, a display 308, a wireless communication interface 310, a network interface 312, a microphone 314, a global position system (GPS) sensor 316, and one or more biometric devices 317. The AR user device 110 may be configured as shown or in any other suitable configuration. For example, AR user device 110 may comprise one or more additional components and/or one or more shown components may be omitted.
Examples of the camera 306 include, but are not limited to, charge-coupled device (CCD) cameras and complementary metal-oxide semiconductor (CMOS) cameras. The camera 306 is configured to capture images 332 of people, text, and objects within a real environment. The camera 306 may be configured to capture images 332 continuously, at predetermined intervals, or on-demand. For example, the camera 306 may be configured to receive a command from a user to capture an image 332. In another example, the camera 306 is configured to continuously capture images 332 to form a video stream of images 332. The camera 306 may be operably coupled to a facial recognition engine 322 and/or object recognition engine 324 and provides images 332 to the facial recognition engine 322 and/or the object recognition engine 324 for processing, for example, to identify people, text, and/or objects in front of the user. Facial recognition engine 322 may confirm a user's 105 identity.
The display 308 is configured to present visual information to a user in an augmented reality environment that overlays virtual or graphical objects onto tangible objects in a real scene in real-time. In an embodiment, the display 308 is a wearable optical head-mounted display configured to reflect projected images and allows a user to see through the display. For example, the display 308 may comprise display units, lens, semi-transparent mirrors embedded in an eye glass structure, a visor structure, or a helmet structure. Examples of display units include, but are not limited to, a cathode ray tube (CRT) display, a liquid crystal display (LCD), a liquid crystal on silicon (LCOS) display, a light emitting diode (LED) display, an active matrix OLED (AMOLED), an organic LED (OLED) display, a projector display, or any other suitable type of display as would be appreciated by one of ordinary skill in the art upon viewing this disclosure. In another embodiment, the display 308 is a graphical display on a user device. For example, the graphical display may be the display of a tablet or smart phone configured to display an augmented reality environment with virtual or graphical objects overlaid onto tangible objects in a real scene in real-time.
Examples of the wireless communication interface 310 include, but are not limited to, a Bluetooth interface, an RFID interface, an NFC interface, a local area network (LAN) interface, a personal area network (PAN) interface, a wide area network (WAN) interface, a Wi-Fi interface, a ZigBee interface, or any other suitable wireless communication interface as would be appreciated by one of ordinary skill in the art upon viewing this disclosure. The wireless communication interface 310 is configured to allow the processor 302 to communicate with other devices. For example, the wireless communication interface 310 is configured to allow the processor 302 to send and receive signals with other devices for the user (e.g. a mobile phone) and/or with devices for other people. The wireless communication interface 310 is configured to employ any suitable communication protocol.
The network interface 312 is configured to enable wired and/or wireless communications and to communicate data through a network, system, and/or domain. For example, the network interface 312 is configured for communication with a modem, a switch, a router, a bridge, a server, or a client. The processor 302 is configured to receive data using network interface 312 from a network or a remote source.
Microphone 314 is configured to capture audio signals (e.g. voice signals or commands) from a user and/or other people near the user. The microphone 314 is configured to capture audio signals continuously, at predetermined intervals, or on-demand. The microphone 314 is operably coupled to the voice recognition engine 320 and provides captured audio signals to the voice recognition engine 320 for processing, for example, to identify a voice command from the user.
The GPS sensor 316 is configured to capture and to provide geographical location information. For example, the GPS sensor 316 is configured to provide the geographic location of a user employing the augmented reality user device 300. The GPS sensor 316 is configured to provide the geographic location information as a relative geographic location or an absolute geographic location. The GPS sensor 316 provides the geographic location information using geographic coordinates (i.e. longitude and latitude) or any other suitable coordinate system.
Examples of biometric devices 317 include, but are not limited to, retina scanners, finger print scanners, voice recorders, and cameras. Biometric devices 317 are configured to capture information about a person's physical characteristics and to output a biometric signal 305 based on captured information. A biometric signal 305 is a signal that is uniquely linked to a person based on their physical characteristics. For example, a biometric device 317 may be configured to perform a retinal scan of the user's eye and to generate a biometric signal 305 for the user based on the retinal scan. As another example, a biometric device 317 is configured to perform a fingerprint scan of the user's finger and to generate a biometric signal 305 for the user based on the fingerprint scan. The biometric signal 305 is used by a physical identification verification engine 330 to identify and/or authenticate a person.
The processor 302 is implemented as one or more CPU chips, logic units, cores (e.g. a multi-core processor), FPGAs, ASICs, or DSPs. The processor 302 is communicatively coupled to and in signal communication with the memory 304, the camera 306, the display 308, the wireless communication interface 310, the network interface 312, the microphone 314, the GPS sensor 316, and the biometric devices 317. The processor 302 is configured to receive and transmit electrical signals among one or more of the memory 304, the camera 306, the display 308, the wireless communication interface 310, the network interface 312, the microphone 314, the GPS sensor 316, and the biometric devices 317. The electrical signals are used to send and receive data (e.g. images 232 and transfer tokens 124) and/or to control or communicate with other devices. For example, the processor 302 transmits electrical signals to operate the camera 306. The processor 302 may be operably coupled to one or more other devices (not shown).
The processor 302 is configured to process data and may be implemented in hardware or software. The processor 302 is configured to implement various instructions. For example, the processor 302 is configured to implement a virtual overlay engine 318, a voice recognition engine 320, a facial recognition engine 322, an object recognition engine 324, a gesture capture engine 326, a digital data transfer engine 328, a physical identification verification engine 330, and a gesture confirmation engine 331. In an embodiment, the virtual overlay engine 318, the voice recognition engine 320, the facial recognition engine 322, the object recognition engine 324, the gesture capture engine 326, the digital data transfer engine 328, the physical identification verification engine 330, and the gesture confirmation engine 331 is implemented using logic units, FPGAs, ASICs, DSPs, or any other suitable hardware.
The virtual overlay engine 318 is configured to overlay virtual objects onto tangible objects in a real scene using the display 308. For example, the display 308 may be a head-mounted display that allows a user to simultaneously view tangible objects in a real scene and virtual objects. The virtual overlay engine 318 is configured to process data to be presented to a user as an augmented reality virtual object on the display 308. An example of overlay virtual objects onto tangible objects in a real scene is shown in
The voice recognition engine 320 is configured to capture and/or identify voice patterns using the microphone 314. For example, the voice recognition engine 320 is configured to capture a voice signal from a person and to compare the captured voice signal to known voice patterns or commands to identify the person and/or commands provided by the person. For instance, the voice recognition engine 320 is configured to receive a voice signal to authenticate a user and/or another person or to initiate a digital data transfer.
The facial recognition engine 322 is configured to identify people or faces of people using images 332 or video streams created from a series of images 332. In one embodiment, the facial recognition engine 322 is configured to perform facial recognition on an image 332 captured by the camera 306 to identify the faces of one or more people in the captured image 332. In another embodiment, the facial recognition engine 322 is configured to perform facial recognition in about real-time on a video stream captured by the camera 306. For example, the facial recognition engine 322 is configured to continuously perform facial recognition on people in a real scene when the camera 306 is configured to continuous capture images 332 from the real scene. The facial recognition engine 322 employs any suitable technique for implementing facial recognition as would be appreciated by one of ordinary skill in the art upon viewing this disclosure.
The object recognition engine 324 is configured to identify objects, object features, text, and/or logos using images 332 or video streams created from a series of images 332. In one embodiment, the object recognition engine 324 is configured to identify objects and/or text within an image 332 captured by the camera 306. In another embodiment, the object recognition engine 324 is configured to identify objects and/or text in about real-time on a video stream captured by the camera 306 when the camera 306 is configured to continuously capture images 332. The object recognition engine 324 employs any suitable technique for implementing object and/or text recognition as would be appreciated by one of ordinary skill in the art upon viewing this disclosure.
The gesture recognition engine 326 is configured to identify gestures performed by a user and/or other people. Examples of gestures include, but are not limited to, hand movements, hand positions, finger movements, head movements, audible gestures, and/or any other actions that provide a signal from a person. For example, gesture recognition engine 326 is configured to identify hand gestures provided by a user 105 to indicate that the user 105 executed a document. For example, the hand gesture may be a signing gesture associated with a stylus, a camera, and/or a data glove. As another example, the gesture recognition engine 326 is configured to identify an audible gesture from a user 105 that indicates that the user 105 executed virtual file document 120. The gesture recognition engine 326 employs any suitable technique for implementing gesture recognition as would be appreciated by one of ordinary skill in the art upon viewing this disclosure.
The physical identification verification engine 330 is configured to identify a person based on a biometric signal 305 generated from the person's physical characteristics. The physical identification verification engine 330 employs one or more biometric devices 317 to identify a user based on one or more biometric signals 305. For example, the physical identification verification engine 330 receives a biometric signal 305 from the biometric device 317 in response to a retinal scan of the user's eye, a fingerprint scan of the user's finger, an audible voice capture, and/or a facial image capture. The physical identification verification engine 330 compares biometric signals 305 from the biometric device 317 to previously stored biometric signals 305 for the user to authenticate the user. The physical identification verification engine 330 authenticates the user when the biometric signals 305 from the biometric devices 317 substantially matches (e.g. is the same as) the previously stored biometric signals 305 for the user. In some embodiments, physical identification verification engine 330 includes voice recognitions engine 320 and/or facial recognition engine 322.
Gesture confirmation engine 331 is configured to receive a signor identity confirmation token, communicate a signor identity confirmation token, and display the gesture motion from the signor. Gesture confirmation engine 331 may facilitate allowing a witness, such as a notary public or an uninterested witness, to confirm that the signor executed the document. Gesture engine 331 may instruct AR user device 110 to display the signor's digital signature 135 on virtual file document 120. Gesture confirmation engine 331 may instruct AR user device 110 to display the gesture motion from the signor in any suitable way including displaying via audio, displaying via an image such as video or a still image, or displaying via virtual overlay.
The memory 304 comprises one or more disks, tape drives, or solid-state drives, and may be used as an over-flow data storage device, to store programs when such programs are selected for execution, and to store instructions and data that are read during program execution. The memory 304 may be volatile or non-volatile and may comprise ROM, RAM, TCAM, DRAM, and SRAM. The memory 304 is operable to store transfer tokens 125, biometric signals 305, virtual overlay instructions 336, voice recognition instructions 338, facial recognition instructions 340, object recognition instructions 342, gesture recognition instructions 344, digital data transfer instructions 346, biometric instructions 347, and any other data or instructions.
Biometric signals 305 are signals or data that is generated by a biometric device 317 based on a person's physical characteristics. Biometric signal 305 are used by the AR user device 110 to identify and/or authenticate an AR user device 110 user by comparing biometric signals 305 captured by the biometric devices 317 with previously stored biometric signals 305.
Transfer tokens 125 are generated by the digital data transfer engine 328 and sent to other AR user device 110, server 140, and/or any other suitable component of system 100. The transfer tokens 125 may comprise any suitable information for remote document execution. For example, the transfer tokens 125 may comprise an identification 130 and/or a digital signature 130, as discussed. In particular embodiments, transfer tokens 125 are encoded or encrypted to obfuscate and mask information being communicated across a network. Masking the information being communicated protects users and their information in the event of unauthorized access to the network and/or data occurs.
The virtual overlay instructions 336, the voice recognition instructions 338, the facial recognition instructions 340, the object recognition instructions 342, the gesture recognition instructions 344, the digital data transfer instructions 346, and the biometric instructions 347 each comprise any suitable set of instructions, logic, rules, or code operable to execute virtual overlay engine 318, the voice recognition engine 320, the facial recognition engine 322, the object recognition engine 324, the gesture recognition capture 326, the digital data transfer engine 328, and the physical identification verification engine 330, respectively.
The signor may view virtual file document 120 and execute the document. For example, the signor may perform a gesture motion representing a signature on virtual file document 120 to execute virtual file document 120. At step 420, the first AR user device 110 generates a digital signature 135 for the signor based on the gesture motion.
At step 430, virtual file document 120 is communicated to a second AR user device 110 associated with a witness. For example, the witness may be a notary public. The second AR user device 110 confirms the notary's identity by receiving biometric data for the notary and comparing the received biometric data to predetermined biometric data for the notary. The second AR user device 110 generates an identification token 130 for the notary in response to the confirmation as previously discussed. If the second AR user device does not confirm the notary's identity, the method ends. At step 440 the second AR user device 110 displays virtual file document 120 to the notary. For example, the second AR user device 110 displays virtual file document 120 to the signor. The first AR user device 110 may use a head-mounted display to overlay the virtual file document onto a tangible object.
The second AR user device 110 communicates the signor's digital signature 135 and/or identification token 130 to the notary at step 445. The notary views uses identification token 130 to authenticate the signor's identity. The notary then uses digital signature 135 to confirm that the signor executed the document (e.g., by viewing the signor executing the document). If the notary does not confirm that the signor executed the document at step 450, the method ends. If the notary does confirm that the signor executed the document at step 450, the method proceeds to step 455 where the notary makes a gesture motion representing a signature on virtual file document 120, and the second AR user device generates a digital signature 135 for the notary using the gesture motion. The second AR user device generates a transfer token 125 for the notary at step 460, wherein the transfer token 125 comprises the identification token 130 and digital signature 135 for the notary. The second AR user device 110 communicates the transfer token 125 to server 140. At step 465, server 140 receives tokens from the witness and the notary and stores the tokens as tokens 165. Server 140 may store the transfer token 125 for the signor, the identification token 130 for the signor, the digital signature 135 for the signor, the transfer token 125 for the notary, the identification token 130 for the notary, and/or the digital signature 130 for the notary as tokens 165. Server 140 generates executed document 170 using the virtual file document 120 and tokens 165 at step 465 before the method ends. For example, server 140 may generate a single file comprising virtual file document 120 and one or more tokens 165 to generated executed document 170. As another example, server 140 may extract one or more digital signatures 135 from tokens 165 and overlay the digital signatures 135 onto virtual file document 120 to create executed document 170.
Modifications, additions, or omissions may be made to method 400 depicted in
Although the present disclosure includes several embodiments, a myriad of changes, variations, alterations, transformations, and modifications may be suggested to one skilled in the art, and it is intended that the present disclosure encompass such changes, variations, alterations, transformations, and modifications as fall within the scope of the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5999944 | Lipkin | Dec 1999 | A |
| 6408257 | Harrington et al. | Jun 2002 | B1 |
| 6602075 | Adams | Aug 2003 | B2 |
| 6602076 | Adams | Aug 2003 | B2 |
| 6625299 | Meisner et al. | Sep 2003 | B1 |
| 6871140 | Florance et al. | Mar 2005 | B1 |
| 6941001 | Bolle et al. | Sep 2005 | B1 |
| 7099850 | Mann, II et al. | Aug 2006 | B1 |
| 7392208 | Morse et al. | Jun 2008 | B2 |
| 7680694 | Glazer et al. | Mar 2010 | B2 |
| 7787992 | Pretlove et al. | Aug 2010 | B2 |
| 7817104 | Ryu et al. | Oct 2010 | B2 |
| 7831471 | Adams | Nov 2010 | B2 |
| 7834883 | Adams | Nov 2010 | B2 |
| 8069095 | Glazer et al. | Nov 2011 | B2 |
| 8165924 | Smyers et al. | Apr 2012 | B2 |
| 8214387 | King et al. | Jul 2012 | B2 |
| 8285638 | Jung et al. | Oct 2012 | B2 |
| 8326704 | Glazer et al. | Dec 2012 | B2 |
| 8385981 | Kumaran | Feb 2013 | B2 |
| 8396738 | Allan et al. | Mar 2013 | B1 |
| 8417625 | Bannerjee et al. | Apr 2013 | B2 |
| 8433650 | Thomas | Apr 2013 | B1 |
| 8438001 | Natarajan et al. | May 2013 | B2 |
| 8438110 | Calman et al. | May 2013 | B2 |
| 8442295 | Sam | May 2013 | B2 |
| 8442906 | Thomas | May 2013 | B1 |
| 8451266 | Hertenstein | May 2013 | B2 |
| 8577803 | Chatterjee et al. | Nov 2013 | B2 |
| 8589255 | Glazer et al. | Nov 2013 | B2 |
| 8601386 | Altberg et al. | Dec 2013 | B2 |
| 8611601 | Calman et al. | Dec 2013 | B2 |
| 8612363 | Karkanias et al. | Dec 2013 | B2 |
| 8635104 | Adams | Jan 2014 | B2 |
| 8638363 | King et al. | Jan 2014 | B2 |
| 8660951 | Calman et al. | Feb 2014 | B2 |
| 8688594 | Thomas et al. | Apr 2014 | B2 |
| 8718612 | Calman et al. | May 2014 | B2 |
| 8743145 | Price | Jun 2014 | B1 |
| 8803916 | Paczkowski et al. | Aug 2014 | B1 |
| 8805739 | Brown et al. | Aug 2014 | B2 |
| 8810599 | Tseng | Aug 2014 | B1 |
| 8811711 | Calman et al. | Aug 2014 | B2 |
| 8890896 | Tseng | Nov 2014 | B1 |
| 8929591 | Calman et al. | Jan 2015 | B2 |
| 8989431 | Erol et al. | Mar 2015 | B1 |
| 8990235 | King et al. | Mar 2015 | B2 |
| 8990914 | Da Cruz Pinto et al. | Mar 2015 | B2 |
| 9007473 | Worley, III et al. | Apr 2015 | B1 |
| 9026486 | Doorhy et al. | May 2015 | B2 |
| 9044673 | Ahuja et al. | Jun 2015 | B1 |
| 9047636 | Ross | Jun 2015 | B2 |
| 9066200 | Loxam et al. | Jun 2015 | B1 |
| 9082149 | Argue et al. | Jul 2015 | B2 |
| 9092600 | Scavezze et al. | Jul 2015 | B2 |
| 9092898 | Fraccaroli et al. | Jul 2015 | B1 |
| 9100493 | Zhou et al. | Aug 2015 | B1 |
| 9105011 | Calman et al. | Aug 2015 | B2 |
| 9105013 | Chavez | Aug 2015 | B2 |
| 9111383 | Fein et al. | Aug 2015 | B2 |
| 9153074 | Zhou et al. | Oct 2015 | B2 |
| 9223950 | Li et al. | Dec 2015 | B2 |
| 9230367 | Stroila | Jan 2016 | B2 |
| 9251411 | Todeschini | Feb 2016 | B2 |
| 9251504 | Chavez | Feb 2016 | B2 |
| 9317860 | Calman et al. | Apr 2016 | B2 |
| 9331969 | Barak et al. | May 2016 | B2 |
| 9338589 | Loxam et al. | May 2016 | B2 |
| 9342928 | Rasane et al. | May 2016 | B2 |
| 9349118 | Chavez | May 2016 | B2 |
| 9355123 | Wnuk et al. | May 2016 | B2 |
| 9367878 | Rao | Jun 2016 | B2 |
| 9384594 | Maciocci et al. | Jul 2016 | B2 |
| 20020044152 | Abbott, III et al. | Apr 2002 | A1 |
| 20090235082 | Garrett | Sep 2009 | A1 |
| 20100238161 | Varga et al. | Sep 2010 | A1 |
| 20110134108 | Hertenstein | Jun 2011 | A1 |
| 20120156668 | Zelin | Jun 2012 | A1 |
| 20120232966 | Calman et al. | Sep 2012 | A1 |
| 20120232968 | Calman et al. | Sep 2012 | A1 |
| 20120232976 | Calman et al. | Sep 2012 | A1 |
| 20120232977 | Calman et al. | Sep 2012 | A1 |
| 20120310826 | Chatterjee | Dec 2012 | A1 |
| 20130166332 | Hammad | Jun 2013 | A1 |
| 20130226682 | Grossman | Aug 2013 | A1 |
| 20140040127 | Chatterjee et al. | Feb 2014 | A1 |
| 20140067712 | Prasad et al. | Mar 2014 | A1 |
| 20140100994 | Tatzel et al. | Apr 2014 | A1 |
| 20140172559 | Calman et al. | Jun 2014 | A1 |
| 20140181678 | Louchheim et al. | Jun 2014 | A1 |
| 20140279426 | Holman et al. | Sep 2014 | A1 |
| 20140330511 | Tison et al. | Nov 2014 | A1 |
| 20140337175 | Katzin et al. | Nov 2014 | A1 |
| 20140379468 | Ganesh et al. | Dec 2014 | A1 |
| 20150012426 | Purves et al. | Jan 2015 | A1 |
| 20150046284 | Hart | Feb 2015 | A1 |
| 20150058229 | Wiacek et al. | Feb 2015 | A1 |
| 20150066722 | Calman et al. | Mar 2015 | A1 |
| 20150073907 | Purves et al. | Mar 2015 | A1 |
| 20150082203 | James et al. | Mar 2015 | A1 |
| 20150086114 | Todeschini | Mar 2015 | A1 |
| 20150154446 | Masood et al. | Jun 2015 | A1 |
| 20150186984 | Loganathan | Jul 2015 | A1 |
| 20150206218 | Banerjee et al. | Jul 2015 | A1 |
| 20150221151 | Bacco et al. | Aug 2015 | A1 |
| 20150229750 | Zhou et al. | Aug 2015 | A1 |
| 20150254510 | McKinnon et al. | Sep 2015 | A1 |
| 20150294322 | Grigg et al. | Oct 2015 | A1 |
| 20150302027 | Wnuk et al. | Oct 2015 | A1 |
| 20150324562 | Scavezze et al. | Nov 2015 | A1 |
| 20150339468 | Son et al. | Nov 2015 | A1 |
| 20150348329 | Carre et al. | Dec 2015 | A1 |
| 20150363761 | Grigg et al. | Dec 2015 | A1 |
| 20150363764 | Grigg et al. | Dec 2015 | A1 |
| 20150371445 | Karrer Walker et al. | Dec 2015 | A1 |
| 20160049095 | Yannier et al. | Feb 2016 | A1 |
| 20160063484 | Carpenter et al. | Mar 2016 | A1 |
| 20160063517 | Sorensen | Mar 2016 | A1 |
| 20160078277 | Sprigg | Mar 2016 | A1 |
| 20160078449 | Banerjee | Mar 2016 | A1 |
| 20160098936 | Solomon | Apr 2016 | A1 |
| 20160171767 | Anderson | Jun 2016 | A1 |
| 20160188861 | Todeschini | Jun 2016 | A1 |
| 20160189426 | Thomas et al. | Jun 2016 | A1 |
| 20160206960 | Allen et al. | Jul 2016 | A1 |
| 20160210784 | Ramsby et al. | Jul 2016 | A1 |
| 20160210790 | Rasane et al. | Jul 2016 | A1 |
| 20160217623 | Singh | Jul 2016 | A1 |
| 20170140486 | Saxena | May 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 103635920 | Mar 2014 | CN |
| Entry |
|---|
| Saettler, M., “Westpac integrates augmented reality into bank account management,” http://www.mobilecommercedaily.com/westpac-integrates-augmented-reality-into-bank-account-management, Aug. 6, 2014, 8 pages. |
| Dolan, H. et al., “Facilitating Digital Data Transfers Using Augmented Reality Display Devices,” U.S. Appl. No. 15/353,005, filed Nov. 16, 2016, 50 pages. |
| Johansen, J. N. et al., “Real World Gamification Using Augmented Reality User Devices ,” U.S. Appl. No. 15/377,690, filed Dec. 13, 2016, 70 pages. |
| Adams, A. J. et al., “Virtual Reality Dynamic Authentication,” U.S. Appl. No. 15/367,590, filed Dec. 2, 2016, 58 pages. |
| Lee, J. et al., “Contextual Augmented Reality Overlays,” U.S. Appl. No. 15/363,388, filed Nov. 29, 2016, 50 pages. |
| Waldron, W. H. et al., “Virtual Assessments Using Augmented Reality User Devices,” U.S. Appl. No. 15/364,927, filed Nov. 30, 2016, 85 pages. |
| Dolan, H. et al., “Augmented Reality Headset and Digital Wallet,” U.S. Appl. No. 15/363,692, filed Nov. 29, 2016, 41 pages. |
| Johansen, J. N., “Facilitating Dynamic Across-Network Location Determination Using Augmented Reality Display Devices,” U.S. Appl. No. 15/372,909, filed Dec. 8, 2016, 44 pages. |
| Ogrinz, M. et al., “Facilitating Network Security Analysis Using Virtual Reality Display Devices.” U.S. Appl. No. 15/367,896, filed Dec. 2, 2016, 44 pages. |
| Dintenfass, K., “Property Assessments Using Augmented Reality User Devices,” U.S. Appl. No. 15/367,435, filed Dec. 2, 2016, 81 pages. |
| Wadley, C. D. et al., “Facilitating Across-Network, Multi-User Sessions Using Augmented Reality Display Devices,” U.S. Appl. No. 15/397,086, filed Jan. 3, 2017, 49 pages. |
| Dintenfass, K., “Geo-targeted Property Analysis Using Augmented Reality User Devices,” U.S. Appl. No. 15/367,554, filed Dec. 2, 2016, 80 pages. |
| Adams, A. J. et al., “Augmented Reality Dynamic Authentication for Electronic Transactions,” U.S. Appl. No. 15/367,551, filed Dec. 2, 2016, 57 pages. |
| Lee, J., “Facilitating Digital Data Transfers Using Virtual Reality Display Devices,” U.S. Appl. No. 15/363,185, filed Nov. 29, 2016, 52 pages. |
| Dintenfass, K., “Real Estate Property Project Analysis Using Augmented Reality User Devices,” U.S. Appl. No. 15/367,822, filed Dec. 2, 2016, 81 pages. |
| Adams, A. J. et al., “Augmented Reality Dynamic Authentication,”U.S. Appl. No. 15/367,502, filed Dec. 2, 2016, 57 pages. |
| Waldron, W. H. et al., “Virtual Behavior Training Using Augmented Reality User Devices,” U.S. Appl. No. 15/377,795, filed Dec. 13, 2016, 71 pages. |
| Dolan, H. et al., “User Authentication and Authorization for Electronic Transaction,” U.S. Appl. No. 15/363,495, filed Nov. 29, 2016, 41 pages. |
| Waldron, W. H. et al., “Geolocation Notifications Using Augmented Reality User Devices,” U.S. Appl. No. 15/365,272, filed Nov. 30, 2016, 85 pages. |
| Waldron, W. H. et al., “Object Recognition and Analysis Using Augmented Reality User Devices,” U.S. Appl. No. 15/365,511, filed Nov. 30, 2016, 86 pages. |
| Wadley, C. D. et al., “Facilitating Across-Network Handoffs for Devices Using Augmented Reality Display Devices,” U.S. Appl. No. 15/397,031, filed Jan. 3, 2017, 49 pages. |
| Wadley, C. D. et al., “Facilitating Across-Network Handoffs for an Assistant Using Augmented Reality Display Devices,” U.S. Appl. No. 15/397,125, filed Jan. 3, 2017, 48 pages. |
| Johansen, J. N., “Facilitating Dynamic Across-Network Location Determination Using Augmented Reality Display Devices,” U.S. Appl. No. 15/372,964, filed Dec. 8, 2016, 43 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20180139204 A1 | May 2018 | US |
