Patent Description:
It is with respect to these and other general considerations that embodiments have been described. Also, although relatively specific problems have been discussed, it should be understood that the embodiments should not be limited to solving the specific problems identified in the background. <CIT> relates to the field of electronic commerce stores offering goods and/or services for sale or purchase. The described techniques can provide information to a virtual reality device and/or an augmented reality device, among others, of a user/customer. The information can be associated with offerings of goods and/services for sale, purchase or rent. Determining the information can be based on past actions of the user and/or other users. For example, the determined information can be inferred from past actions of the user and/or other users. A layout of a virtual store and/or presentations of one or more items can be based on past actions of the user and/or other users. One or more of the layout of the virtual store and/or providing the information associated with the goods and/or services can be determined and/or chosen to maximize sales and/or profits.

Preferred embodiment are defined by the independent claims.

Aspects of the present disclosure relate to contextual input in a three-dimensional (3D) environment. In an example, a 3D environment is authored using an authoring application, wherein the author selects and positions one or more content items within the 3D environment. The 3D environment has a set of possible environment events that are associated with user input events and used to trigger actions for content items in the 3D environment. An author uses the authoring application to associate a given environment event with a content item action. Thus, an environment event is generated when a user input event is received from an input device, thereby causing the content item action to occur.

Accordingly, a user is able to use a variety of input devices to interact with the 3D environment regardless of the type of input events that are generated by such input devices. When an input event is received from an input device, an associated environment event is generated. A content item is determined in order to provide the generated environment event to the content item with which the user is interacting. The environment event is provided to the content item, thereby causing the content item action to be performed.

Non-limiting and non-exhaustive examples are described with reference to the following Figures.

In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These aspects may be combined, other aspects may be utilized, and structural changes may be made without departing from the present disclosure. Embodiments may be practiced as methods, systems or devices. Accordingly, embodiments may take the form of a hardware implementation, an entirely software implementation, or an implementation combining software and hardware aspects. The following detailed description is therefore not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

In an example, an author uses an authoring application to author a three-dimensional (3D) environment. The authoring application enables the author to add content to the 3D environment and position the content therein. An end user may use a viewer application to consume the 3D environment and interact with the content accordingly. However, a wide variety of possible input devices may be used, including, but not limited to, a mouse, a keyboard, a touchscreen, a game controller, or a physical gesture recognition device, among other examples. As a result, accounting for a wide array of potential input events is difficult. Additionally, different content within the 3D environment may process input events differently to perform one or more actions. Correctly linking various input events to such actions is a complex task and may introduce unnecessary complexity for an author of the 3D environment.

Accordingly, aspects of the present disclosure relate to contextual input in a 3D environment. In examples, a 3D environment has a set of possible environment events, such as a primary event and a secondary event, among other events. One or more input events (e.g., as may be received by an input device) are associated with an environment event. As a result, when an input event is received by an input device, an associated environment event is determined. A content item has an associated action, which can be linked to the environment event in order to cause the associated action to be performed by the content item when the environment event is triggered. Thus, according to aspects disclosed herein, an authoring application is used to add content item to a 3D environment and link environment events to content item actions accordingly. When a user interacts with the 3D environment, an input event from an input device is processed to generate an environment event, which is provided to an associated content item accordingly, thereby causing the content item to perform the action associated with the environment event.

As used herein, an authoring application is used by an author to create or edit a 3D environment. The authoring application may be a native application, a web application, or any combination thereof, among other examples. In some examples, different types of content may be embedded or included in the 3D environment as content items. Example content includes, but is not limited to, 3D objects (e.g., 3D models, figures, shapes, etc.), 2D objects (e.g., files, images, presentations, documents, web sites, videos, remote resources, etc.), or audio content, among other content. In addition to content items added to the 3D environment, one or more assets may be used. For example, a 3D environment may comprise a structure in which content is placed, assets for a background of the 3D environment, sound assets, or animation assets, among other assets. Thus, an asset may be a 3D model, a texture, an image, an animation, or a sound, among other assets used to implement or generate aspects of a 3D environment.

A 3D environment has a set of environment events. As used herein, an environment event is a predefined event of a 3D environment, which is associated with one or more input events from one or more input devices. Thus, the set of environment events provides a level of abstraction from specific (e.g., device-specific, manufacturer-specific, etc.) input events that are generated by various input devices. Thus, environment events can be used to specify actions that should be performed in the 3D environment. Example environment events include, but are not limited to, a primary event, a secondary event, a next event, and/or a back event. Input events are associated with environment events. For example, a left click or trigger press may be associated with a primary environment event, a right click or an inspect button may be associated with a secondary environment event, a right arrow or right swipe may be associated with a next environment event, while a left arrow or left swipe may be associated with a back environment event. An authoring application may enumerate a list of available environment events, such that an author is able to associate an environment event with an action of a content item. As a result, the author need not consider which of a variety of input devices may be used to interact with the 3D environment. Similarly, an end user is able to use a wide array of input devices when consuming the 3D environment. In some examples, a content item triggers another content item. For example, the first content item may provide an indication causing an environment event to be generated and provided to the second content item. As used herein, an "author" and an "end user" are each a type of user of a computing device. It will be appreciated that tasks described with respect to an author may, in other examples, be performed by an end user, and vice versa.

An authored 3D environment is stored as an environment data file. The environment data file comprises information relating to content items, environment event and action associations, and assets for inclusion in the 3D environment. In examples, a viewer application generates a 3D environment based on an environment data file for consumption by an end user. In examples, a 3D environment may be a virtual space, such as a virtual reality (VR) world, or may be a real world space in which content may be displayed or layered on top of the real world, among other augmented reality (AR) or VR techniques. The viewer application is executed by a computing device, such as a desktop computer or a smartphone. In an example, a 3D environment is experienced using any of a wide variety of VR or AR devices, ranging from low-end devices (e.g., GOOGLE CARDBOARD) to high-end devices (e.g., MICROSOFT HOLOLENS, OCULOUS RIFT, HTC VIVE, etc.).

As discussed above, a computing device may have any of a variety of input devices, including, but not limited to, a mouse, a keyboard, a touchscreen, a game controller, or a physical gesture recognition device, among other examples. Accordingly, input events received from such devices are processed by the viewer application to generate associated environment events, which are provided to content items in the 3D environment accordingly. Thus, device- or platform-specific idiosyncrasies may be handled by the viewer application, thereby making such idiosyncrasies invisible to both the end user and the author of the 3D environment.

<FIG> illustrates an overview of an example system <NUM> for contextual input in a three-dimensional environment. As illustrated, system <NUM> comprises computing devices <NUM> and <NUM>, and 3D environment service <NUM>. In an example, computing devices <NUM> and <NUM> may be any of a variety of computing devices, including, but not limited to, a mobile computing device, a laptop computing device, a tablet computing device, or a desktop computing device. In some examples, 3D environment service <NUM> is provided as part of a collaborative, communication, or productivity platform. It will be appreciated that while 3D environment service <NUM> and elements <NUM>-<NUM> are illustrated as separate from computing devices <NUM> and/or <NUM>, one or more of elements <NUM>-<NUM> may be provided by computing devices <NUM> and/or <NUM> other examples. As an example, computing device <NUM> may comprise authoring application <NUM>, while computing device <NUM> may comprise viewer application <NUM>.

System <NUM> illustrates 3D environment service <NUM> as comprising authoring application <NUM>, viewer application <NUM>, user input processing engine <NUM>, and authored environment data store <NUM>. Authoring application <NUM> is used to author a 3D environment according to aspects disclosed herein. In an example, authoring application <NUM> provides a graphical user interface (GUI) with which a user designs a 3D environment. For example, authoring application <NUM> enables an author to select content items and position the content items within the 3D environment accordingly. In examples, authoring application <NUM> presents a list of available environment events, which an author uses to associate one or more actions of a content item with a selected environment event. In some examples, the list of available environment events is filtered based on a content item type. In other examples, the list comprises events generated by one or more content items, such that one content item can trigger another content item. As discussed in greater detail below, an end user may then use viewer application <NUM> to consume the 3D environment and interact with content items.

3D environment service <NUM> is illustrated as further comprising user input processing engine <NUM>. In examples, authoring application <NUM> uses user input processing engine <NUM> to enumerate available environment events for a 3D environment. For example, user input processing engine <NUM> may determine a set of available environment events based on a content item type (e.g., a video content item, an image content item, a 3D model content item, etc.). User input processing engine <NUM> is used by authoring application <NUM> to process user input events when an author is authoring the 3D environment, thereby enabling the author to interact with content items. Similarly, user input processing engine <NUM> is used by viewer application <NUM> to process user input events when an end user is viewing / interacting with the 3D environment. While user input processing engine <NUM> is illustrated as separate from authoring application <NUM> and viewer application <NUM>, it will be appreciated that, in other examples, similar aspects are implemented by authoring application <NUM> and/or viewer application <NUM>.

In examples, processing an input event comprises identifying an association of the input event with an environment event. User input processing engine <NUM> further determines a content item that receives the environment event. In examples, an association between the environment event and an action of the determined content item is used to determine the action that is performed by the content item. Determining the content item to receive the environment event may comprise determining whether the input event is associated with a bounding box associated with a content item. As used herein, a bounding box is a rectangular prism that encompasses the graphical representation of the content item in the 3D environment. It will be appreciated that other geometry may be used, such as a bounding sphere or a more complex mesh associated with a content item. For example, a cursor may be positioned between the bounding box of a content item and a camera associated with a view of the user into the 3D environment, such that an input event associated with the cursor is determined to be directed to the content item. In another example, a user uses a VR controller to gesture in the direction of a content item, such that it is determined that the content item is the target of the input event. It will be appreciated that other detection techniques may be used according to aspects described herein.

In some instances, multiple bounding boxes are identified, such that a set of potential content items is determined. In examples, one content item is determined from the set based on evaluating a model associated with the content item. For example, a bounding box comprising a graphical representation of the content item at the location of the input event is selected over a bounding box comprising empty space at the location of the input event. In other examples, bounding box size or proximity to the user is evaluated to select one content item from the set of potential content items.

A 3D environment authored using authoring application <NUM> is stored as an environment data file. The environment data file comprises information relating to content items, environment event and action associations, and assets for inclusion in the 3D environment. For example, the environment data file comprises information relating to one or more content items, such as a location at which to display the content item, as well as a reference to the content. In other examples, the environment data file stores the content itself. It will be appreciated that the information stored by an environment data file described herein is provided as an example. The environment data file may be stored in authored environment data store <NUM> for consumption by an end user (e.g., using viewer application <NUM>) or for further revision using authoring application <NUM> (e.g., by the same author, a different author, etc.).

In some examples, authoring application <NUM> is a web-based application, wherein a computing device of a user (e.g., computing device <NUM> or computing device <NUM>) may access authoring application <NUM> using a web browser. In other examples, authoring application <NUM> may be an executable application, which may be retrieved and executed by a user's computing device.

Viewer application <NUM> generates a 3D environment based on an environment data file to enable a user to view, explore, and/or interact with the 3D environment and content items located therein. In an example, viewer application <NUM> is a web-based application, wherein a computing device of a user (e.g., computing device <NUM> or computing device <NUM>) accesses viewer application <NUM> using a web browser. In other examples, viewer application <NUM> may be an executable application, which may be retrieved and executed by a user's computing device. Viewer application <NUM> may populate the generated 3D environment with content items as specified by the environment data file.

Viewer application <NUM> uses user input processing engine <NUM> to process user input from one or more input devices when a user is exploring a 3D environment as described above. For example, input events received by viewer application <NUM> from one or more input devices are processed to generate associated environment events. A target content item for the user input is determined, such that a generated environment event is provided to the content item in the 3D environment accordingly.

Authored environment data store <NUM> stores one or more environment data files, as may be authored by authoring application <NUM>. In some examples, an "environment data file" as is used herein is stored as a file on a file system, an entry in a database, or may be stored using any of a variety of other data storage techniques. In examples, the environment data file is stored on a server (e.g., server <NUM> in <FIG>). In an example where authoring application <NUM> is a locally-executed application, at least a part of an authored environment data file may be received from one of computing devices <NUM> and <NUM>, and stored using authored environment data store <NUM>. In some examples, viewer application <NUM> retrieves an environment data file from authored environment data store <NUM>, which, in conjunction with one or more content items and/or assets, may be used to generate a 3D environment. In an example where a viewer application is a locally-executed application, aspects of one or more asset containers may be stored local and/or remote to the device executing the application, and at least a part of an environment data file may be retrieved from authored environment data store <NUM>. In some examples, the environment data file may be streamed or retrieved in chunks, so as to reduce bandwidth consumption and/or to improve responsiveness.

Applications <NUM> and <NUM> of computing devices <NUM> and <NUM>, respectively, may be any of a variety of applications. In an example, application <NUM> and/or <NUM> is an authoring application as described above, wherein a user of computing device <NUM> and/or <NUM> may use the application to author a 3D environment described by an environment data file. In some examples, the environment data file is stored by authored environment data store <NUM>. In another example, application <NUM> and/or <NUM> is a viewer application as described above, which may be used to view, render, and/or explore a 3D environment defined at least in part by an environment data file. In other examples, computing device <NUM> and/or <NUM> comprises an authored environment data store similar to authored environment data store <NUM>. In instances where viewer application <NUM> is a web-based application, application <NUM> and/or <NUM> is a web browser that is used to access viewer application <NUM>. In examples, one or more input devices and/or a hardware AR or VR device (not pictured) is attached to computing devices <NUM> and/or <NUM> and used to view and/or engage with a rendered 3D environment. For example, a VR or AR headset may be used.

<FIG> illustrates an overview of an example method <NUM> for authoring a three-dimensional environment implementing aspects of contextual input described herein. In examples, aspects of method <NUM> are performed by an authoring application, such as authoring application <NUM> in <FIG>. The authoring application may be a web-based application and/or a native application executing on a computing device, such as computing device <NUM> or <NUM> in <FIG>. Method <NUM> begins at operation <NUM>, where a selection of a content item to add to a 3D environment is received. Example content items include, but are not limited to, 3D objects (e.g., 3D models, figures, shapes, etc.), 2D objects (e.g., files, images, presentations, documents, web sites, videos, remote resources, etc.), or audio, among other content. The selection may indicate a location in the 3D environment at which the content should be placed. While method <NUM> is described with respect to receiving a single selection, it will be appreciated that, in other examples, aspects of method <NUM> are performed multiple times to add multiple content items to the 3D environment.

At operation <NUM>, a selection indicating a content item action for an environment event is received. As described herein, the 3D environment has a set of environment events, such that content item actions may be associated with environment events accordingly. Thus, the authoring application may display a list of environment events, thereby enabling the author to select a content item action to be associated with a displayed environment event. In examples, the user selection is received as a result of a user interacting with such a user interface, additional aspects of which are discussed with respect to <FIG>.

Flow progresses to operation <NUM>, where the selected content item action is associated with the environment event. In examples, the content item action is associated with the environment event by editing a property associated with the content item to indicate that the content item "listens" for the selected environment event. The property may identify the content item action that is performed when the environment event occurs. In another example, an event table is used for the 3D environment, wherein the event table lists content item actions and associated environment events. While example techniques for associating a content item action with an environment event are described, it will be appreciated that other techniques may be used.

At operation <NUM>, an environment data file is generated comprising the association between the content item action and the environment event. In examples, operation <NUM> is performed as a result of receiving a save indication or a publish indication. As described herein, the environment data file comprises information relating to content items, environment event and action associations, and assets for inclusion in the 3D environment. Similar techniques to those described above with respect to operation <NUM> may be used to store the association in the environment data file. For example, a property of a content item may reflect the association or an environment event table may be used, among other examples.

Moving to operation <NUM>, the environment data file is stored. As an example, the environment data file is stored in an authored environment data store, such as authored environment data store <NUM> in <FIG>. In another example, the environment data file is stored using a local storage device. In some examples, at least a part of the environment data file is stored using the local storage device, while another part of the environment data file is stored by the authored environment data store. It will be appreciated that any of a variety of techniques may be used to store the environment data store. Flow terminates at operation <NUM>.

<FIG> illustrates an overview of an example method <NUM> for the contextual processing of a user input in a three-dimensional environment. In examples, aspects of method <NUM> are performed by an authoring application or a viewer application, such as authoring application <NUM> or viewer application <NUM> in <FIG>. For example, a user input processing engine may be used, such as user input processing engine <NUM> in <FIG>. The authoring / viewer application may be a web-based application and/or a native application executing on a computing device, such as computing device <NUM> or <NUM> in <FIG>.

Method <NUM> begins at operation <NUM>, where a user selection of an environment data file is received. As an example, the environment data file is selected by a user browsing a webpage, wherein a link on the webpage directs a web browser to the environment data file. As another example, a user accesses the environment data file using a file browser, or selects the environment data file from a list of authored environment data files (e.g., as may be stored by an authored environment data store, such as authored environment data store <NUM> in <FIG>). While example user selections are discussed herein, it will be appreciated that other user selections may be received in other examples.

At operation <NUM>, a 3D environment is generated based on the selected environment data file. The generated 3D environment comprises one or more content items, as may be specified by the selected environment data file. In examples, the environment data file comprises references and/or data relating to the content items, as well as locations in the 3D environment at which the content items are displayed. As described above, a 3D environment comprises other assets, such as a structure and a background, among other examples. Accordingly, operation <NUM> may comprise accessing such assets and incorporating them into the 3D environment.

Moving to operation <NUM>, a user input is received for the 3D environment. In examples, the user input is received from an input device of the computing device. For example the input device may be wired, wireless, or a combination thereof. Example input devices include, but are not limited to, a mouse, a keyboard, a touchscreen, a game controller, or a physical gesture recognition device, among other examples. It will be appreciated that an input device may recognize other input aside from physical movement of the user. For example, an input device may process speech input.

At operation <NUM>, an environment event is generated based on the received user input. In examples, the environment event is generated using a user input processing engine, such as user input processing engine <NUM> in <FIG>. In some examples, a mapping is used to identify an environment event associated with the received user input. In another example, a user preference is evaluated to determine an environment event that was associated with the user input by the user. While example techniques for determining an environment event from a user input are described, it will be appreciated that other techniques may be used according to aspects described herein.

Flow progresses to operation <NUM>, where a content item associated with the user input is determined. Aspects of operation <NUM> may be performed using a user input processing engine, such as user input processing engine <NUM> in <FIG>. In examples, determining a content item associated with the user input comprises determining whether the user input is associated with a bounding box of a content item in the 3D environment. For example, a cursor may be positioned between the bounding box of a content item and a camera associated with a view of the user into the 3D environment, such that user input associated with the cursor is determined to be associated with the content item. In another example, a user uses a VR controller to gesture in the direction of a content item, such that it is determined that the content item is the target of the input event. It will be appreciated that other detection techniques may be used according to aspects described herein. Additional example aspects are discussed below with respect to <FIG>.

At operation <NUM>, the determined environment event is provided to the determined content item, thereby causing the content item to perform the content item action associated with the environment event. For example, the environment event is provided to an event handler associated with the content item. In other examples, a callback function is associated with the environment event for the content item, such that the callback function is called as a result of determining that the content item is the target of the user input. The callback function may have been specified in the environment data file, as a result of performing aspects of method <NUM> in <FIG>. While example techniques for providing an environment event and performing an associated content item action are described herein, it will be appreciated that other techniques may be used to trigger a content item action accordingly in other examples. Flow terminates at operation <NUM>.

<FIG> illustrates an overview of an example method <NUM> for determining a content item that receives an input event based on a user input. In examples, aspects of method <NUM> are performed by an authoring application or a viewer application, such as authoring application <NUM> or viewer application <NUM> in <FIG>. In some examples, aspects of method <NUM> are performed as part of operation <NUM> of method <NUM> described above with respect to <FIG>.

Method <NUM> begins at operation <NUM>, where user input is received for a 3D environment. In examples, the user input is received from an input device of the computing device. A wide variety of input devices may be used according to aspects described herein. Flow progresses to operation <NUM>, where a bounding box associated with the user input is identified. As used herein, a bounding box is a rectangular prism that encompasses the graphical representation of the content item in the 3D environment. It will be appreciated that other geometry may be used, such as a bounding sphere or a more complex mesh associated with a content item. In an example, a cursor is positioned between the bounding box of a content item and a camera associated with a view of the user, such that user input associated with the cursor is determined to be associated with the content item. It will be appreciated that other techniques may be used, such as hit-scan techniques or iterating through locations of available content items, among other examples.

At determination <NUM>, it is determined whether one bounding box has been identified. In examples, multiple bounding boxes are associated with the user input, such as instances where there are overlapping content items in the 3D environment. Accordingly, if it is determined that only one bounding box has been identified, flow branches "YES" to operation <NUM>, where the determined environment event is provided to the content item associated with the identified bounding box, thereby causing the content item to perform the content item action associated with the environment event. Flow terminates at operation <NUM>.

However, if it is instead determined that only one bounding box has not been identified, flow instead branches "NO" to determination <NUM>, where it is determined whether multiple bounding boxes have been identified. In examples, a user input may not be associated with any bounding boxes. Accordingly, flow branches "NO" to operation <NUM>, where the user input is ignored. It will be appreciated that, in other examples, other actions may be taken when a user input is received that does not relate to any content items in the 3D environment. Flow terminates at operation <NUM>.

If it is determined at determination <NUM>, however, that multiple bounding boxes have been identified, flow instead branches "YES" to operation <NUM>, where one content item is identified from the set of potential content items associated with the identified bounding boxes based on analyzing models associated with the user input. For example, a bounding box comprising a graphical representation of the content item at the location of the user input is selected over a bounding box comprising empty space at the location of the input event. It will be appreciated that, in other examples, other techniques may be used to identify one content item from a set of potential content items, such as bounding box size or proximity to the user input.

Flow progresses to operation <NUM>, where the determined environment event is provided to the content item identified at operation <NUM>, thereby causing the content item to perform the content item action associated with the environment event. Flow terminates at operation <NUM>. Flow terminates at operation <NUM>.

<FIG> illustrate example user interface aspects for contextual input in a three-dimensional environment according to aspects described herein. As shown in <FIG>, example user interface <NUM> is of an authoring application, such as authoring application <NUM> in <FIG>. The example 3D environment comprises content items <NUM> and <NUM>. According to aspects described herein, an author may have selected content items <NUM> and <NUM> and positioned them within the 3D environment.

Example user interface <NUM> further comprises "save as draft" control <NUM>, "discard changes" control <NUM>, and "publish" control <NUM>. In examples, save as draft control <NUM> generates a draft environment data file, which may be stored locally on the computing device. In another example, the draft environment data file is stored in an authored environment data store with a flag indicating it is a draft. Accordingly, the draft 3D environment may be available to one or more authors, but may not be widely available until it is published. Discard changes control <NUM> may be used to revert any changes to the 3D environment back to a state of the 3D environment as was last saved (e.g., using save as draft control <NUM> or publish control <NUM>). Publish control <NUM> publishes the authored 3D environment for consumption by other users. For example, the environment data file is stored using an authored environment data store from which other users may access the environment data file and consume the environment data file using a viewer application.

Example user interface <NUM> further comprises object properties panel <NUM>, which enables an author to modify various properties of a selected content item. As illustrated, object properties panel <NUM> is modifying content item <NUM>. Example user interface <NUM> enables an author to specify a name <NUM> of the content item, as well as a description <NUM>. Object properties panel <NUM> further comprises primary event selector <NUM> and secondary event selector <NUM>. According to aspects described herein, primary event selector <NUM> and secondary event selector <NUM> are used to associate content item actions with environment events.

Primary event selector <NUM> is illustrated as comprising dropdown <NUM>. The "Inspect" content item action is illustrated with a checkmark, thereby indicating that the primary environment event is associated with the "Inspect" content item action. As a result, if a primary environment event is received by content item <NUM>, the "Inspect" action is performed. Secondary event selector <NUM> is similarly illustrated as comprising dropdown <NUM>, wherein the "Show Actions" action is illustrated with a checkmark to indicate that the secondary environment event is associated with the "Show Actions" content item action. Thus, if a secondary environment event is received by content item <NUM>, the "Show Actions" action is performed. While example user interface elements and techniques are described herein, it will be appreciated that other examples may be used to enable a user to associate environment events with content item actions.

Turning to <FIG>, example view <NUM> illustrates content item <NUM> performing the content item action associated with a secondary environment event. Example views <NUM>-<NUM> may be of an authoring application or a viewer application, such as authoring application <NUM> or viewer application <NUM> in <FIG>. As discussed above, the associated content item action is "Show Actions. " Thus, action display <NUM> is presented as a result of a secondary environment event generated in response to a received user input from an input device. Action display <NUM> is illustrated as comprising "inspect" action <NUM> and "link to other environment" action <NUM>. In examples, an inspect action causes content item <NUM> to appear larger in the view of the user, as is discussed in greater detail with respect to <FIG>. The link to other environment action may cause a different 3D environment to be loaded and displayed to the user. While example actions are described, it will be appreciated that any of a variety of other content item actions may be provided.

Example view <NUM> in <FIG> is provided to illustrate the "inspect" action, wherein a content item is scaled to increase its size as perceived by the user. As illustrated, content item <NUM> appears larger in the user's view, while content item <NUM> is in the background. In examples, the background may be dimmed such that content item <NUM> is further emphasized. It will be appreciated that other visual effects may be used. As discussed above in <FIG>, the inspect action is performed as a result of a user actuating "inspect" action <NUM> in action display <NUM>. In another example, the inspect action is performed as a result of a primary environment event being triggered based on a received user input from an input device. <FIG> illustrated the association between the primary environment event and the inspect action in primary event selector <NUM>.

Example view <NUM> of <FIG> illustrates bounding boxes <NUM> and <NUM> of content items <NUM> and <NUM>, respectively. It will be appreciated that, in examples, bounding boxes <NUM> and <NUM> are not graphically displayed within a 3D environment but are displayed in environment <NUM> for illustrative purposes. Similar to aspects discussed with respect to methods <NUM> and <NUM> in <FIG> and <FIG>, respectively, bounding boxes <NUM> and <NUM> are evaluated in order to determine a content item to which an environment event is provided. In examples where bounding boxes <NUM> and <NUM> overlap (as may be the case if the view of the user is shifted to the left), other aspects of content items <NUM> and <NUM> may be evaluated to determine which content item receives the event. For example, one or more models of content items <NUM> and <NUM> are evaluated or the proximity of the content item to a camera associated with the user's view is evaluated, among other examples. It will be appreciated that bounding boxes <NUM> and <NUM> are provided as examples and that, in other examples, other geometry may be used, such as a bounding sphere or a more complex mesh associated with a content item.

<FIG> and the associated descriptions provide a discussion of a variety of operating environments in which aspects of the disclosure may be practiced. However, the devices and systems illustrated and discussed with respect to <FIG> are for purposes of example and illustration and are not limiting of a vast number of computing device configurations that may be utilized for practicing aspects of the disclosure, described herein.

<FIG> is a block diagram illustrating physical components (e.g., hardware) of a computing device <NUM> with which aspects of the disclosure may be practiced. The computing device components described below may be suitable for the computing devices described above, including the computing devices <NUM> and <NUM> and the 3D environment service <NUM>. In a basic configuration, the computing device <NUM> may include at least one processing unit <NUM> and a system memory <NUM>. Depending on the configuration and type of computing device, the system memory <NUM> may comprise, but is not limited to, volatile storage (e.g., random access memory), non-volatile storage (e.g., read-only memory), flash memory, or any combination of such memories.

The system memory <NUM> may include an operating system <NUM> and one or more program modules <NUM> suitable for running software application <NUM>, such as one or more components supported by the systems described herein. As examples, system memory <NUM> may store authoring application <NUM> and user input processing engine <NUM>. The operating system <NUM>, for example, may be suitable for controlling the operation of the computing device <NUM>.

Furthermore, embodiments of the disclosure may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated in <FIG> by those components within a dashed line <NUM>. The computing device <NUM> may have additional features or functionality. For example, the computing device <NUM> may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in <FIG> by a removable storage device <NUM> and a non-removable storage device <NUM>.

As stated above, a number of program modules and data files may be stored in the system memory <NUM>. While executing on the processing unit <NUM>, the program modules <NUM> (e.g., application <NUM>) may perform processes including, but not limited to, the aspects, as described herein. Other program modules that may be used in accordance with aspects of the present disclosure may include electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc..

For example, embodiments of the disclosure may be practiced via a system-on-a-chip (SOC) where each or many of the components illustrated in <FIG> may be integrated onto a single integrated circuit. Such an SOC device may include one or more processing units, graphics units, communications units, system virtualization units and various application functionality all of which are integrated (or "burned") onto the chip substrate as a single integrated circuit. When operating via an SOC, the functionality, described herein, with respect to the capability of client to switch protocols may be operated via application-specific logic integrated with other components of the computing device <NUM> on the single integrated circuit (chip). Embodiments of the disclosure may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies.

The computing device <NUM> may also have one or more input device(s) <NUM> such as a keyboard, a mouse, a pen, a sound or voice input device, a touch or swipe input device, etc. The output device(s) <NUM> such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used. The computing device <NUM> may include one or more communication connections <NUM> allowing communications with other computing devices <NUM>. Examples of suitable communication connections <NUM> include, but are not limited to, radio frequency (RF) transmitter, receiver, and/or transceiver circuitry; universal serial bus (USB), parallel, and/or serial ports.

<FIG> and <FIG> illustrate a mobile computing device <NUM>, for example, a mobile telephone, a smart phone, wearable computer (such as a smart watch), a tablet computer, a laptop computer, and the like, with which embodiments of the disclosure may be practiced. In some aspects, the client may be a mobile computing device. With reference to <FIG>, one aspect of a mobile computing device <NUM> for implementing the aspects is illustrated. In a basic configuration, the mobile computing device <NUM> is a handheld computer having both input elements and output elements. The mobile computing device <NUM> typically includes a display <NUM> and one or more input buttons <NUM> that allow the user to enter information into the mobile computing device <NUM>. The display <NUM> of the mobile computing device <NUM> may also function as an input device (e.g., a touch screen display).

If included, an optional side input element <NUM> allows further user input. The side input element <NUM> may be a rotary switch, a button, or any other type of manual input element. In alternative aspects, mobile computing device <NUM> may incorporate more or less input elements. For example, the display <NUM> may not be a touch screen in some embodiments.

In yet another alternative embodiment, the mobile computing device <NUM> is a portable phone system, such as a cellular phone. The mobile computing device <NUM> may also include an optional keypad <NUM>. Optional keypad <NUM> may be a physical keypad or a "soft" keypad generated on the touch screen display.

In various embodiments, the output elements include the display <NUM> for showing a graphical user interface (GUI), a visual indicator <NUM> (e.g., a light emitting diode), and/or an audio transducer <NUM> (e.g., a speaker). In some aspects, the mobile computing device <NUM> incorporates a vibration transducer for providing the user with tactile feedback. In yet another aspect, the mobile computing device <NUM> incorporates input and/or output ports, such as an audio input (e.g., a microphone jack), an audio output (e.g., a headphone jack), and a video output (e.g., a HDMI port) for sending signals to or receiving signals from an external device.

<FIG> is a block diagram illustrating the architecture of one aspect of a mobile computing device. That is, the mobile computing device <NUM> can incorporate a system (e.g., an architecture) <NUM> to implement some aspects. In one embodiment, the system <NUM> is implemented as a "smart phone" capable of running one or more applications (e.g., browser, e-mail, calendaring, contact managers, messaging clients, games, and media clients/players). In some aspects, the system <NUM> is integrated as a computing device, such as an integrated personal digital assistant (PDA) and wireless phone.

One or more application programs <NUM> may be loaded into the memory <NUM> and run on or in association with the operating system <NUM>. Examples of the application programs include phone dialer programs, e-mail programs, personal information management (PIM) programs, word processing programs, spreadsheet programs, Internet browser programs, messaging programs, and so forth. The system <NUM> also includes a non-volatile storage area <NUM> within the memory <NUM>. The non-volatile storage area <NUM> may be used to store persistent information that should not be lost if the system <NUM> is powered down. The application programs <NUM> may use and store information in the non-volatile storage area <NUM>, such as e-mail or other messages used by an e-mail application, and the like. A synchronization application (not shown) also resides on the system <NUM> and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in the non-volatile storage area <NUM> synchronized with corresponding information stored at the host computer. As should be appreciated, other applications may be loaded into the memory <NUM> and run on the mobile computing device <NUM> described herein (e.g., a web browser, an authoring application, a viewer application, etc.).

The visual indicator <NUM> may be used to provide visual notifications, and/or an audio interface <NUM> may be used for producing audible notifications via the audio transducer <NUM>. In the illustrated embodiment, the visual indicator <NUM> is a light emitting diode (LED) and the audio transducer <NUM> is a speaker. These devices may be directly coupled to the power supply <NUM> so that when activated, they remain on for a duration dictated by the notification mechanism even though the processor <NUM> and other components might shut down for conserving battery power. The LED may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device. The audio interface <NUM> is used to provide audible signals to and receive audible signals from the user. For example, in addition to being coupled to the audio transducer <NUM>, the audio interface <NUM> may also be coupled to a microphone to receive audible input, such as to facilitate a telephone conversation. In accordance with embodiments of the present disclosure, the microphone may also serve as an audio sensor to facilitate control of notifications, as will be described below. The system <NUM> may further include a video interface <NUM> that enables an operation of an on-board camera <NUM> to record still images, video stream, and the like.

<FIG> illustrates one aspect of the architecture of a system for processing data received at a computing system from a remote source, such as a personal computer <NUM>, tablet computing device <NUM>, or mobile computing device <NUM>, as described above. Content displayed at server device <NUM> may be stored in different communication channels or other storage types. For example, various documents may be stored using a directory service <NUM>, a web portal <NUM>, a mailbox service <NUM>, an instant messaging store <NUM>, or a social networking site <NUM>.

A user input processing engine <NUM> may be employed by a client that communicates with server device <NUM>, and/or the 3D environment service <NUM> may be employed by server device <NUM>. The server device <NUM> may provide data to and from a client computing device such as a personal computer <NUM>, a tablet computing device <NUM> and/or a mobile computing device <NUM> (e.g., a smart phone) through a network <NUM>. By way of example, the computer system described above may be embodied in a personal computer <NUM>, a tablet computing device <NUM> and/or a mobile computing device <NUM> (e.g., a smart phone). Any of these embodiments of the computing devices may obtain content from the store <NUM>, in addition to receiving graphical data useable to be either pre-processed at a graphic-originating system, or post-processed at a receiving computing system.

<FIG> illustrates an exemplary tablet computing device <NUM> that may execute one or more aspects disclosed herein. In addition, the aspects and functionalities described herein may operate over distributed systems (e.g., cloud-based computing systems), where application functionality, memory, data storage and retrieval and various processing functions may be operated remotely from each other over a distributed computing network, such as the Internet or an intranet. User interfaces and information of various types may be displayed via on-board computing device displays or via remote display units associated with one or more computing devices. For example, user interfaces and information of various types may be displayed and interacted with on a wall surface onto which user interfaces and information of various types are projected. Interaction with the multitude of computing systems with which embodiments of the invention may be practiced include, keystroke entry, touch screen entry, voice or other audio entry, gesture entry where an associated computing device is equipped with detection (e.g., camera) functionality for capturing and interpreting user gestures for controlling the functionality of the computing device, and the like.

As will be understood from the foregoing disclosure, one aspect of the technology relates to a system comprising: at least one processor; and memory storing instructions that, when executed by the at least one processor, causes the system to perform a set of operations. The set of operations comprises: generating a three-dimensional (3D) environment comprising a first content item, wherein the first content item is associated with a first content item action; receiving a first user input event from a first input device; generating an environment event from a set of environment events for the 3D environment, wherein the environment event is associated with the first user input event from the first input device; determining the first user input event is for the first content item; and based on determining that the first user input event is for the first content item, causing, using an association between the environment event and the first content item action, the first content item action to be performed by the first content item. In an example, determining the first user input event is for the first content item comprises evaluating the first user input event based on a bounding box associated with the first content item. In another example, the set of operations further comprises: receiving, from a second input device, a second user input event, wherein the second user input event is different from the first user input event; and generating the environment event based on an association between the environment event the first user input event. In a further example, the 3D environment further comprises a second content item associated with a second content item action, and the set of operations further comprises: receiving an indication from the first content item; based on the received indication: generating another environment event; and providing the another environment event to the second content item, thereby causing the second content item action to be performed. In yet another example, determining the first user input event is for the first content item comprises: identifying a first bounding box associated with the first content item and a second bounding box associated with a second content item as both being associated with the first user input event; and determining, based on evaluating a first model associated with the first content item and a second model associated with the second content item, that the first user input event is for the first content item. In a further still example, determining the first user input event is for the first content item comprises: identifying a first bounding box associated with the first content item and a second bounding box associated with a second content item as both being associated with the first user input event; and determining, based on the first content item being closer to a camera associated with a user's view than the second content item, that the first user input event is for the first content item. In another example, the 3D environment is generated from an environment data file comprising: the first content item; and an association of the first content item action with the environment event.

In another aspect, the technology relates to a method for contextual input in a three-dimensional (3D) environment. The method comprises: generating a 3D environment comprising: a first content item associated with a first content item action; and a second content item associated with a second content item action; receiving a first user input event from a first input device; generating an environment event from a set of environment events for the 3D environment, wherein the environment event is associated with the first user input event from the first input device; determining whether the first user input event is for the first content item or the second content item; when it is determined that the first user input event is for the first content item, providing the generated environment event to the first content item, thereby causing the first content item action to be performed; and when it is determined that the first user input event is for the second content item, providing the generated environment event to the second content item, thereby causing the second content item action to be performed. In an example, determining whether the first user input event is for the first content item or the second content item comprises evaluating the first user input event based on: a first bounding box associated with the first content item; and a second bounding box associated with the second content item. In another example, the method further comprises: receiving, from a second input device, a second user input event, wherein the second user input event is different from the first user input event; and generating the environment event based on an association between the environment event the first user input event. In a further example, the method further comprises: receiving an indication from the first content item; based on the received indication: generating another environment event; and providing the another environment event to the second content item, thereby causing the second content item action to be performed. In yet another example, determining whether the first user input event is for the first content item or the second content item comprises: identifying a first bounding box associated with the first content item and a second bounding box associated with a second content item as both being associated with the first user input event; and determining, based on the first content item being closer to a camera associated with a user's view than the second content item, that the first user input event is for the first content item. In a further still example, the 3D environment is generated from an environment data file comprising: the first content item; and an association of the first content item action with the environment event.

In another aspect, the technology relates to another method for or contextual input in a three-dimensional (3D) environment. The method comprises: generating a 3D environment comprising a first content item, wherein the first content item is associated with a first content item action; receiving a first user input event from an input device; generating an environment event from a set of environment events for the 3D environment, wherein the environment event is associated with the first user input event from the first input device; determining the first user input event is for the first content item; and based on determining that the first user input event is for the first content item, causing, using an association between the environment event and the first content item action, the first content item action to be performed by the first content item. In an example, determining the first user input event is for the first content item comprises evaluating the first user input event based on a bounding box associated with the first content item. In another example, the method further comprises: receiving, from a second input device, a second user input event, wherein the second user input event is different from the first user input event; and generating the environment event based on an association between the environment event the first user input event. In a further example, the 3D environment further comprises a second content item associated with a second content item action, and the method further comprises: receiving an indication from the first content item; based on the received indication: generating another environment event; and providing the another environment event to the second content item, thereby causing the second content item action to be performed. In yet another example, determining the first user input event is for the first content item comprises: identifying a first bounding box associated with the first content item and a second bounding box associated with a second content item as both being associated with the first user input event; and determining, based on evaluating a first model associated with the first content item and a second model associated with the second content item, that the first user input event is for the first content item. In a further still example, determining the first user input event is for the first content item comprises: identifying a first bounding box associated with the first content item and a second bounding box associated with a second content item as both being associated with the first user input event; and determining, based on the first content item being closer to a camera associated with a user's view than the second content item, that the first user input event is for the first content item. In another example, the 3D environment is generated from an environment data file comprising: the first content item; and an association of the first content item action with the environment event.

Claim 1:
A system comprising:
at least one processor; and
memory storing instructions that, when executed by the at least one processor, causes the system to perform a set of operations, the set of operations comprising:
associating (<NUM>), using an authoring application, a first content item action of a first content item with an environment event, wherein the environment event is a predefined event of a three-dimensional, 3D, environment, which is associated with a first input event from a first input device;
generating (<NUM>) and storing (<NUM>) an environment data file comprising the association between the first content item action and the environment event;
receiving (<NUM>) a user selection of the environment data file;
generating (<NUM>) the 3D environment comprising the first content item based on the environment data file;
receiving (<NUM>) the first user input event from the first input device;
generating (<NUM>) the environment event associated with the first user input event from the first input device;
determining (<NUM>) the first user input event is for the first content item; and
based on determining that the first user input event is for the first content item, causing (<NUM>), using the association between the environment event and the first content item action, the first content item action to be performed by the first content item.