SECURED TRANSACTIONS ON WEARABLE DEVICES

Systems herein describe a secured transaction system for accessing a camera stream from a front-facing camera unit of a wearable computing device, identifying a visual marker in the camera feed associated with a payment application, in response to identifying the visual marker, transmitting a request to an operating system of the wearable computing device to isolate access of the camera stream to the payment application and in response to transmitting the request, initiating a transaction using the payment application.

TECHNICAL FIELD

Systems herein describe hardware and software solutions to secure transactions. More specifically, but not by way of limitations, systems herein describe solutions for securing transactions on wearable glasses.

BACKGROUND

Wearable computing devices, including wearable eyeglasses are increasingly becoming prevalent in society. These wearable eyeglasses are designed to leverage a camera system and allow its users to engage with virtual reality, augmented reality, and other image processing related technologies.

DETAILED DESCRIPTION

Systems herein describe a secured transaction system on a wearable computing device. Most financial transactions conducted on handheld devices utilize near-field communication (NFC) technology. But due to the lack of proximity of a wearable device such as wearable glasses to a physical transaction terminal, NFC is not a feasible protocol for financial transactions on wearable glasses.

A secured transaction system can facilitate financial transactions on wearable glasses without compromising security of a user's financial data. The financial transactions can be performed using outward facing (e.g., front-facing) cameras that are used to scan a visual marker associated with a transaction. For example, the visual marker can include a QR code. In response to scanning the code, the secured transactions system can secure the camera feed such that only a payment application associated with the visual marker can access the camera feed. After the camera feed has been secured, the secured transaction system permits the wearable glasses to be used to complete the transaction.

In some examples the camera feed is secured by storing the incoming camera feed in a secure memory buffer. In some examples, the camera feed is secured by transmitting a request to the operating system to restrict access of the camera feed to only a specific set of applications. Further details of the secured transaction system are described below.

Networked Computing Environment

FIG. 1 is a block diagram showing an example interaction system 100 for facilitating interactions (e.g., exchanging text messages, conducting text audio and video calls, or playing games) over a network. The interaction system 100 includes multiple user systems 102, each of which hosts multiple applications, including an interaction client 104 and other applications 106. Each interaction client 104 is communicatively coupled, via one or more communication networks including a network 108 (e.g., the Internet), to other instances of the interaction client 104 (e.g., hosted on respective other user systems 102), an interaction server system 110 and third-party servers 112). An interaction client 104 can also communicate with locally hosted applications 106 using Applications Program Interfaces (APIs).

Each user system 102 may include multiple user devices, such as a mobile device 114, head-wearable apparatus 116, and a computer client device 118 that are communicatively connected to exchange data and messages.

An interaction client 104 interacts with other interaction clients 104 and with the interaction server system 110 via the network 108. The data exchanged between the interaction clients 104 (e.g., interactions 120) and between the interaction clients 104 and the interaction server system 110 includes functions (e.g., commands to invoke functions) and payload data (e.g., text, audio, video, or other multimedia data).

The interaction server system 110 provides server-side functionality via the network 108 to the interaction clients 104. While certain functions of the interaction system 100 are described herein as being performed by either an interaction client 104 or by the interaction server system 110, the location of certain functionality either within the interaction client 104 or the interaction server system 110 may be a design choice. For example, it may be technically preferable to initially deploy particular technology and functionality within the interaction server system 110 but to later migrate this technology and functionality to the interaction client 104 where a user system 102 has sufficient processing capacity.

The interaction server system 110 supports various services and operations that are provided to the interaction clients 104. Such operations include transmitting data to, receiving data from, and processing data generated by the interaction clients 104. This data may include message content, client device information, geolocation information, media augmentation and overlays, message content persistence conditions, entity relationship information, and live event information. Data exchanges within the interaction system 100 are invoked and controlled through functions available via user interfaces (UIs) of the interaction clients 104.

Turning now specifically to the interaction server system 110, an Application Program Interface (API) server 122 is coupled to and provides programmatic interfaces to interaction servers 124, making the functions of the interaction servers 124 accessible to interaction clients 104, other applications 106 and third-party server 112. The interaction servers 124 are communicatively coupled to a database server 126, facilitating access to a database 128 that stores data associated with interactions processed by the interaction servers 124. Similarly, a web server 130 is coupled to the interaction servers 124 and provides web-based interfaces to the interaction servers 124. To this end, the web server 130 processes incoming network requests over the Hypertext Transfer Protocol (HTTP) and several other related protocols.

The Application Program Interface (API) server 122 receives and transmits interaction data (e.g., commands and message payloads) between the interaction servers 124 and the user systems 102 (and, for example, interaction clients 104 and other application 106) and the third-party server 112. Specifically, the Application Program Interface (API) server 122 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the interaction client 104 and other applications 106 to invoke functionality of the interaction servers 124. The Application Program Interface (API) server 122 exposes various functions supported by the interaction servers 124, including account registration; login functionality; the sending of interaction data, via the interaction servers 124, from a particular interaction client 104 to another interaction client 104; the communication of media files (e.g., images or video) from an interaction client 104 to the interaction servers 124; the settings of a collection of media data (e.g., a story); the retrieval of a list of friends of a user of a user system 102; the retrieval of messages and content; the addition and deletion of entities (e.g., friends) to an entity relationship graph (e.g., the entity graph 310); the location of friends within an entity relationship graph; and opening an application event (e.g., relating to the interaction client 104).

The interaction servers 124 host multiple systems and subsystems, described below with reference to FIG. 2.

System Architecture

FIG. 2 is a block diagram illustrating further details regarding the interaction system 100, according to some examples. Specifically, the interaction system 100 is shown to comprise the interaction client 104 and the interaction servers 124. The interaction system 100 embodies multiple subsystems, which are supported on the client-side by the interaction client 104 and on the server-side by the interaction servers 124. In some examples, these subsystems are implemented as microservices. A microservice subsystem (e.g., a microservice application) may have components that enable it to operate independently and communicate with other services. Example components of microservice subsystem may include:

In some examples, the interaction system 100 may employ a monolithic architecture, a service-oriented architecture (SOA), a function-as-a-service (FaaS) architecture, or a modular architecture:

Example subsystems are discussed below.

An image processing system 202 provides various functions that enable a user to capture and augment (e.g., annotate or otherwise modify or edit) media content associated with a message.

A camera system 204 includes control software (e.g., in a camera application) that interacts with and controls hardware camera hardware (e.g., directly or via operating system controls) of the user system 102 to modify and augment real-time images captured and displayed via the interaction client 104.

The augmentation system 206 provides functions related to the generation and publishing of augmentations (e.g., media overlays) for images captured in real-time by cameras of the user system 102 or retrieved from memory of the user system 102. For example, the augmentation system 206 operatively selects, presents, and displays media overlays (e.g., an image filter or an image lens) to the interaction client 104 for the augmentation of real-time images received via the camera system 204 or stored images retrieved from memory 602 of a user system 102. These augmentations are selected by the augmentation system 206 and presented to a user of an interaction client 104, based on a number of inputs and data, such as for example:

An augmentation may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., a photo or video) at user system 102 for communication in a message, or applied to video content, such as a video content stream or feed transmitted from an interaction client 104. As such, the image processing system 202 may interact with, and support, the various subsystems of the communication system 208, such as the messaging system 210 and the video communication system 212.

A media overlay may include text or image data that can be overlaid on top of a photograph taken by the user system 102 or a video stream produced by the user system 102. In some examples, the media overlay may be a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In further examples, the image processing system 202 uses the geolocation of the user system 102 to identify a media overlay that includes the name of a merchant at the geolocation of the user system 102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the databases 128 and accessed through the database server 126.

The image processing system 202 provides a user-based publication platform that enables users to select a geolocation on a map and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The image processing system 202 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

The augmentation creation system 214 supports augmented reality developer platforms and includes an application for content creators (e.g., artists and developers) to create and publish augmentations (e.g., augmented reality experiences) of the interaction client 104. The augmentation creation system 214 provides a library of built-in features and tools to content creators including, for example custom shaders, tracking technology, and templates.

In some examples, the augmentation creation system 214 provides a merchant-based publication platform that enables merchants to select a particular augmentation associated with a geolocation via a bidding process. For example, the augmentation creation system 214 associates a media overlay of the highest bidding merchant with a corresponding geolocation for a predefined amount of time.

A communication system 208 is responsible for enabling and processing multiple forms of communication and interaction within the interaction system 100 and includes a messaging system 210, an audio communication system 216, and a video communication system 212. The messaging system 210 is responsible for enforcing the temporary or time-limited access to content by the interaction clients 104. The messaging system 210 incorporates multiple timers (e.g., within an ephemeral timer system) that, based on duration and display parameters associated with a message or collection of messages (e.g., a story), selectively enable access (e.g., for presentation and display) to messages and associated content via the interaction client 104. The audio communication system 216 enables and supports audio communications (e.g., real-time audio chat) between multiple interaction clients 104. Similarly, the video communication system 212 enables and supports video communications (e.g., real-time video chat) between multiple interaction clients 104.

A user management system 218 is operationally responsible for the management of user data and profiles, and maintains entity information (e.g., stored in entity tables 308, entity graphs 310 and profile data 302) regarding users and relationships between users of the interaction system 100.

A map system 222 provides various geographic location (e.g., geolocation) functions and supports the presentation of map-based media content and messages by the interaction client 104. For example, the map system 222 enables the display of user icons or avatars (e.g., stored in profile data 302) on a map to indicate a current or past location of “friends” of a user, as well as media content (e.g., collections of messages including photographs and videos) generated by such friends, within the context of a map. For example, a message posted by a user to the interaction system 100 from a specific geographic location may be displayed within the context of a map at that particular location to “friends” of a specific user on a map interface of the interaction client 104. A user can furthermore share his or her location and status information (e.g., using an appropriate status avatar) with other users of the interaction system 100 via the interaction client 104, with this location and status information being similarly displayed within the context of a map interface of the interaction client 104 to selected users.

An external resource system 226 provides an interface for the interaction client 104 to communicate with remote servers (e.g., third-party servers 112) to launch or access external resources, i.e., applications or applets. Each third-party server 112 hosts, for example, a markup language (e.g., HTML5) based application or a small-scale version of an application (e.g., game, utility, payment, or ride-sharing application). The interaction client 104 may launch a web-based resource (e.g., application) by accessing the HTML5 file from the third-party servers 112 associated with the web-based resource. Applications hosted by third-party servers 112 are programmed in JavaScript leveraging a Software Development Kit (SDK) provided by the interaction servers 124. The SDK includes Application Programming Interfaces (APIs) with functions that can be called or invoked by the web-based application. The interaction servers 124 host a JavaScript library that provides a given external resource access to specific user data of the interaction client 104. HTML5 is an example of technology for programming games, but applications and resources programmed based on other technologies can be used.

To integrate the functions of the SDK into the web-based resource, the SDK is downloaded by the third-party server 112 from the interaction servers 124 or is otherwise received by the third-party server 112. Once downloaded or received, the SDK is included as part of the application code of a web-based external resource. The code of the web-based resource can then call or invoke certain functions of the SDK to integrate features of the interaction client 104 into the web-based resource.

The SDK stored on the interaction server system 110 effectively provides the bridge between an external resource (e.g., applications 106 or applets) and the interaction client 104. This gives the user a seamless experience of communicating with other users on the interaction client 104 while also preserving the look and feel of the interaction client 104. To bridge communications between an external resource and an interaction client 104, the SDK facilitates communication between third-party servers 112 and the interaction client 104. A bridge script running on a user system 102 establishes two one-way communication channels between an external resource and the interaction client 104. Messages are sent between the external resource and the interaction client 104 via these communication channels asynchronously. Each SDK function invocation is sent as a message and callback. Each SDK function is implemented by constructing a unique callback identifier and sending a message with that callback identifier.

By using the SDK, not all information from the interaction client 104 is shared with third-party servers 112. The SDK limits which information is shared based on the needs of the external resource. Each third-party server 112 provides an HTML5 file corresponding to the web-based external resource to interaction servers 124. The interaction servers 124 can add a visual representation (such as a box art or other graphic) of the web-based external resource in the interaction client 104. Once the user selects the visual representation or instructs the interaction client 104 through a GUI of the interaction client 104 to access features of the web-based external resource, the interaction client 104 obtains the HTML5 file and instantiates the resources to access the features of the web-based external resource.

The interaction client 104 presents a graphical user interface (e.g., a landing page or title screen) for an external resource. During, before, or after presenting the landing page or title screen, the interaction client 104 determines whether the launched external resource has been previously authorized to access user data of the interaction client 104. In response to determining that the launched external resource has been previously authorized to access user data of the interaction client 104, the interaction client 104 presents another graphical user interface of the external resource that includes functions and features of the external resource. In response to determining that the launched external resource has not been previously authorized to access user data of the interaction client 104, after a threshold period of time (e.g., 3 seconds) of displaying the landing page or title screen of the external resource, the interaction client 104 slides up (e.g., animates a menu as surfacing from a bottom of the screen to a middle or other portion of the screen) a menu for authorizing the external resource to access the user data. The menu identifies the type of user data that the external resource will be authorized to use. In response to receiving a user selection of an accept option, the interaction client 104 adds the external resource to a list of authorized external resources and allows the external resource to access user data from the interaction client 104. The external resource is authorized by the interaction client 104 to access the user data under an OAuth 2 framework.

The interaction client 104 controls the type of user data that is shared with external resources based on the type of external resource being authorized. For example, external resources that include full-scale applications (e.g., an application 106) are provided with access to a first type of user data (e.g., two-dimensional avatars of users with or without different avatar characteristics). As another example, external resources that include small-scale versions of applications (e.g., web-based versions of applications) are provided with access to a second type of user data (e.g., payment information, two-dimensional avatars of users, three-dimensional avatars of users, and avatars with various avatar characteristics). Avatar characteristics include different ways to customize a look and feel of an avatar, such as different poses, facial features, clothing, and so forth.

An artificial intelligence and machine learning system 230 provides a variety of services to different subsystems within the interaction system 100. For example, the artificial intelligence and machine learning system 230 operates with the image processing system 202 and the camera system 204 to analyze images and extract information such as objects, text, or faces. This information can then be used by the image processing system 202 to enhance, filter, or manipulate images. The artificial intelligence and machine learning system 230 may be used by the augmentation system 206 to generate augmented content and augmented reality experiences, such as adding virtual objects or animations to real-world images. The communication system 208 and messaging system 210 may use the artificial intelligence and machine learning system 230 to analyze communication patterns and provide insights into how users interact with each other and provide intelligent message classification and tagging, such as categorizing messages based on sentiment or topic. The artificial intelligence and machine learning system 230 may also provide chatbot functionality to message interactions 120 between user systems 102 and between a user system 102 and the interaction server system 110. The artificial intelligence and machine learning system 230 may also work with the audio communication system 216 to provide speech recognition and natural language processing capabilities, allowing users to interact with the interaction system 100 using voice commands.

A secured transaction system 232 allows for the camera feed of front-facing cameras of a wearable device to be isolated to a specific application on the wearable device that is being used to conduct a transaction. The secured transaction system 232 further establishes a secure connection to at least one of a financial institution or a vendor so that the payment can be fully processed. The secured transaction system 232 can receive an indication from the financial institution the vendor that the payment has been successfully received. Further details of the secured transaction system 232 are described below.

Data Architecture

FIG. 3 is a schematic diagram illustrating data structures 300, which may be stored in the database 304 of the interaction server system 110, according to certain examples. While the content of the database 304 is shown to comprise multiple tables, it will be appreciated that the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database 304 includes message data stored within a message table 306. This message data includes, for any particular message, at least message sender data, message recipient (or receiver) data, and a payload. Further details regarding information that may be included in a message, and included within the message data stored in the message table 306, are described below with reference to FIG. 3.

An entity table 308 stores entity data, and is linked (e.g., referentially) to an entity graph 310 and profile data 302. Entities for which records are maintained within the entity table 308 may include individuals, corporate entities, organizations, objects, places, events, and so forth. Regardless of entity type, any entity regarding which the interaction server system 110 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph 310 stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization), interest-based, or activity-based, merely for example. Certain relationships between entities may be unidirectional, such as a subscription by an individual user to digital content of a commercial or publishing user (e.g., a newspaper or other digital media outlet, or a brand). Other relationships may be bidirectional, such as a “friend” relationship between individual users of the interaction system 100.

Certain permissions and relationships may be attached to each relationship, and also to each direction of a relationship. For example, a bidirectional relationship (e.g., a friend relationship between individual users) may include authorization for the publication of digital content items between the individual users, but may impose certain restrictions or filters on the publication of such digital content items (e.g., based on content characteristics, location data or time of day data). Similarly, a subscription relationship between an individual user and a commercial user may impose different degrees of restrictions on the publication of digital content from the commercial user to the individual user, and may significantly restrict or block the publication of digital content from the individual user to the commercial user. A particular user, as an example of an entity, may record certain restrictions (e.g., by way of privacy settings) in a record for that entity within the entity table 308. Such privacy settings may be applied to all types of relationships within the context of the interaction system 100, or may selectively be applied to certain types of relationships.

The profile data 302 stores multiple types of profile data about a particular entity. The profile data 302 may be selectively used and presented to other users of the interaction system 100 based on privacy settings specified by a particular entity. Where the entity is an individual, the profile data 302 includes, for example, a user name, telephone number, address, settings (e.g., notification and privacy settings), as well as a user-selected avatar representation (or collection of such avatar representations). A particular user may then selectively include one or more of these avatar representations within the content of messages communicated via the interaction system 100, and on map interfaces displayed by interaction clients 104 to other users. The collection of avatar representations may include “status avatars,” which present a graphical representation of a status or activity that the user may select to communicate at a particular time.

The database 304 also stores augmentation data, such as overlays or filters, in an augmentation table 312. The augmentation data is associated with and applied to videos (for which data is stored in a video table 314) and images (for which data is stored in an image table 316).

Another type of filter is a data filter, which may be selectively presented to a sending user by the interaction client 104 based on other inputs or information gathered by the user system 102 during the message creation process. Examples of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a user system 102, or the current time.

Other augmentation data that may be stored within the image table 316 includes augmented reality content items (e.g., corresponding to applying “lenses” or augmented reality experiences). An augmented reality content item may be a real-time special effect and sound that may be added to an image or a video.

As mentioned above, the video table 314 stores video data that, in some examples, is associated with messages for which records are maintained within the message table 306. Similarly, the image table 316 stores image data associated with messages for which message data is stored in the entity table 308. The entity table 308 may associate various augmentations from the augmentation table 312 with various images and videos stored in the image table 316 and the video table 314.

The databases 304 also include a gesture table 320 for storing hand gesture data and a fingerprint table 322 for storing fingerprint data. The gesture table 320 and the fingerprint table 322 are used by the secured transaction system 232 to authenticate a user of the wearable device before initiating a financial transaction using the wearable device. The gesture table 320 stores data relating to hand gestures that are used to authenticate a user. The data can include hand joint coordinate locations and images. The fingerprint table 322 stores fingerprint data that is used to authenticate a user of the wearable device. The fingerprint data is captured using outward facing (front-facing) cameras of the wearable device.

Data Communications Architecture

FIG. 4 is a schematic diagram illustrating a structure of a message 400, according to some examples, generated by an interaction client 104 for communication to a further interaction client 104 via the interaction servers 124. The content of a particular message 400 is used to populate the message table 306 stored within the database 304, accessible by the interaction servers 124. Similarly, the content of a message 400 is stored in memory as “in-transit” or “in-flight” data of the user system 102 or the interaction servers 124. A message 400 is shown to include the following example components:

The contents (e.g., values) of the various components of message 400 may be pointers to locations in tables within which content data values are stored. For example, an image value in the message image payload 406 may be a pointer to (or address of) a location within an image table 316. Similarly, values within the message video payload 408 may point to data stored within an image table 316, values stored within the message augmentation data 412 may point to data stored in an augmentation table 312, values stored within the message story identifier 418 may point to data stored in a collections table 318, and values stored within the message sender identifier 422 and the message receiver identifier 424 may point to user records stored within an entity table 308.

FIG. 5 illustrates a process 500 for performing secured financial transactions on a head-wearable apparatus 116 in accordance with one embodiment. In one example, the processor in a secured transaction system 232, the processor in the head-wearable apparatus 116, the processor in the interaction server system 110 or any combination thereof, can perform the operations in process 500.

At operation 502 the processor accesses a camera stream from front-facing cameras of a wearable computing device. The camera stream includes a set of image frames. The front-facing cameras are outward facing cameras that are directionally facing away from a user of a head-wearable apparatus 116. Although the description herein refers to the head-wearable apparatus 116, any suitable wearable computing device with a camera unit can be used.

At operation 504, the processor identifies a visual marker in the camera stream, the visual marker associated with a payment application. The visual marker can be a QR code or a barcode that when scanned, triggers a payment application to initiate a transaction. The visual marker can be a unique visual marker that is generated for and associated with a specific payment amount for a particular transaction or can be a general visual marker associated with a payment application. The payment application can be a mobile payment application or a digital wallet application. The digital wallet application includes payment instrument information including bank data, credit card data, and any other suitable payment instrument.

The processor further causes display of transaction confirmation instructions on a display unit of the wearable computing device. The transaction confirmation instructions are visual instructions for performing a particular hand gesture. The instructions for gesture verification can include graphics, text, or a combination of graphics and text relating to a hand gesture. The processor identifies that a user of the wearable computing device has performed the hand gesture by comparing the hand gesture captured from the front-facing camera unit to the gesture data in the gesture table 320. After verifying the hand gesture, the processor proceeds to operation 504.

The gesture verification can further include identifying fingerprint data associated with the hand gesture. In response to a determination that the fingerprint data matches data in the fingerprint table 322, the processor proceeds to perform the steps of operation 506. The fingerprint data can be identified using the front-facing camera unit of the wearable computing device. The processor of the wearable computing device can utilize image processing techniques to analyze the image and compare the image to data in the fingerprint table 322.

The gesture verification described above can occur prior to operating the wearable device, after operation 504, or any combination thereof. In some examples, the processor can prompt a user of the wearable device to perform a first gesture that can be used to unlock the wearable computing device to enable operation of the device and can prompt the user to perform a second gesture to perform the steps of operation 506.

At operation 506, in response to identifying the visual marker, the processor transmits a request to an operating system of the wearable computing device to isolate access of the camera stream to the payment application. The request can be generated by the payment application and is transmitted to the operating system of the wearable computing device using a software framework associated with the front-facing camera unit. If the operating system accepts the request, the processor can isolate access of the camera stream to the payment application only. In some examples, the processor can isolate access of the camera stream by providing the camera stream to a secure hardware buffer of the wearable computing device. Individual camera frames of the camera stream can be provided to a particular portion of memory in the hardware of the wearable computing device.

The operating system could perform the software isolation whenever the payment application is running on the foreground. The payment application could set a flag (permission protected, only this payment application can set the flag), where the operating system would read and know that access should be only granted to the payment application. If the payment application sets the flag to make the camera only available to it, no other application gets access to camera frames. If the flag isn't set, all running application have access to the camera.

The processor can thus isolate access of the camera stream by transmitting a request to the operating system of the wearable computing device or by providing the camera stream to the secure hardware buffer. In some examples, the processor can attempt to transmit the request to the operating system and if the request is denied, the processor can provide the camera stream to the secure hardware buffer.

At operation 508, in response to transmitting the request, the processor initiates a transaction using the payment application. In some examples, the processor can automatically initiate the transaction. In other examples, the processor can prompt a user of the wearable device to input further information in the payment application relating to the transaction. The processor can cause display of a transaction flow associated with the transaction on the display unit of the wearable computing device. The transaction flow can prompt the user to input information using gestures, audio commands, or tactile input.

System with Head-Wearable Apparatus

FIG. 6 illustrates a system 600 including a head-wearable apparatus 116 with a selector input device, according to some examples. FIG. 6 is a high-level functional block diagram of an example head-wearable apparatus 116 communicatively coupled to a mobile device 114 and various server systems 604 (e.g., the interaction server system 110) via various networks 108.

The head-wearable apparatus 116 includes one or more cameras, each of which may be, for example, a visible light camera 606, an infrared emitter 608, and an infrared camera 610.

The mobile device 114 connects with head-wearable apparatus 116 using both a low-power wireless connection 612 and a high-speed wireless connection 614. The mobile device 114 is also connected to the server system 604 and the network 616.

The head-wearable apparatus 116 further includes two image displays of the image display of optical assembly 618. The two image displays of optical assembly 618 include one associated with the left lateral side and one associated with the right lateral side of the head-wearable apparatus 116. The head-wearable apparatus 116 also includes an image display driver 620, an image processor 622, low-power circuitry 624, and high-speed circuitry 626. The image display of optical assembly 618 is for presenting images and videos, including an image that can include a graphical user interface to a user of the head-wearable apparatus 116.

The image display driver 620 commands and controls the image display of optical assembly 618. The image display driver 620 may deliver image data directly to the image display of optical assembly 618 for presentation or may convert the image data into a signal or data format suitable for delivery to the image display device. For example, the image data may be video data formatted according to compression formats, such as H.264 (MPEG-4 Part 10), HEVC, Theora, Dirac, RealVideo RV40, VP8, VP9, or the like, and still image data may be formatted according to compression formats such as Portable Network Group (PNG), Joint Photographic Experts Group (JPEG), Tagged Image File Format (TIFF) or exchangeable image file format (EXIF) or the like.

The head-wearable apparatus 116 includes a frame and stems (or temples) extending from a lateral side of the frame. The head-wearable apparatus 116 further includes a user input device 628 (e.g., touch sensor or push button), including an input surface on the head-wearable apparatus 116. The user input device 628 (e.g., touch sensor or push button) is to receive from the user an input selection to manipulate the graphical user interface of the presented image.

The components shown in FIG. 6 for the head-wearable apparatus 116 are located on one or more circuit boards, for example a PCB or flexible PCB, in the rims or temples. Alternatively, or additionally, the depicted components can be located in the chunks, frames, hinges, or bridge of the head-wearable apparatus 116. Left and right visible light cameras 606 can include digital camera elements such as a complementary metal oxide-semiconductor (CMOS) image sensor, charge-coupled device, camera lenses, or any other respective visible or light-capturing elements that may be used to capture data, including images of scenes with unknown objects.

The head-wearable apparatus 116 includes a memory 602, which stores instructions to perform a subset or all of the functions described herein. The memory 602 can also include storage device.

As shown in FIG. 6, the high-speed circuitry 626 includes a high-speed processor 630, a memory 602, and high-speed wireless circuitry 632. In some examples, the image display driver 620 is coupled to the high-speed circuitry 626 and operated by the high-speed processor 630 in order to drive the left and right image displays of the image display of optical assembly 618. The high-speed processor 630 may be any processor capable of managing high-speed communications and operation of any general computing system needed for the head-wearable apparatus 116. The high-speed processor 630 includes processing resources needed for managing high-speed data transfers on a high-speed wireless connection 614 to a wireless local area network (WLAN) using the high-speed wireless circuitry 632. In certain examples, the high-speed processor 630 executes an operating system such as a LINUX operating system or other such operating system of the head-wearable apparatus 116, and the operating system is stored in the memory 602 for execution. In addition to any other responsibilities, the high-speed processor 630 executing a software architecture for the head-wearable apparatus 116 is used to manage data transfers with high-speed wireless circuitry 632. In certain examples, the high-speed wireless circuitry 632 is configured to implement Institute of Electrical and Electronic Engineers (IEEE) 802.11 communication standards, also referred to herein as WI-FIR. In some examples, other high-speed communications standards may be implemented by the high-speed wireless circuitry 632.

The low-power wireless circuitry 634 and the high-speed wireless circuitry 632 of the head-wearable apparatus 116 can include short-range transceivers (Bluetooth™) and wireless wide, local, or wide area network transceivers (e.g., cellular or WI-FI®). Mobile device 114, including the transceivers communicating via the low-power wireless connection 612 and the high-speed wireless connection 614, may be implemented using details of the architecture of the head-wearable apparatus 116, as can other elements of the network 616.

The memory 602 includes any storage device capable of storing various data and applications, including, among other things, camera data generated by the left and right visible light cameras 606, the infrared camera 610, and the image processor 622, as well as images generated for display by the image display driver 620 on the image displays of the image display of optical assembly 618. While the memory 602 is shown as integrated with high-speed circuitry 626, in some examples, the memory 602 may be an independent standalone element of the head-wearable apparatus 116. In certain such examples, electrical routing lines may provide a connection through a chip that includes the high-speed processor 630 from the image processor 622 or the low-power processor 636 to the memory 602. In some examples, the high-speed processor 630 may manage addressing of the memory 602 such that the low-power processor 636 will boot the high-speed processor 630 any time that a read or write operation involving memory 602 is needed.

As shown in FIG. 6, the low-power processor 636 or high-speed processor 630 of the head-wearable apparatus 116 can be coupled to the camera (visible light camera 606, infrared emitter 608, or infrared camera 610), the image display driver 620, the user input device 628 (e.g., touch sensor or push button), and the memory 602.

The head-wearable apparatus 116 is connected to a host computer. For example, the head-wearable apparatus 116 is paired with the mobile device 114 via the high-speed wireless connection 614 or connected to the server system 604 via the network 616. The server system 604 may be one or more computing devices as part of a service or network computing system, for example, that includes a processor, a memory, and network communication interface to communicate over the network 616 with the mobile device 114 and the head-wearable apparatus 116.

The mobile device 114 includes a processor and a network communication interface coupled to the processor. The network communication interface allows for communication over the network 616, low-power wireless connection 612, or high-speed wireless connection 614. Mobile device 114 can further store at least portions of the instructions in the memory of the mobile device 114 memory to implement the functionality described herein.

Output components of the head-wearable apparatus 116 include visual components, such as a display such as a liquid crystal display (LCD), a plasma display panel (PDP), a light-emitting diode (LED) display, a projector, or a waveguide. The image displays of the optical assembly are driven by the image display driver 620. The output components of the head-wearable apparatus 116 further include acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor), other signal generators, and so forth. The input components of the head-wearable apparatus 116, the mobile device 114, and server system 604, such as the user input device 628, may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instruments), tactile input components (e.g., a physical button, a touch screen that provides location and force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.

The head-wearable apparatus 116 may also include additional peripheral device elements. Such peripheral device elements may include biometric sensors, additional sensors, or display elements integrated with the head-wearable apparatus 116. For example, peripheral device elements may include any I/O components including output components, motion components, position components, or any other such elements described herein.

For example, the biometric components include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye-tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The biometric components may include a brain-machine interface (BMI) system that allows communication between the brain and an external device or machine. This may be achieved by recording brain activity data, translating this data into a format that can be understood by a computer, and then using the resulting signals to control the device or machine.

Example types of BMI technologies, including:

Any biometric data collected by the biometric components is captured and stored with only user approval and deleted on user request. Further, such biometric data may be used for very limited purposes, such as identification verification. To ensure limited and authorized use of biometric information and other personally identifiable information (PII), access to this data is restricted to authorized personnel only, if at all. Any use of biometric data may strictly be limited to identification verification purposes, and the biometric data is not shared or sold to any third party without the explicit consent of the user. In addition, appropriate technical and organizational measures are implemented to ensure the security and confidentiality of this sensitive information.

The motion components include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The position components include location sensor components to generate location coordinates (e.g., a Global Positioning System (GPS) receiver component), Wi-Fi or Bluetooth™ transceivers to generate positioning system coordinates, altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like. Such positioning system coordinates can also be received over low-power wireless connections 612 and high-speed wireless connection 614 from the mobile device 114 via the low-power wireless circuitry 634 or high-speed wireless circuitry 632.

Machine Architecture

FIG. 7 is a diagrammatic representation of the machine 700 within which instructions 702 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 700 to perform any one or more of the methodologies discussed herein may be executed. For example, the instructions 702 may cause the machine 700 to execute any one or more of the methods described herein. The instructions 702 transform the general, non-programmed machine 700 into a particular machine 700 programmed to carry out the described and illustrated functions in the manner described. The machine 700 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 700 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 700 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smartphone, a mobile device, a wearable device (e.g., a smartwatch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 702, sequentially or otherwise, that specify actions to be taken by the machine 700. Further, while a single machine 700 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 702 to perform any one or more of the methodologies discussed herein. The machine 700, for example, may comprise the user system 102 or any one of multiple server devices forming part of the interaction server system 110. In some examples, the machine 700 may also comprise both client and server systems, with certain operations of a particular method or algorithm being performed on the server-side and with certain operations of the particular method or algorithm being performed on the client-side.

The machine 700 may include processors 704, memory 706, and input/output I/O components 708, which may be configured to communicate with each other via a bus 710. In an example, the processors 704 (e.g., a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) Processor, a Complex Instruction Set Computing (CISC) Processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 712 and a processor 714 that execute the instructions 702. The term “processor” is intended to include multi-core processors that may comprise two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously. Although FIG. 7 shows multiple processors 704, the machine 700 may include a single processor with a single-core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiples cores, or any combination thereof.

The memory 706 includes a main memory 716, a static memory 718, and a storage unit 720, both accessible to the processors 704 via the bus 710. The main memory 706, the static memory 718, and storage unit 720 store the instructions 702 embodying any one or more of the methodologies or functions described herein. The instructions 702 may also reside, completely or partially, within the main memory 716, within the static memory 718, within machine-readable medium 722 within the storage unit 720, within at least one of the processors 704 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 700.

In further examples, the I/O components 708 may include biometric components 728, motion components 730, environmental components 732, or position components 734, among a wide array of other components. For example, the biometric components 728 include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye-tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram-based identification), and the like. The biometric components may include a brain-machine interface (BMI) system that allows communication between the brain and an external device or machine. This may be achieved by recording brain activity data, translating this data into a format that can be understood by a computer, and then using the resulting signals to control the device or machine.

Example types of BMI technologies, including:

Any biometric data collected by the biometric components is captured and stored only with user approval and deleted on user request. Further, such biometric data may be used for very limited purposes, such as identification verification. To ensure limited and authorized use of biometric information and other personally identifiable information (PII), access to this data is restricted to authorized personnel only, if at all. Any use of biometric data may strictly be limited to identification verification purposes, and the data is not shared or sold to any third party without the explicit consent of the user. In addition, appropriate technical and organizational measures are implemented to ensure the security and confidentiality of this sensitive information.

The motion components 730 include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope).

With respect to cameras, the user system 102 may have a camera system comprising, for example, front cameras on a front surface of the user system 102 and rear cameras on a rear surface of the user system 102. The front cameras may, for example, be used to capture still images and video of a user of the user system 102 (e.g., “selfies”), which may then be augmented with augmentation data (e.g., filters) described above. The rear cameras may, for example, be used to capture still images and videos in a more traditional camera mode, with these images similarly being augmented with augmentation data. In addition to front and rear cameras, the user system 102 may also include a 360° camera for capturing 360° photographs and videos. The rear cameras are also referred to herein as “front-facing cameras” and “outward facing cameras.”

Further, the camera system of the user system 102 may include dual rear cameras (e.g., a primary camera as well as a depth-sensing camera), or even triple, quad or penta rear camera configurations on the front and rear sides of the user system 102. These multiple cameras systems may include a wide camera, an ultra-wide camera, a telephoto camera, a macro camera, and a depth sensor, for example.

Communication may be implemented using a wide variety of technologies. The I/O components 708 further include communication components 736 operable to couple the machine 700 to a network 738 or devices 740 via respective coupling or connections. For example, the communication components 736 may include a network interface component or another suitable device to interface with the network 738. In further examples, the communication components 736 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 740 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a USB).

The various memories (e.g., main memory 716, static memory 718, and memory of the processors 704) and storage unit 720 may store one or more sets of instructions and data structures (e.g., software) embodying or used by any one or more of the methodologies or functions described herein. These instructions (e.g., the instructions 702), when executed by processors 704, cause various operations to implement the disclosed examples.

The instructions 702 may be transmitted or received over the network 738, using a transmission medium, via a network interface device (e.g., a network interface component included in the communication components 736) and using any one of several well-known transfer protocols (e.g., hypertext transfer protocol (HTTP)). Similarly, the instructions 702 may be transmitted or received using a transmission medium via a coupling (e.g., a peer-to-peer coupling) to the devices 740.

Software Architecture

FIG. 8 is a block diagram 800 illustrating a software architecture 802, which can be installed on any one or more of the devices described herein. The software architecture 802 is supported by hardware such as a machine 804 that includes processors 806, memory 808, and I/O components 810. In this example, the software architecture 802 can be conceptualized as a stack of layers, where each layer provides a particular functionality. The software architecture 802 includes layers such as an operating system 812, libraries 814, frameworks 816, and applications 818. Operationally, the applications 818 invoke API calls 820 through the software stack and receive messages 822 in response to the API calls 820.

The operating system 812 manages hardware resources and provides common services. The operating system 812 includes, for example, a kernel 824, services 826, and drivers 828. The kernel 824 acts as an abstraction layer between the hardware and the other software layers. For example, the kernel 824 provides memory management, processor management (e.g., scheduling), component management, networking, and security settings, among other functionalities. The services 826 can provide other common services for the other software layers. The drivers 828 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 828 can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flash memory drivers, serial communication drivers (e.g., USB drivers), WI-FI® drivers, audio drivers, power management drivers, and so forth.

The libraries 814 provide a common low-level infrastructure used by the applications 818. The libraries 814 can include system libraries 830 (e.g., C standard library) that provide functions such as memory allocation functions, string manipulation functions, mathematic functions, and the like. In addition, the libraries 814 can include API libraries 832 such as media libraries (e.g., libraries to support presentation and manipulation of various media formats such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries (e.g., an OpenGL framework used to render in two dimensions (2D) and three dimensions (3D) in a graphic content on a display), database libraries (e.g., SQLite to provide various relational database functions), web libraries (e.g., WebKit to provide web browsing functionality), and the like. The libraries 814 can also include a wide variety of other libraries 834 to provide many other APIs to the applications 818.

The frameworks 816 provide a common high-level infrastructure that is used by the applications 818. For example, the frameworks 816 provide various graphical user interface (GUI) functions, high-level resource management, and high-level location services. The frameworks 816 can provide a broad spectrum of other APIs that can be used by the applications 818, some of which may be specific to a particular operating system or platform.

In an example, the applications 818 may include a home application 836, a contacts application 838, a browser application 840, a book reader application 842, a location application 844, a media application 846, a messaging application 848, a game application 850, and a broad assortment of other applications such as a third-party application 852. The applications 818 are programs that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications 818, structured in a variety of manners, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or procedural programming languages (e.g., C or assembly language). In a specific example, the third-party application 852 (e.g., an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or another mobile operating system. In this example, the third-party application 852 can invoke the API calls 820 provided by the operating system 812 to facilitate functionalities described herein.

Examples

Example 1 is a method including accessing a camera stream from a front-facing camera unit of a wearable computing device, identifying a visual marker in the camera feed associated with a payment application, in response to identifying the visual marker, transmitting a request to an operating system of the wearable computing device to isolate access of the camera stream to the payment application, and in response to transmitting the request, initiating a transaction using the payment application.

In Example 2, the subject matter of Example 1 including in response to identifying the visual marker, causing display of transaction confirmation instructions on a display unit of the wearable computing device, the transaction confirmation instructions comprising instructions for performing a hand gesture, identifying, by the front facing camera unit of the wearable device, the hand gesture of a user of the wearable computing device, the hand gesture corresponding to the transaction confirmation instructions, in response to identifying the hand gesture, transmitting the request to the operating system.

In Example 3, the subject matter of Examples 1-2 including causing display of a transaction flow associated with the transaction on the display unit of the wearable computing device.

In Example 4, the subject matter of Examples 1-3 including wherein identifying the hand gesture further comprises, identifying fingerprint data associated with the hand gesture of the user, in response to a determination that the identified fingerprint data matches data in a database of fingerprint data, transmitting the request to the operating system.

In Example 5, the subject matter of Examples 1˜4 including wherein the request is generated by the payment application.

In Example 6, the subject matter of Examples 1-5 including storing camera frames of the camera stream in a secure hardware buffer of the wearable computing device.

In Example 7, the subject matter of Examples 1-6 including wherein the wearable computing device is a head-wearable apparatus.

Example 8 is an apparatus comprising means to implement of any of Examples 1-5.

Example 9 is a non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform the method of any of Examples 1-7.

Glossary

“Carrier signal” refers, for example, to any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine and includes digital or analog communications signals or other intangible media to facilitate communication of such instructions. Instructions may be transmitted or received over a network using a transmission medium via a network interface device.

“Non-transitory computer-readable storage medium” refers, for example, to a tangible medium that is capable of storing, encoding, or carrying the instructions for execution by a machine.

“User device” refers, for example, to a device accessed, controlled or owned by a user and with which the user interacts perform an action or interaction on the user device, including an interaction with other users or computer systems.