Methods And Systems For Generating And Displaying Three

Dimensional Digital Assets For Use In An Online Environment

Cross Reference to Related Applications

[0001] This application claims priority from U.S. Patent Application No. 15/209,679, filed on July 13, 2016, titled "Methods And Systems For Generating Digital Smart Objects For Use In A Three Dimensional Environment," filed on July 13, 2016, and U.S. Patent Application No. 15/209,688, titled "Methods And Systems For Displaying Digital Smart Objects In A Three Dimensional Environment," filed on July 13, 2016. The contents of the above disclosed applications are incorporated by reference in their entirety herein.

Technical Field

[0002] Embodiments of the present invention relates generally to the field of three

dimensional environments. More particularly, embodiments of the invention relate to generation of three dimensional digital assets that can be used for data collection purposes, in a three dimensional environment, for advertisers, data analysts, developers, or educationalists/trainers in a variety of fields.

Background of the Invention

[0003] Digital advertising currently requires creating specific and customized content (e.g., images, videos, text, etc.) for each advertiser individually, and placing them directly at various forms of digital platforms (e.g., websites, games, etc.). Furthermore, such advertising often relies on Hypertext Transfer Protocol (HTTP) based cookies. An HTTP cookie, also known as a web cookie or browser cookie, is data sent from a server and stored at a client's machine comprising information related to the user's choices so that only relevant ads are transmitted to the user. Conventionally, once the user visits a website/web-page, a third party cookie is saved locally at the client machine and each time the client revisits the webpage/website the cookie is transmitted back to the third party server. Furthermore, such systems require that the advertiser provide content for the advertisement, however, the advertiser has no control where or how the content would be displayed, except for providing keywords to the advertising system. [0004] However, such advertising systems often result in ineffective advertising due to the inherent limitations of keyword based advertising. Furthermore, fake or mistaken clicks occur regularly, which are further detrimental to the advertiser's interest. Such systems have no means of determining, in advance, if its advertising at a publisher's digital platform would generate in meaningful results. Thus, conventional advertising platforms often result in wasteful and inefficient advertising. Therefore, efficient systems, methods, and techniques are needed that allow a developer, publisher, or advertiser to overcome these limitations without the use of cookies. Such systems should further permit the developer or publisher to provide information that can help an advertiser determine the intended audience of the publisher's content.

Summary of Invention

[0005] Using various embodiments, methods and systems are disclosed to generate three dimensional (3D) digital assets, referred to as smart objects or digital smart objects herein, for use in various digital platforms. 3D digital smart objects, in one embodiment, can be used to generate generic content (banner/billboard, videos, and/or 3D assets) that can optionally be replaced with branded content from an advertiser within a variety of digital platforms and measure the user performance with both the generic and branded content across the digital platform. In one embodiment, a 3D digital smart object comprises an asset encompassed in a transparent 3D asset placeholder that dictates the maximum X-Axis, Y-Axis, and Z-Axis dimensions of an asset/object and/or and understands the scaling dimensions that takes up a specific shape in a 3D digital environment. The asset within the 3D asset placeholder provides a visual representation of the 3D digital smart object. The asset can be, in one embodiment, a 3D representation of geometric data, where the asset within the 3D asset placeholder provides a visual representation of the 3D digital smart object. A 3D digital smart object comprises an asset that can be any media content such as, 3D non-active assets, assets, video, audio, multimedia object, any general 3D representation of geometric data, or a combination thereof. In various embodiments, 3D digital smart objects can be used for services related to advertising, notification, or generally for any service that can personalize a viewer's environment with 3D content that is relevant to each viewer.

[0006] In one embodiment a digital smart object generation system can be configured to present a 3D placeholder to a publisher/game developer of a 3D environment and receive an asset the publisher to be placed within the 3D placeholder. Throughout this disclosure developer and publisher refer to the digital platform creator, and have been used interchangeably. The developer can further select an asset category and/or asset type related to the asset, using which data related to the 3D digital smart object would be cataloged in a repository or database. In one embodiment, the asset category and asset type can assist the system and/or an advertiser using the system in determining the relevancy of the 3D digital smart object to a viewer. Once the asset is uploaded, the system can then associate the developer or publisher's selected asset category and/or asset type with the uploaded asset. The digital smart object generation system can also receive standard asset size information of the asset within the 3D asset placeholder; the standard asset size information includes an X-axis, Y-axis, and Z-axis dimension of the asset within the 3D asset placeholder. The standard asset size information provides the maximum 3D size of the asset that can be accommodated within the 3D asset placeholder without disturbing the aspect ratio of the asset, as determined suitable by the developer or publisher. In one embodiment, the 3D placeholder can be a cube. However, the 3D placeholder is not limited to any particular geometrical shape. For example, in various embodiments, the 3D placeholder can be a polyhedron, cylinder, sphere, cone, torus based structure, or a combination thereof. Further, the standard asset size information, in one embodiment, can be determined when the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D asset placeholder. This can be achieved when the developer places a 3D asset in the 3D asset placeholder and scales the asset so that at least one of the dimensions of the asset equals to that of the 3D placeholder. In one embodiment, such scaling of the asset can be achieved when the developer clicks and drags the asset to maximize the asset size within the 3D asset placeholder.

7] A system using the techniques described herein can also be configured to receive (or provide) the asset a position positioning information including asset orientation information and asset position anchor location. The asset position anchor location determines the location of the asset relative to the 3D asset placeholder, while the asset orientation determines the orientation of the asset itself (e.g., vertical, horizontal, etc.); the asset position anchor location in one embodiment can be the X-axis coordinates, the Y- axis coordinates, the Z-axis coordinates, or a combination thereof, of the 3D asset placeholder. The asset position anchor location is the axis of the 3D asset placeholder that acts as a base axis for the asset (in other words, the asset's orientation is relative to the selected axis of the 3D placeholder). In such an embodiment, the anchor location can be provided by the developer, or can be defaulted to a certain axis (e.g., X-axis). An X-axis coordinates based anchor position (e.g, in a lxlxl cube, a (0.5,0,0) based anchor position would indicate that the anchor is positioned on in the middle of the X-axis of the placeholder, with the X-axis as a base position). A Y-Axis based anchor position would indicate that the anchor is positioned on the Y-axis of the placeholder (e.g, in a lxlxl cube, a (0,0.5,0) based anchor position would indicate that the anchor is positioned on in the middle of the Y-axis of the placeholder, with the Y-axis as a base position). A Z-axis based anchor position would indicate the depth of the anchor position within the placeholder (e.g, in a lxlxl cube, a (0,0,0.5) based anchor position would indicate that the anchor is positioned on the middle of the Z-axis of the placeholder, with the Z-axis as a base position). Therefore, a combination of X-axis and Y-axis coordinates (e.g., 0.5, 0.5, 0.5) would indicate that the placeholder is an anchor position location, that is hanging in the center of the 3D placeholder. In one embodiment, an anchor position location can assist the developer implementing the digital smart object the creator's intention how the object should be placed within the 3D environment. In another embodiment, the anchor position location can also govern the orientation of the asset when a user/viewer interacts with the digital smart object.

8] In one embodiment, after the above mentioned information is received by the system, the system can be further configured to store the digital smart object data, including the asset, standard asset size information, asset positioning anchor location, a maximum and minimum polygon count value associated with the asset (when available), and asset data (category and/or type) in a repository. Using the digital smart object data, the system can then further be configured to generate the 3D digital smart object that can be placed within various 3D environments (e.g., games, Virtual Reality environments, Augmented Reality environments, Smartphone Applications ("Apps"), Digital TV (OTT), Web Interfaces, Game Consoles, Video, etc.), and can be associated with advertisements that are to be analyzed. The 3D digital smart object can also record different types of interaction of the 3D digital smart object with a user of the game and transmit user interaction information to the computing device with the use of event triggers (by associating the digital smart object data with the event triggers during generation of the 3D digital smart object). In one embodiment, event triggers are capable of determining user interaction with, or viewability of, a 3D digital smart object and transmit metrics, based on the user interaction (or viewability), to a digital smart object processing system. In one embodiment, the event triggers transmit user interaction including (but not limited to) determining a user viewing a 3D digital smart object, the user interacting with a 3D digital smart object, a distance between the user and a 3D digital smart object, a percentage size of a 3D digital smart object in relationship to the size of the user interface, a period of time that the user interacted with a 3D digital smart object, the percentage of the 3D digital smart object that was viewable on the user's screen (e.g., is the viewable surface of 3D digital smart object 50% below the screen), etc. In one embodiment, event triggers can be configured or customized by the publisher or the advertiser.

[0009] In another embodiment, the 3D placeholder can be presented to the developer via an Application Program Interface (API) or a software development kit (SDK). In one embodiment, the asset uploaded for a 3D digital smart object by the publisher can be a generic 3D representation of geometric data. Such a 3D digital smart object is referred to as Generic Digital smart object (GSO) herein. In another embodiment, an advertiser can replace the generic 3D asset with a branded 3D asset/object associated with the advertiser in a GSO. In such an embodiment, the publisher of the GSO can define a minimum and/or maximum polygon count value for the asset that is allowed within the GSO. An advertiser who wishes to have a generic 3D asset in a GSO to be replaced with a branded object would have to provide the branded object that is within the minimum and maximum polygon count value defined by the publisher. Such a 3D digital smart object (with a branded object/asset) is referred to as Branded Digital smart object (BSO) herein. In one embodiment, defining a minimum and/or maximum polygon count value assists in generating an advertisement standard that can allow of a GSO be converted into a BSO programmatically. In another embodiment, the publisher can further identify the types of different branded objects that can replace the asset by identifying the asset category and/or asset type, as discussed herein. In one embodiment, the digital smart object data can further associated with publisher identification data associated with the developer. In another embodiment, the digital smart object data can also be associated with advertiser identification data associated with an advertiser.

[0010] In other embodiments, methods and systems are disclosed to display three

dimensional (3D) digital assets, referred to as smart objects or digital smart objects herein, in various 3D environments (e.g., games, Virtual Reality environments,

Augmented Reality environments, Smartphone Applications ("Apps"), Digital TV (OTT), Web Interfaces, Game Consoles, Video, etc.), and can be associated with advertisements that are to be analyzed. Although certain embodiments are discussed within a gaming environment, a person having ordinary skill in the art would appreciate that the techniques described herein can be implemented in any 3D environment. Furthermore, a game, as referred herein this document, can be any 3D interactive environment. Similarly, a game engine, as referred herein, can be any rendering engine suitable for its respective 3D environment; game development environment, as referred herein, can be any 3D development environment, as known to a person having ordinary skill in the art.

[0011] In one embodiment, a system implementing the techniques described herein can

receive a request to present the 3D digital smart object in a game development environment of a game engine. In one embodiment, the 3D digital smart object can be enclosed in a 3D placeholder. In one embodiment, the 3D placeholder can be a transparent cube. The system can further be configured to retrieve 3D digital smart object data from an asset repository. The 3D digital smart object data can be associated with an asset category and asset type. In one embodiment, the 3D digital smart object data can include an asset, asset anchor location, and standard asset size information of the asset in a 3D space. In another embodiment, the 3D digital smart object data can further include a minimum and/or maximum polygon count value of the asset. In one embodiment, the asset can be a generic representation of an object or shape. In another embodiment the asset can be a branded representation of an object or shape. In yet another embodiment, the asset can be replaced with a branded representation of another object or shape.

[0012] In one embodiment, the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder. The standard asset size information can also include an X-axis, Y-axis, and Z-axis dimension of the asset. In one embodiment, the standard asset size information can be determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder.

[0013] The system can further be configured to transmit the 3D digital smart object data to the game development environment of the game engine, and receive a position location for the 3D digital smart object in the online game. In one embodiment, the position location includes an X-axis, Y-axis, and Z-axis coordinates of a location within a scene of the game where the 3D digital smart object is intended to be placed. The system can also receive scaling information related to the 3D digital smart object. In one embodiment, the scaling information provides a factor for each coordinate of the 3D digital smart object. The factor determines the relative size of the 3D digital smart object in a game scene of the game. The system can then store, into an asset repository, the position location, and scaling information related to the 3D digital smart object displayed in the game. The 3D digital smart object can be displayed at the position location when a player is interacting with the game at the game scene.

[0014] In yet another embodiment, the 3D digital smart object can be placed within a game and associated with advertisements that are to be analyzed. In this embodiment, the 3D digital smart object can record different types of interaction of the 3D digital smart object with a user of the game and transmit user interaction information to the system.

[0015] Further, in another embodiment, the 3D digital smart object can be placed within any 3D environment (e.g., 3D virtual environment for commercial and/or residential Real estate). A person having ordinary skill in the art would appreciate that in this

embodiment, the 3D digital smart objects can transmit user interaction/viewability information based on a user's browsing the virtual environment. In another embodiment, the user can interact with a 3D digital smart object from within (that is, from inside the smart object). For example, in a real estate 3D environment (where the game is an interactive environment displaying a 3D view of at least one property), different rooms throughout the real estate property can be a smart object whereas the system records and transmits the overall time spent a user had in each room.

Brief Description of Drawings

[0016] The present invention is illustrated by way of example and not limitation in the

figures of the accompanying drawings in which like references indicate similar elements.

[0017] FIG. 1 illustrates a block diagram of a general system architecture that can generate and implement 3D digital smart objects to process advertising related relevant information, according to one embodiment of the present invention.

[0018] FIG. 2 illustrates a block diagram of generating a 3D digital smart object, according to one embodiment of the present invention. [0019] FIG. 3 illustrates a block diagram of the generation of a 3D digital smart object while providing a horizontal orientation, according to one embodiment of the present invention.

[0020] FIG. 4 illustrates a block diagram of the data associated with a 3D digital smart

object, according to one embodiment of the present invention.

[0021] FIG. 5 illustrates a block diagram of a system that generates 3D digital smart objects, according to an embodiment of the present invention.

[0022] FIG. 6 illustrates the asset positioning anchor of 3D digital smart objects, according to one embodiment of the present invention.

[0023] FIG. 7 illustrates a flow chart of a method by a system to generate a 3D digital smart object, according to one embodiment of the present invention.

[0024] FIG. 8 illustrates a flow chart of a method implemented by a client machine to

generate a 3D digital smart object, according to one embodiment of the present invention.

[0025] FIG. 9 illustrates a flow chart of generating a branded digital smart object from a generic digital smart object by a system, according to one embodiment of the present invention.

[0026] FIG. 10 is a block diagram illustrating a data processing system such as a computing system which can be used with an embodiment of the present invention.

[0027] FIG. 11 illustrates displaying a 3D digital smart object in a three dimensional

environment by a publisher, according to one embodiment of the present invention.

[0028] FIG. 12 illustrates describing the operations of a system implementing a 3D digital smart object in a three dimensional environment, according to one embodiment of the present invention.

[0029] FIG.13 illustrates the operations of an advertiser replacing a generic asset of a 3D digital smart object with a branded asset, according to one embodiment of the present invention.

[0030] FIG. 14 illustrates the implementation of a branded 3D digital smart object in a three dimensional environment, according to one embodiment of the present invention. [0031] FIG. 15 illustrates a block diagram describing a 3D digital smart object processing system receiving data from a three dimensional environment, according to one embodiment of the present invention.

[0032] FIG. 16 illustrates the operations of displaying a 3D digital smart object in a game development environment.

[0033] FIG. 17 illustrates the operations of receiving user engagement actions related to a 3D digital smart object by a 3D digital smart object placement system, according to one embodiment of the present invention.

[0034] FIG. 18 illustrates the operations of receiving user engagement data by a 3D digital smart object processing system, according to one embodiment of the present invention.

Description of Embodiments

[0035] Various embodiments and aspects of the inventions will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative of the invention and are not to be construed as limiting the invention. Numerous specific details are described to provide a thorough understanding of various embodiments of the present invention. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of embodiments of the present inventions.

[0036] Reference in the specification to "one embodiment" or "an embodiment" or

"another embodiment" means that a particular feature, structure, or characteristic described in conjunction with the embodiment can be included in at least one embodiment of the invention. The appearances of the phrase "in one embodiment" in various places in the specification do not necessarily all refer to the same embodiment. The processes depicted in the figures that follow are performed by processing logic that comprises hardware (e.g., circuitry, dedicated logic, etc.), software, or a combination of both. Although the processes are described below in terms of some sequential operations, it should be appreciated that some of the operations described can be performed in a different order. Moreover, some operations can be performed in parallel rather than sequentially. [0037] FIG. 1 illustrates a block diagram of a general system architecture that can generate and implement 3D digital smart objects to process advertising related relevant information, according to one embodiment of the present invention. As illustrated, publisher or developer can, using publisher interface 102, request the digital smart object generation system 106 to create 3D digital smart object 101, as described further herein.

The digital smart object generation system 106 can request the publisher's input to provide digital smart object data 122, and save it in database 121. Digital smart object generation system 106 can interact with the developer using various 3D environments (e.g., games, Virtual Reality environments, Augmented Reality environments,

Smartphone Applications ("Apps"), Digital TV (OTT), Web Interfaces, Game Consoles,

Videos, etc.). Generally, a 3D environment intending to implement the techniques described herein would need to provide SDK(s), API(s), or any other means using which digital smart object generation system can interact with the 3D environment's development interface. Thus, in one embodiment, publisher interface 102 can be a game development environment (e.g., Unity® engine, Unreal® engine, Adobe® Air, etc.). In another embodiment, publisher interface 102 can be any 3D development environment, as known to a person having ordinary skill in the art. However, it should be noted, the invention described herein is not intended to be limited to any particular 3D development environment.

[0038] After 3D digital smart object 101 has been generated, the publisher can request the 3D digital smart object 101 be placed in an 3D environment by requesting the digital smart object placement system 108, using a SDK or API set provided to the developer by the 3D environment. In another embodiment, a system administrator of the digital smart object generation system 106 can generate predetermined digital smart objects that can be directly placed by the developer using digital smart object placement system 108.

Generally, digital smart object placement system 108 can be any computing engine that can interact with a 3D environment and determine the location (within the environment) where the 3D digital smart object has been placed by the developer/publisher, and save it as placement data. Digital smart object placement system 108 can further associate the placement data of 3D digital smart object 101 in a 3D environment with 3D environment identification data that identifies the digital platform using 3D digital smart object 101. In one embodiment, 3D digital smart object can be a GSO. After 3D digital smart object 101 is placed in the 3D environment, an advertiser, in one embodiment, using advertiser interface 104 can interact directly with digital smart object generation system 106 (represented with dashed line in Fig. 1) to replace the publisher provided asset with a branded asset to generate a BSO. In another embodiment, advertiser interface 104 can indirectly interact with digital smart object generation system 106 via digital smart object placement system 108. In yet another embodiment, the developer/publisher can provide the system with a branded asset (instead of a generic asset) to generate a BSO.

[0039] After the placement of 3D digital smart object 101 into the 3D environment, user interaction or viewability based metrics generated from 3D digital smart object 101 can be generated via digital smart object processing system 110. In one embodiment, digital smart object processing system 110 can be any system that is capable of analyzing information received from 3D digital smart object 101 and generate metrics related to any user interaction, including tapping, touching, moving, viewing (e.g., from a distance), requesting detailed description, etc., of mart object 101, via user interface 112. The generated metrics can be useful to advertiser and/or publisher associated with the 3D environment.

[0040] Various exemplary embodiments of implementing 3D digital smart object 101 in a 3D environment, are disclosed in U.S. Patent Application No. 15/209,688, filed concurrently with the instant application, can be employed, in whole or in part, with the present invention. As a result, the above-identified disclosures are incorporated herein by reference in their entirety and the contents of which are replicated along with Figures 11- xx herein.

[0041] FIG. 2 illustrates a block diagram of generating a 3D digital smart object by a

publisher associated with a 3D environment, according to one embodiment of the present invention. In one embodiment, as illustrated at 201, the publisher registers with the digital smart object generation system. At 203, the publisher logs in to generate 3D digital smart object 101 for use in an 3D environment and a 3D placeholder can be presented to the publisher. At 205, publisher selects to create 3D digital smart object 101 and a 3D placeholder is presented to the publisher via an API or SDK of the digital smart object generation system 106. At 209, the publisher uploads an asset to use as a 3D geometrical representation of 3D digital smart object 101. The asset in one embodiment, can be a generic 3D representation of geometric data, and the asset within the 3D placeholder provides a visual representation of the 3D digital smart object to be generated. For example, in one embodiment, the user can browse files 210A, and then select an asset 210B (e.g., beverage can), as the intended representation object of 3D digital smart object 101. In one embodiment, once digital smart object generation system 106 receives asset 210C from the publisher, asset 210C is previewed inside a 3D placeholder 210D to the publisher. At 211, the developer is given the opportunity to provide an asset category and/or type that would be associated with the uploaded asset. The asset category and/or type, can also be used for cataloging 3D digital smart object 101. For example, in one embodiment, at 212A, the publisher can select asset data, including an asset type category as 'beverage' and at 212B the asset type, in this embodiment, can be a 'beverage can'. In an alternative embodiment, the developer/ publisher can also provide a minimum and maximum polygon count of the asset. Such standardization can be assist the publisher to ensure only the intended resolution and or size of the asset is used, in case the asset is replaced by a branded asset. This standardization also ensures that the branded asset, if it replaces an asset in a GSO, preserves the quality and load time as intended by the developer/publisher of the GSO. In one embodiment, the developer/publisher can upload a branded asset to directly create a BSO. The selected asset along with asset data (including asset category and asset type related to the asset), and/or minimum/maximum asset polygon count value, as provided by the publisher/developer, is received by digital smart object generation system 106. In one embodiment, the minimum and maximum asset polygon count value is optional, and in certain embodiments, a polygon count value based constraint may not be required at all. The system then associates the asset with an asset identification in database 121.

2] Thereafter, as illustrated at 213, the publisher is requested to provide a standard asset size information of asset 210C located in 3D placeholder 210D. In one embodiment, the standard asset size information that includes an X-axis, Y-axis, and Z-axis dimension of the asset (as intended to represent 3D digital smart object 101). An asset generally provides the visual representation of 3D digital smart object 101. In one embodiment, the standard size information of asset 2 IOC can be provided by the publisher by clicking on asset 210C, and dragging the asset boundary markers to maximize the size of asset 210C within 3D placeholder 210D. This usually means at least one dimension (X-axis, Y-axis, or Z-axis) of asset 210C is equal to the corresponding axis of 3D placeholder 210D. This creates a standard object size for the associated asset category and/or asset type. In one embodiment, 3D Digital smart object 101 encompasses asset 210C in a transparent 3D placeholder cube 210D, where the 3D placeholder cube 210D dictates the maximum XYZ dimensions of an object that takes up a specific space in a 3D environment.

[0043] As illustrated as 216, the system requests the publisher to provide asset position

information of 3D digital smart object 101, in one embodiment. The asset positioning information includes an anchor positioning location 214 and an asset orientation (not shown). The anchor positioning location, in one embodiment, can be the X-axis coordinates, Y-axis coordinates, Z-axis coordinates, or a combination thereof, of the 3D placeholder; the asset orientation is the desired orientation of the asset selected by publisher. For example, as illustrated in fig. 2, asset 2 IOC is illustrated to have a vertical orientation and the asset anchor positioning location 214A is shown to be located on the

X-axis. In one embodiment, the anchor positioning location determines how the asset is positioned within 3D environments. Anchor positioning location 214 indicated as X-axis signifies that the asset is grounded or the determined orientation is relative to the X-axis in the 3D environment. Anchor positioning location 214 indicated as Y-axis signifies that the asset is grounded or the determined orientation is relative to the Y-axis in the 3D environment. Anchor positioning location 214 indicated as a combination of X-axis coordinate, Y-axis coordinate, and Z-axis coordinate values of the 3D placeholder can signify, in one embodiment that the asset anchor is hanging within the 3D placeholder. Similarly, an orientation position of the asset can be selected with respect to the axis of the 3D placeholder. In yet another embodiment, the asset orientation can be requested from the publisher after providing the standard asset size information at 213. As illustrated at 215, the system displays 3D digital smart object data 101 to the user, and at 217 saves and associates the digital smart object data received from the publisher, including the asset, standard asset size information, asset positioning information, and asset data in repository 121. After 3D digital smart object data is saved, the publisher can edit or review the data, as illustrated at 207. In one embodiment, the 3D digital smart object can now be placed within an 3D environment and associated with data collection activities that measure the user's response, viewability, and/or interaction with the 3D digital smart object.

[0044] FIG. 3 illustrates a block diagram of the generation of a 3D digital smart object while providing a horizontal orientation, according to one embodiment of the present invention. As illustrated in fig. 2, in one embodiment, at 203, the publisher logs in to generate 3D digital smart object 101 for use in an 3D environment. At 205, publisher selects to create 3D digital smart object 101. At 209, the publisher uploads an asset to use as a 3D geometrical representation of 3D digital smart object 101. For example, in one embodiment, the user can browse files 210A, and then select an asset 210B (e.g., beverage can), as the intended representation object of 3D digital smart object 101. In one embodiment, once digital smart object generation system 106 receives asset 210C from the publisher, asset 2 IOC is previewed inside a 3D placeholder 210D to the publisher. At 211, the developer is given the opportunity to provide an asset category and/or type that would be associated with the uploaded asset. The asset category and/or type, can also be used for cataloging 3D digital smart object 101. For example, in one embodiment, at

212A, the publisher can select asset data, including an asset type category as 'beverage' and at 212B the asset type, in this embodiment, can be a 'beverage can'. At 303, the publisher can change the orientation of asset 2 IOC, as represented by horizontally oriented asset 301. At 305, the publisher can determine the asset anchor position location, and the system can thereby save digital smart object data as described above while discussing fig. 2.

5] FIG. 4 illustrates a block diagram of the data associated with a 3D digital smart object, according to one embodiment of the present invention. As illustrated 3D digital smart object 101, in one embodiment, can be associated with digital smart object identification data 401, that represents the identification of the 3D digital smart object when implemented by the publisher and can be associated with digital smart object data stored in repository 121. 3D digital smart object 101 can also be associated with publisher identification data 403 identifying the publisher who implemented the 3D digital smart object. Such identification can be helpful to assist in presenting a game developer digital smart objects only related to their associated 3D digital smart objects, since 3D digital smart objects can be configured, in one embodiment, to collect viewability metrics and transmit it back to the publisher implementing the 3D digital smart object in their 3D environment. In an alternative embodiment, 3D digital smart object 101 can also be associated with advertiser identification 405 that can be used when a GSO asset is replaced with a branded asset to generate a BSO. By associating 3D digital smart object

101 with advertiser identification 405, advertising based metrics can be transmitted to the advertiser. Although the techniques described herein are generally associated with data collection for advertisers, it should be noted, the invention generally relates to data collection using 3D digital smart objects, and is not intended to be limited for advertising purposes. Specifically, generation of 3D digital smart objects can be used for data collection purposes, in a three dimensional environment, for advertisers, data analysts, software developers (e.g., object performances in game or application development, etc.), or for training purposes in a variety of fields (e.g., medical, military, or any area that involves precision based training using a 3D environment). The data collected by the digital smart objects can then be used for data analysis to determine if a goal has been achieved. In yet another embodiment, the data analysis can be used for predictive advertisement. The goal can be different based on the field where the 3D digital smart objects are used. For example, in the advertising realm the goal can include user interaction and/or viewability with the 3D digital smart object, in medicinal or military training related tasks the goal can include determining the precise interaction (e.g., orientation, speed, etc.) the 3D digital smart object with the user, etc. In the realm of virtual reality, for example, a user's interaction with the 3D digital smart object can be measured with use of accelerometers, gyroscopes, scripts or a combination thereof.

Therefore, advertiser identification 405 can be associated with any 3rd party (who is not the publisher/developer) of the 3D digital smart object, but as a requirement to collect data from the end user's viewability or interaction with the digital smart object. For example, advertising identification data 405 can be associated with a medical training services provider, military training service provider, etc. depending on the usage of the

3D digital smart object. In one embodiment, data received from the 3D digital smart object can inform the user of their performance score/level.

6] 3D digital smart object 101 can also be associated with asset identification 409 which determines the asset representation(s) (e.g. video, image, 3D object, audio, or a combination thereof) of the 3D digital smart object. In one embodiment, Asset identification 409 can also identify if 3D digital smart object 101 is a GSO or BSO, that is, if the asset object/video/3D representation comprises a generic asset or a branded asset. Asset identification 409 can be further associated with asset category identification 407 A and/or Asset type identification 407B. In one embodiment, the publisher, while generating 3D digital smart object 101, is given a list of predetermined asset categories and/or asset type from which the publisher selects a desired category or type to associated with 3D digital smart object 101. Assigning an asset category and/or type can be useful while generating a BSO (from a GSO) because it can provide the advertiser the publisher's intended representation of 3D digital smart object 101. For example, if the publisher generates a GSO and assigns it to category 'beverage', and type 'soda can', this would suggest that a GUCCI® 'leather studded sandal' is not intended to be the branded asset of the GSO. Therefore, in one embodiment, providing an asset category and/or type can prevent ineffective advertising by informing the advertiser the intended representation of 3D digital smart object 101. Further, asset category and type can also provide the advertiser information about the intended audience of 3D digital smart object 101, since a 'soda can' based branded 3D digital smart object is more likely going to be considered appropriate to a general audience, while a leather studded sandal based branded 3D digital smart object is more likely to be considered suitable to a feminine audience between the ages of 25-50. Thus, by providing an asset category and/ or asset type, the publisher can further identify one or more categories/types of different branded objects that are intended to replace the asset in a GSO.

7] As illustrated in fig. 4, 3D digital smart object 101 can also be associated with asset positioning information (e.g., asset orientation, asset anchor position, etc.) 411 and standard object size dimensions 413, as disclosed above, herein. Further, 3D digital smart object 101 can also be associated with a maximum and/or minimum polygon count value 415. In one embodiment, when a publisher is in the process of generating 3D digital smart object 101, the publisher/developer can specify a minimum and/or maximum polygon count value 415 of the 3D asset that would be included in 3D digital smart object 101. ).

In this embodiment, an advertiser can replace the asset of a GSO with a branded object, where the branded object is related to a brand associated with the advertiser. In this embodiment, once the publisher defines a minimum and maximum polygon count value for the asset associated the 3D digital smart object (GSO), and a branded object/asset can replace the publisher provided asset only when the branded object has a polygon count within the defined minimum and maximum polygon count value. This can be helpful, among other things, to ensure fast loading 3D digital smart object 101 when it is implemented in a 3D environment. As polygon count value of a 3D asset can be directly associated with the size of the asset (in memory), setting a minimum and/or maximum polygon can assist in fast loading (or rendering) of 3D digital smart object 101 during implementation. Further, setting minimum/maximum polygon count 415 can assist the publisher in ensuring the aesthetic aspect of the 3D digital smart object is not compromised when an asset is replaced (e.g., when a GSO asset is replaced with a branded asset to convert the GSO into a BSO.

[0048] Further, 3D digital smart object 101 can also be associated with event triggers (e.g., scripts) 417. In one embodiment, the event triggers are capable of determining user interaction with, or viewability of, the 3D digital smart object. Event scripts 117, in one embodiment, can transmit data to the system that can be used to generate user viewability or interaction based metrics. In another embodiment, the event triggers transmit user interaction including determining a user looking at the 3D digital smart object, the user interacting with the 3D digital smart object, a distance between the user and the 3D digital smart object, a percentage size of the 3D digital smart object in relationship to the size of the user interface, a period of time that the user interacted with the 3D digital smart object, the percentage of the smart object seen from the user, the angle with which the 3D digital smart object was moved or lifted by the user, or the speed with which the 3D digital smart object was moved by the user, etc. Non-limiting examples of event triggers can include the events as illustrated below in table 1 :

[0049]

Event Trigger Purpose

OnClickedO; Triggers whenever the digital smart object is

tapped or clicked

GetScreenRealEstate() ; Gets screen real estate at current time and stores in array for calculating averages of the time the user could view the 3D digital smart object

IsInView(); Various calculations to determine whether object

is in view using ray casts to main camera (user focus). If actual geometry determination is not performed, this can, in one embodiment, be determined by collision detection so determination can be based on probability.

OpenDetailsQ; Provide details of the information associated with

the digital smart object (e.g., in a pop-up window). ObjectAngleO; Relative angle with which the user is interacting

with the digital smart object

UserSpeedQ; The relative speed (pixel traversed per seconds)

with which a user is moving the digital smart object

Table 1

[0050] In one embodiment, digital smart objects can also include a collision mesh (e.g., in gaming environments), which can be used to detect event triggers. Thus, digital smart objects, in one embodiment, can be used to calculate if an object is visible to a user, and if so, the percentage of the smart object viewable on the user's screen. For example, digital smart objects implemented in a gaming environment (where a collision mesh can be implemented) can determine if a mesh renderer is active, and further evaluate if a digital smart object is being drawn on the current Camera's culling mask. Thereafter, using ray casting techniques, a line between the main camera and the digital smart object can be drawn. If this line collides with a collidable mesh of the digital smart object then it can be assumed that the digital smart object is being blocked (and is viewable on the user's interface). To calculate the proportion of the digital smart object on screen, in a gaming environment, a screen bounds function (or equivalent) can be used to obtain an approximation (percentage) of the screen that the digital smart object is covering. In other environments (e.g., non-gaming environments) similar techniques can be implemented, as known to a person having ordinary skill in the art.

[0051] A person having ordinary skill in the art would appreciate that other event triggers can also be implemented, depending on the business needs of the advertiser/service provider, and/or publisher. Thus, in another embodiment, other functions specific to individual digital smart objects can also be specified (e.g., other multimedia effects within the 3D digital environment can be effected). In one embodiment, 3D digital smart object 101 can be configured to transmit the data generated by the event triggers to a digital smart object manager which can forward the information to one or more systems for metrics generation and/or further processing. In one embodiment, event triggers can be configured or customized by the publisher or advertiser/service provider, depending on their business needs. In yet another embodiment, event triggers cannot be configured or customized by the publisher or advertiser/service provider, in order to prevent advertisement metrics, viewability/interaction fraud with the 3D digital smart object. In such an embodiment, event trigger scripts can be encrypted and provided by 3D digital smart object generator 106. In this embodiment, a developer and/or advertiser can present a request to the system to generate event trigger scripts that can be customized by the developer/publisher, or can request the system to create entirely new event trigger scripts to meet specific data reporting needs of the publisher.

[0052] FIG. 5 illustrates a block diagram of a system that generates 3D digital smart objects, according to an embodiment of the present invention. In one embodiment, based on any digital smart object ID, Digital smart object generation system 106 can retrieve digital smart object data (from database 121), including asset information related to the 3D digital smart object from an associated asset ID 505, digital smart object position information, dimensions, min/max polygon count, etc. 507, and associated event trigger scripts 509. After gathering the digital smart object data, digital smart object generation system can generate (as disclosed herein) a 3D digital smart object to be implemented in various 3D environments.

[0053] FIG. 6 illustrates the asset positioning anchor of 3D digital smart objects, according to one embodiment of the present invention. As illustrated, various 3D digital smart objects 101 implemented in a 3D environment are displayed. In one embodiment, 3D digital smart object 101 can, once implemented in the 3D environment, display asset 603 with its positioning based on the defined asset position anchor 214. Position anchor, as illustrated, can be in a hanging position 601 relative to 3D placeholder 210D, anchored to the base 602 of 3D placeholder 210D, anchored to the side 603 or placeholder 210D, or a combination thereof.

[0054] FIG. 7 illustrates a flow chart of a method by a system to generate a 3D digital smart object, according to one embodiment of the present invention. As illustrated, at 701, a system implementing the method includes authorizing a publisher to upload an asset in a 3D placeholder. At 703, the system receives asset data, including asset category and asset type related to the asset. At 705, the system can further be configured to receive standard asset size information of the asset in a 3D space (e.g., X-axis, Y-axis, and Z-axis dimension of the asset). At 707, the system receives asset positioning information including anchor location and asset orientation. Thereafter, the system, at 709, receives minimum and/or maximum polygon count associated with the asset, and stores the digital smart object data received, including the asset, standard asset size information, asset positioning information ( anchor location and/or orientation), polygon count (when available), and asset data into the repository. At 713, the system can generate the 3D digital smart object by using the digital smart object data received from the publisher.

[0055] FIG. 8 illustrates a flow chart of a method implemented by a client machine to

generate a 3D digital smart object, according to one embodiment of the present invention. As illustrated, a publisher/developer instantiates generation of 3D digital smart object, at 801. At 803, the publisher provides asset data, including asset category and asset type related to the asset and uploads asset. The publisher then provides, at 805, standard asset size information of the asset in a 3D space (e.g., X-axis, Y-axis, and Z-axis dimension of the asset). At 807, the publisher determines asset positioning information, including anchor location and orientation of the asset relative to the 3D placeholder, (e.g., X-axis coordinates, Y-axis coordinates, Z-axis coordnates, or a combination thereof of the 3D placeholder). The publisher can also set minimum and/or maximum polygon count associated with the asset, at 809, and then and 811, save 3D digital smart object information.

[0056] FIG. 9 illustrates a flow chart of generating a branded digital smart object from a generic digital smart object by a system, according to one embodiment of the present invention. As illustrated, the system, after an advertiser logs into the digital smart object generation system, in one embodiment, the system displays available Generic Digital smart objects (GSOs) to an advertiser based on advertiser's selected Asset Category and/or Asset Type, at 901. At 903, the properties of a GSO set by the publisher/developer, including, standard asset size information, asset positioning information, and/or minimum/maximum polygon count, are displayed to the advertiser. At 905, the system receives an uploaded branded asset from advertiser. At 907, the system verifies that the uploaded branded asset conforms to the properties of the GSO as set by the

developer/publisher. At 900, the BSO is previewed to the advertiser and the BSO is associated with advertiser identification; the system then saves the associated data to the repository. Thereafter, once the GSO is implemented by a developer/publisher in a 3D environment, the BSO can be displayed instead of the GSO and transmit necessary data to a system capable of receiving the information (e.g., digital smart object processing system 110) to generate and process necessary metrics for the advertiser. [0057] The techniques shown in the figures can be implemented using computer program instructions (computer code) and data stored and executed on one or more electronic systems (e.g., computer systems, etc.). Such electronic systems store and communicate (internally and/or with other electronic systems over a network) code and data using machine -readable media, such as machine -readable non-transitory storage media (e.g., magnetic disks; optical disks; random access memory; dynamic random access memory; read only memory; flash memory devices; phase-change memory). In addition, such electronic systems typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices, user input/output devices (e-g-, a keyboard, a touchscreen, and/or a display), and network connections. The coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers). The storage device and signals carrying the network traffic respectively represent one or more machine -readable storage media and machine-readable communication media. Thus, the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device.

[0058] It should be apparent from this description that aspects of the present invention may be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other computer system in response to its processor, such as a microprocessor, executing sequences of instructions contained in memory, such as a

ROM, DRAM, mass storage, or a remote storage device. In various embodiments, hardware circuitry may be used in combination with software instructions to implement the present invention. Thus, the techniques are not limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the computer system. In addition, throughout this description, various functions and operations are described as being performed by or caused by software code to simplify description. However, those skilled in the art will recognize what is meant by such expressions is that the functions result from execution of the code by a processor.

[0059] FIG. 10 is a block diagram illustrating a data processing system such as a computing system 1900 which may be used with one embodiment of the invention. For example, system 1900 may be implemented as part of a system that can at least generate 3D digital smart objects using the techniques described herein. In one embodiment, system 1900 may represent digital smart object generating system 106, digital smart object placement system 108, or digital smart object processing system 110. System 1900 may have a distributed architecture having dispersed units coupled through a network, or all of its components may be integrated into a single unit. Computing system 1900 may be implemented as part of a diverse range of products implemented by Trivver, Inc.

[0060] For example, computing system 1900 may represents any of data processing systems described above performing any of the processes or methods described above. System 1900 can include many different components. These components can be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules adapted to a circuit board such as a motherboard or add-in card of the computer system, or as components otherwise incorporated within a chassis of the computer system. Note also that system 1900 is intended to show a high level view of many components of the computer system. However, it is to be understood that additional or fewer components may be present in certain implementations and furthermore, different arrangement of the components shown may occur in other implementations. System 1900 may represent a desktop, a laptop, a tablet, a server, a mobile phone, a programmable logic controller, a personal digital assistant (PDA), a personal communicator, a network router or hub, a wireless access point (AP) or repeater, a set-top box, or a combination thereof.

[0061] In one embodiment, system 1900 includes processor 1901, memory 1903, and devices 1905-1908 via a bus or an interconnect 1922. Processor 1901 may represent a single processor or multiple processors with a single processor core or multiple processor cores included therein. Processor 1901 may represent one or more general-purpose processors such as a microprocessor, a central processing unit (CPU), or the like. More particularly, processor 1901 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word

(VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 1901 may also be one or more special-purpose processors such as an application specific integrated circuit (ASIC), a cellular or baseband processor, a field programmable gate array (FPGA), a digital signal processor (DSP), a network processor, a graphics processor, a network processor, a communications processor, a cryptographic processor, a co-processor, an embedded processor, or any other type of logic capable of processing instructions. [0062] Processor 1901, which may be a low power multi-core processor socket such as an ultra-low voltage processor, may act as a main processing unit and central hub for communication with the various components of the system. Such processor can be implemented as a system on chip (SoC). In one embodiment, processor 1901 may be an Intel® Architecture Core™-based processor such as an i3, i5, il9 or another such processor available from Intel Corporation, Santa Clara, Calif. However, other low power processors such as available from Advanced Micro Devices, Inc. (AMD) of Sunnyvale, Calif., an ARM-based design from ARM Holdings, Ltd. or a MlPS-based design from MIPS Technologies, Inc. of Sunnyvale, Calif., or their licensees or adopters may instead be present in other embodiments.

[0063] Processor 1901 is configured to execute instructions for performing the operations and methods discussed herein. System 1900 further includes a graphics interface that communicates with graphics subsystem 1904, which may include a display controller and/or a display device.

[0064] Processor 1901 may communicate with memory 1903, which in an embodiment can be implemented via multiple memory devices to provide for a given amount of system memory. As examples, the memory can be in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design such as the current LPDDR2 standard according to JEDEC JESD 207-2E (published April 2007), or a next generation LPDDR standard to be referred to as LPDDR3 that will offer extensions to LPDDR2 to increase bandwidth. As examples, 2/4/8 gigabytes (GB) of system memory may be present and can be coupled to processor 1901 via one or more memory interconnects. In various implementations the individual memory devices can be of different package types such as single die package (SDP), dual die package (DDP) or quad die package (QDP). These devices can in some embodiments be directly soldered onto a motherboard to provide a lower profile solution, while in other embodiments the devices can be configured as one or more memory modules that in turn can couple to the motherboard by a given connector.

[0065] Memory 1903 can be a machine readable non-transitory storage medium such as one or more volatile storage (or memory) devices such as random access memory (RAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), static RAM (SRAM), or other types of storage devices such as hard drives and flash memory. Memory 1903 may store information including sequences of executable program instructions that are executed by processor 1901, or any other device. For example, executable code and/or data of a variety of operating systems, device drivers, firmware (e.g., input output basic system or BIOS), and/or applications can be loaded in memory 1903 and executed by processor 1901. An operating system can be any kind of operating systems, such as, for example,

Windows® operating system from Microsoft®, Mac OS®/iOS® from Apple, Android® from Google®, Linux®, Unix®, or other real-time or embedded operating systems such as Vx Works.

[0066] System 1900 may further include IO devices such as devices 1905-1908, including wireless transceiver(s) 1905, input device(s) 1906, audio IO device(s) 19019, and other

IO devices 1908. Wireless transceiver 1905 may be a WiFi transceiver, an infrared transceiver, a Bluetooth transceiver, a WiMax transceiver, a wireless cellular telephony transceiver, a satellite transceiver (e.g., a global positioning system (GPS) transceiver), or other radio frequency (RF) transceivers, network interfaces (e.g., Ethernet interfaces) or a combination thereof.

[0067] Input device(s) 1906 may include a mouse, a touch pad, a touch sensitive screen (which may be integrated with display device 1904), a pointer device such as a stylus, and/or a keyboard (e.g., physical keyboard or a virtual keyboard displayed as part of a touch sensitive screen). For example, input device 1906 may include a touch screen controller coupled to a touch screen. The touch screen and touch screen controller can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen.

[0068] Audio IO device 1907 may include a speaker and/or a microphone to facilitate voice- enabled functions, such as voice recognition, voice replication, digital recording, and/or telephony functions. Other optional devices 1908 may include a storage device (e.g., a hard drive, a flash memory device), universal serial bus (USB) port(s), parallel port(s), serial port(s), a printer, a network interface, a bus bridge (e.g., a PCI-PCI bridge), sensor(s) (e.g., a motion sensor such as an accelerometer, gyroscope, a magnetometer, a light sensor, compass, a proximity sensor, etc.), or a combination thereof. Optional devices 1908 may further include an imaging processing subsystem (e.g., a camera), which may include an optical sensor, such as a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, utilized to facilitate camera functions, such as recording photographs and video clips. Certain sensors may be coupled to interconnect 1907 via a sensor hub (not shown), while other devices such as a keyboard or thermal sensor may be controlled by an embedded controller (not shown), dependent upon the specific configuration or design of system 1900.

[0069] To provide for persistent storage of information such as data, applications, one or more operating systems and so forth, a mass storage (not shown) may also couple to processor 1901. In various embodiments, to enable a thinner and lighter system design as well as to improve system responsiveness, this mass storage may be implemented via a solid state device (SSD). However in other embodiments, the mass storage may primarily be implemented using a hard disk drive (HDD) with a smaller amount of SSD storage to act as a SSD cache to enable non- volatile storage of context state and other such information during power down events so that a fast power up can occur on RE-initiation of system activities. Also a flash device may be coupled to processor 1901, e.g., via a serial peripheral interface (SPI). This flash device may provide for non-volatile storage of system software, including a basic input/output software (BIOS) as well as other firmware of the system.

[0070] Note that while system 1900 is illustrated with various components of a data

processing system, it is not intended to represent any particular architecture or manner of interconnecting the components; as such details are not germane to embodiments of the present invention. It will also be appreciated that network computers, handheld computers, mobile phones, and other data processing systems which have fewer components or perhaps more components may also be used with embodiments of the invention.

[0071] Thus, methods, apparatuses, and computer readable medium to generate 3D digital smart objects for implementation (or use) in a 3D environment. Although the present invention has been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention as set forth in the claims. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. [0072] The description now replicates the contents of U.S. Patent Application No.

15/209,688 which is incorporated by reference herein.

[0073] Referring back to FIG. 1, FIG. 1 illustrates a block diagram of a general system

architecture that can generate and implement 3D digital smart objects to process advertising related relevant information, according to one embodiment of the present invention. 3D digital smart objects, in one embodiment, can be used to generate generic content (banner/billboard, videos, and/or 3D assets) that can optionally be replaced with branded content from an advertiser within a variety of digital platforms and measure the user performance with both the generic and branded content across the digital platform. In one embodiment, a 3D digital smart object comprises an asset encompassed in a transparent 3D asset placeholder that dictates the maximum X-Axis, Y-Axis, and Z-Axis dimensions of an asset/object and/or and understands the scaling dimensions that takes up a specific shape in a 3D digital environment. The asset within the 3D asset placeholder provides a visual representation of the 3D digital smart object. The asset can be, in one embodiment, a 3D representation of geometric data, where the asset within the 3D asset placeholder provides a visual representation of the 3D digital smart object. A 3D digital smart object comprises an asset that can be any media content such as, 3D non-active assets, assets, video, audio, multi-media object, any general 3D representation of geometric data, or a combination thereof. In various embodiments, 3D digital smart objects can be used for services related to advertising, notification, or generally for any service that can personalize a viewer's environment with 3D content that is relevant to each viewer.

[0074] After 3D digital smart object 101 has been generated, it can be placed into a three dimensional environment by 3D digital smart object placement system 108.

[0075] As illustrated, publisher or developer can, using publisher interface 102, request the 3D digital smart object placement system 108 to place 3D digital smart object 101 in a three dimensional environment, as described further herein. 3D digital smart object placement system 108 can request the publisher's input to select a 3D digital smart object (generated by 3D digital smart object generation system 106) and save the coordinates, including game identification data, , smart object identification data, smart object category/type data, publisher/developer identification data, and location/scene identification data. 3D digital smart object placement system 108 can interact with the developer using various 3D game development environments. Generally, a 3D environment intending to implement the techniques described herein would need to provide SDK(s), API(s), or any other means using which 3D digital smart object placement system 108 can interact with the 3D environment's development interface. Thus, in one embodiment, publisher interface 102 can be a game development environment (e.g., Unity® engine, Unreal® engine, Torque 3D® engine, Adobe® Air, etc.). In another embodiment, publisher interface 102 can be any 3D development environment, as known to a person having ordinary skill in the art. However, it should be noted, the invention described herein is not intended to be limited to any particular 3D development environment. Therefore, 3D digital smart object 101 has been generated by

3D digital smart object generation system 106, the publisher can request the 3D digital smart object 101 be placed in an 3D environment by requesting the 3D digital smart object placement system 108, using a SDK or API set provided to the developer by the 3D environment.

6] In another embodiment, a system administrator of the 3D digital smart object placement system 108 can present predetermined 3D digital smart objects (to the developer) that can be placed within a three dimensional environment using 3D digital smart object placement system 108. Generally, 3D digital smart object placement system 108 can be any computing engine that can interact with a 3D environment and determine the location (within the environment) where the 3D digital smart object has been placed by the developer/publisher, and save it as placement data. 3D digital smart object placement system 108 can further associate the placement data of 3D digital smart object 101 in a 3D environment with 3D environment identification data that identifies the digital platform using 3D digital smart object 101. In one embodiment, the publisher or developer can place 3D digital smart object 101 as a GSO. In another embodiment, the publisher or developer can place 3D digital smart object 101 as a BSO. When the developer/publisher places a GSO in the 3D environment, an advertiser, in one embodiment, using advertiser interface 104 can interact with 3D digital smart object placement system 108 to replace the publisher provided asset with a branded asset to generate a BSO. In yet another embodiment, the developer/publisher can provide the system with a branded asset (instead of a generic asset) to generate a BSO, which is then placed by the developer using 3D digital smart object placement system 108. [0077] After the placement of 3D digital smart object 101 into the 3D environment, user interaction or viewability based metrics generated from 3D digital smart object 101 can be generated via 3D digital smart object processing system 110. In one embodiment, 3D digital smart object processing system 110 can be any system that is capable of analyzing information received from 3D digital smart object 101 and generate metrics related to any user interaction, including tapping, touching, moving, time spent with the smart object, viewing (e.g., from a distance), requesting detailed description, etc., of smart object 101, via user interface 112. The generated metrics can be useful to advertiser and/or publisher associated with the 3D environment.

[0078] FIG. 11 illustrates displaying a 3D digital smart object in a three dimensional

environment by a publisher, according to one embodiment of the present invention. As illustrated, at 11202 a publisher or game developer logs in to the gaming environment, via publisher interface 102, the 3D digital smart object implementation system can be accessed in a 3D digital smart object developer menu via an API or SDK installed within the gaming environment. Thereafter, the publisher/ game developer, in one embodiment, can select options like viewing their data dashboard 11204, where performances of their 3D digital smart objects can be viewed and reported, create 3D digital smart object 11206, access games they are developing (or contributing towards), or access 3D digital smart objects 101 generated by the developer or publisher. 3D digital smart objects created by the developer can be generic 3D digital smart objects (GSOs) or branded 3D digital smart objects (BSOs). Generic 3D digital smart objects are 3D digital smart objects in which the asset is a generic representation of an object, location or shape. Branded 3D digital smart objects are 3D digital smart objects in which the asset is a branded representation of an object or shape.

[0079] To implement a 3D digital smart object in a game, the developer can select a game under development, and via the game engine 11213, access 3D digital smart object development interface 11212. 3D digital smart object placement system 108 presents the developer an option to select a 3D digital smart object to be placed within the game, as illustrated at 11214. In one embodiment, the publisher/developer is prompted to select an asset category and/or type to narrow (or filter) the 3D digital smart objects visible to the developer/publisher. Generally, a publisher/developer can only select system provided 3D digital smart objects and/or 3D digital smart objects created by the developer/publisher (or their team). However, in another embodiment, a developer can opt to share their 3D digital smart objects within a group or make them publically accessible. After the publisher/developer selects a 3D digital smart object 3D digital smart object placement system 108, displays the selected 3D digital smart object asset in a 3D placeholder. In one embodiment, the 3D placeholder can be a cube. The 3D digital smart object placement system 108 also retrieves and transmits 3D digital smart object data associated with the displayed asset from an asset repository, associated with the asset category and/or asset type, the 3D digital smart object data including an asset, asset position anchor location, and standard asset size information of the asset in the 3D placeholder. The asset position anchor location determines the location of the asset relative to the 3D asset placeholder, while the asset orientation determines the orientation of the asset itself (e.g., vertical, horizontal, etc.); the asset position anchor location in one embodiment can be at least the X-axis, Y-axis, or Z-axis of the 3D asset placeholder. The asset position anchor location is the axis of the 3D asset placeholder that acts as a base axis for the asset (in other words, the asset's orientation is relative to the selected axis). The anchor location can be provided by the creator of the 3D digital smart object. The standard asset size

information, in one embodiment, provides the maximum 3D size of the asset relative to the 3D placeholder, and includes an X-axis, Y-axis, and Z-axis dimension of the asset. The standard asset size information can be determined when at least one of the X-axis, Y- axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the

3D placeholder.

80] The publisher/developer can then place the 3D digital smart object at their desired location in the game scene (that is, the visible area of a scene in a game), and scale the 3D digital smart object relative to the game scene, as needed, as illustrated at 11216. In one embodiment, the developer can use the same 3D digital smart object and provide different scaling and positioning information, as further illustrated in fig. 5. At 11218, 3D digital smart object placement system 108 can then save the placement information in database 11220, including, size (scale) changes, positioning, and other arrangements to the database. 3D digital smart object placement system 108 can further associate the data with the game identification information, location (position within the game)

identification information, 3D digital smart object identification data, and publisher identification information. The position location, in one embodiment, includes an X-axis, Y-axis, and Z-axis coordinates of a location within a scene of the online game where the 3D digital smart object is intended to be placed/ viewed by a player of the game. In one embodiment, the developer/publisher can override the asset position anchor location while placing the 3D digital smart object in a game. In this embodiment, the developer can transmit their preferred anchor location to 3D digital smart object placement system 108, which is associated with the game, position, and developer identification data and saved in database 11220. In one embodiment, the scaling information provides a factor for each coordinate of the 3D digital smart object; the factor determines the relative size of the 3D digital smart object in a game scene.

[0081] FIG. 12 illustrates describing the operations of a system implementing a 3D digital smart object in a three dimensional environment, according to one embodiment of the present invention. As illustrated, at 302, system 100 is initialized after the developer logs into the 3D game development environment. At 304, system records the developer's identification data and game identification data. When the developer provides an instruction to place a 3D digital smart object within the gaming environment, at 306, the 3D digital smart object placement system 108 prompts the developer to select a 3D digital smart object. The developer can then select a GSO or BSO, as illustrated above. In one embodiment, 3D digital smart objects are presented to the developer via the gaming developer interface/ editor (e.g., Unity) via API provided by system. At 308, system 108 receives developer's selection. At 310, 3D digital smart object placement system 108 receives 3D digital smart object game location, size changes, positioning & arrangements from the developer. At 312, 3D digital smart object placement system 108 saves size and position data, along with 3D digital smart object identification data, location

identification data, game identification data, and publisher identification data in database 314. In one embodiment, in case the developer has positioned a GSO, an advertiser can use this data to target a GSO for asset replacement to convert the GSO into a BSO.

[0082] FIG. 13 illustrates the operations of an advertiser replacing a generic asset of a 3D digital smart object with a branded asset, according to one embodiment of the present invention. In one embodiment, 3D digital smart object 101 can be placed within a three dimensional environment and associated with advertisements that are to be analyzed, and wherein the 3D digital smart object can record different types of interaction of the 3D digital smart object with a user of the game and transmit user interaction information to the computing device. Advertisements can be placed by replacing a generic asset of a 3D digital smart object with a branded asset to convert a GSO to a BSO, in one embodiment, the advertiser logs in to system 100, as illustrated at 402. Thereafter, at 404, the advertiser creates at advertisement campaign. At 406, an advertisement target audience is selected by the advertiser. Based on the advertisement targeted audience, the developer presented an option to select an asset category and/or type related to which GSOs are displayed.

After the advertiser selects an asset category and/or type, a list of GSOs are displayed to the advertiser. At 408, the advertiser can review each GSO's past performance analytics, and select a GSO asset to be replaced by a branded asset to convert a GSO to a BSO, as illustrated at 410. After the advertiser selects a GSO for replacement of the asset, the advertiser uploads the branded asset (e.g., Coca-Cola® soda can) to replace the GSO asset (e.g., generic soda can). After the branded asset has been uploaded, 3D digital smart object placement system 108 can, in one embodiment, ensure that the uploaded branded asset is within the parameters set by the creator of the GSO as illustrated at 412.

Parameters set by the creator of the GSO can be the 3D digital smart object data provided during the generation of the 3D digital smart object, including, the standard asset information, asset anchor location position, and/or a minimum/maximum polygon count value for the branded asset that can replace the GSO asset to generate a BSO. In one embodiment, defining a minimum and/or maximum polygon count value assists in generating an advertisement standard that can allow of a BSO to be generated programmatically by replacing a GSO asset with a branded asset. In another embodiment, the publisher can further identify the types of different branded objects that can replace the asset by identifying the asset category and/or asset type. In one embodiment, the 3D digital smart object data can further associated with publisher identification data associated with the developer. In another embodiment, the 3D digital smart object data can also be associated with advertiser identification data associated with an advertiser.83] In one embodiment, based on the standard asset size information provided by the 3D digital smart object creator, the system can automatically scale the branded asset (of a BSO) to match the asset size of the GSO, as illustrated at 414. At 416, the advertiser can set the advertisement campaign and at 418, the advertiser can review and launch the advertisement campaign. At 420, 3D digital smart object placement system replaces the generic asset with the branded asset to convert the GSO into a BSO. At 422, the BSO's Dimensions, Object ID, Game ID, Location ID, Advertiser ID, Publisher ID and Ad Campaign Information are stored in database 428. In one embodiment, at 424, system 100 can notify the advertiser and/or publisher that the asset replacement has occurred. At 426, in one embodiment, when advertisement campaign is completed the BSO is replaced back to the original GSO in the online game.

[0084] FIG. 14 illustrates the implementation of a branded 3D digital smart object in a three dimensional environment, according to one embodiment of the present invention. As illustrated, game scene 500 can include two BSOs, as depicted at Coca-Cola® beverage cans. In one embodiment, the BSOs can either be placed in the game directly by the publisher/developer. In another embodiment, the developer places GSOs and an advertiser replaces the generic asset with branded assets to convert a GSO into a BSO, as illustrated. Since each 3D digital smart object in the system can be represented by a unique 3D digital smart object identification data, the same GSO can be placed at multiple locations within any number of online games. For example, as illustrated 3D digital smart object 501 and 3D digital smart object 502 can be implemented from one single 3D digital smart object created by a developer or provided by the system.

Therefore, the parameters set by the creator of the 3D digital smart object (e.g., the standard asset information, asset anchor location position, and/or a minimum/maximum polygon count value, etc.) for both 3D digital smart object 501 and 3D digital smart object 502 can be same. However, during placement of the 3D digital smart objects, the developer can provide different scaling factors for each 3D digital smart object relative to the game scene, and the corresponding information can be saved by 3D digital smart object placement system for each location. Since each 3D digital smart object 501 and 3D digital smart object 502 implementation is different (but only shares parameters set by the developer), each 3D digital smart object 501 and 502 can transmit different user engagement metrics to system 100. Therefore, as illustrated, two 3D digital smart objects can be implemented using the same 3D digital smart object and share common parameters as defined/set by the creator of the 3D digital smart object.

[0085] FIG. 15 illustrates a block diagram describing a 3D digital smart object processing system receiving data from a three dimensional environment, according to one embodiment of the present invention. In one embodiment, when a user/player is on a game scene via interface 112, the player can see 3D digital smart objects 101. The player can interact with the 3D digital smart objects, can choose to view them, or a combination thereof. Each 3D digital smart object 101 can be configured to record different types of interaction of 3D digital smart object 101 with a user/player of the game and transmit user interaction (or viewability) information to 3D digital smart object manager 15603, by employing event triggers. 3D digital smart object manager 15603 can then forward the information to 3D digital smart object processing system 110. In one embodiment, event triggers are capable of determining user interaction with, or viewability of, a 3D digital smart object and transmit metrics, based on the user interaction (or viewability), to a 3D digital smart object processing system. In one embodiment, the event triggers transmit user interaction including (but not limited to) determining a user viewing a 3D digital smart object, the user interacting with a 3D digital smart object, a distance between the user and a 3D digital smart object, a percentage size of a 3D digital smart object in relationship to the size of the user interface, a period of time that the user interacted with a 3D digital smart object, the percentage of the 3D digital smart object that was viewable on the user's screen (e.g., is the viewable surface of 3D digital smart object 50% below the screen), etc. In one embodiment, event triggers can be configured or customized by the implementer (developer/publisher) of the 3D digital smart object.

86] In one embodiment, 3D digital smart object manager 15603, can be the

communication interface between 3D digital smart objects 101 and 3D digital smart object processing system 110. In one embodiment, 3D digital smart object manager 15603 resides in the game environment. 3D digital smart objects 101 and 3D digital smart object manager 15603 can be compiled within the gaming environment, thus become part of the game. 3D digital smart object manager receives all event triggers from various 3D digital smart objects within a game, and can periodically transmit the user engagement data to 3D digital smart object processing system 110 of system 100 (residing remotely from the gaming server, in one embodiment). 3D digital smart object processing system 110 can include a 3D digital smart object analytics engine 15607 that can analyze the data received from each 3D digital smart object 101. Based on the received data, 3D digital smart object analytics engine 15607 can transmit the data to a metrics generation module 15609 which keeps track of the viewability/ interaction of different users with the 3D digital smart object, collectively referred to as performance of the 3D digital smart object herein. This information can then be transmitted to a reporting module 15611 that can display the performance at the publisher's and/or advertiser's dashboard. [0087] FIG. 16 illustrates the operations of displaying a 3D digital smart object in a game development environment. As illustrated, at 16701, 3D digital smart object placement system 108 receives a request to present the 3D digital smart object in the game development environment of the game engine, the 3D digital smart object enclosed in a 3D placeholder cube. At 16703, system 108 retrieves 3D digital smart object data from an asset repository including an asset, asset anchor location, and standard asset size information of the asset in a 3D space. At 16705, system 108 transmits the 3D digital smart object data to the game development environment of the game engine, and at 16707 system 108 receives a position location for the 3D digital smart object. At 16709, system 108 receives scaling information related to the 3D digital smart object relative to the game scene. At 16711, system 108 stores into the asset repository the position location, and scaling information related to the 3D digital smart object displayed in the game.

[0088] FIG. 17 illustrates the operations of receiving user engagement actions and

viewability metrics related to a 3D digital smart object by a 3D digital smart object placement system, according to one embodiment of the present invention. At 17801, 3D digital smart object placement system 108 can receive an instruction from an advertiser to create Ad Campaign. At 17802, the system transmits a list 3D digital smart objects that are available to the advertiser. At 17803, the system can receive a selection of 3D digital smart object from advertiser. At 17805, the system present user engagement actions and viewability metrics (scripts) list to advertiser, and at 17807, the system receives user engagement actions and viewability metrics from advertiser. At 17809, system 108 associates selected user engagement actions of the 3D digital smart object with advertiser.

[0089] FIG. 18 illustrates the operations of receiving user engagement data by a 3D digital smart object processing system, according to one embodiment of the present invention. Once the 3D digital smart objects are viewed, or interacted with, by a user/player of the game, at 18901, 3D digital smart object processing system 110 can receive user engagement data and viewability metrics from 3D digital smart object manager. At 18903 system 110 can compute metrics associated with the user engagement data selected by advertiser and at 18905 system 110 can save metrics data in database.

[0090] Thus, methods, apparatuses, and computer readable medium to display and/or

generate 3D digital smart objects in a three dimensional environment. Although the present invention has been described with reference to specific exemplary embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention as set forth in the claims. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense.

Examples and additional notes

[0091] Example 1 is a method to generate a three-dimensional (3D) digital smart object for use in an 3D environment, comprising: presenting, by a computing device, a 3D placeholder to a publisher of the 3D environment; receiving an asset from the publisher to be placed in the 3D placeholder; receiving asset data, the asset data including asset category and asset type associated to the asset, and wherein the asset data further includes, a minimum and maximum asset polygon count value; receiving standard asset size information of the asset in a 3D space, the standard asset size information including an X-axis, Y-axis, and Z-axis dimension of the asset; receiving an asset positioning information, the asset positioning information including an anchor location and an asset orientation, wherein the anchor location being at least one of the X-axis, Y-axis, Z-axis, or a combination thereof, of the 3D placeholder and wherein the asset orientation is the desired orientation of the asset selected by publisher; storing digital smart object data, including the asset, standard asset size information, asset positioning information, and asset data in a repository; and generating the 3D digital smart object by using the digital smart object data; wherein the 3D digital smart object can be placed within the 3D environment and wherein the 3D digital smart object collects data related to user interaction or viewability with the 3D digital smart object.

[0092] In Example 2, the subject matter of Example 1 includes, wherein generating the 3D digital smart object further includes associating the digital smart object data with event triggers, wherein the event triggers can determine user interaction with the 3D digital smart object, the event triggers transmitting data based on the user interaction that can be used to generate user viewability or interaction based metrics. In Example 3, the subject matter of Example 2 includes, wherein at least one event trigger can be configured by the publisher, and wherein at least another of the event trigger can be configured by an advertiser. In Example 4, the subject matter of Examples 2-3 includes, wherein the event triggers transmit user interaction including determining at least one of a user looking at the 3D digital smart object, the user interacting with the 3D digital smart object, a distance between the user and the 3D digital smart object, a percentage size of the 3D digital smart object in relationship to the size of the user interface, the percentage of the digital smart object that was viewed on the user's screen, or a period of time that the user interacted with the 3D digital smart object. In Example 5, the subject matter of Examples 1-4 includes wherein the 3D placeholder is presented to the publisher via at least one of an Application Program Interface (API) or a software development kit (SDK), the asset being a generic 3D representation of geometric data, wherein the asset within the 3D placeholder provides a visual representation of the 3D digital smart object. In Example 6, the subject matter of Examples 1-5 includes, wherein an advertiser can replace the asset with a branded object, the branded object related to a brand associated with the advertiser, and wherein the publisher can define a minimum and maximum polygon count value for the asset in the 3D digital smart object, and wherein the branded object can replace the asset only when the branded object has a polygon count within the defined minimum and maximum polygon count value, and wherein the minimum and maximum polygon count value is included in the digital smart object data. In Example 7, the subject matter of

Example 6 includes, wherein the publisher can further identify the types of different branded objects that can replace the asset based on the asset category and asset type. In Example 8, the subject matter of Examples 1-7 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information is determined when at least one of the X- axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder. In Example 9, the subject matter of Examples 1-8 includes, wherein the anchor location is provided by the publisher, and wherein the digital smart object data is further associated with publisher identification data. In Example 10, the subject matter of Examples 1-9 includes, wherein the 3D digital smart object is used in medical training, and wherein data collected by the 3D digital smart object is associated with user movement and orientation of the 3D digital smart object.

3] Example 11 is a digital smart object generation system to generate a three- dimensional (3D) digital smart object for use in an 3D environment, comprising a hardware processing system coupled to a memory device, the hardware processing system configured to: present a 3D placeholder to a publisher of the 3D environment; receive an asset from the publisher to be placed in the 3D placeholder; receive asset data, the asset data including asset category and asset type associated to the asset, and wherein the asset data further includes, a minimum and maximum asset polygon count value; receive standard asset size information of the asset in a 3D space, the standard asset size information including an X-axis, Y-axis, and Z-axis dimension of the asset; receive an asset positioning information, the asset positioning information including an anchor location and an asset orientation, wherein the anchor location being at least one of the X- axis, Y-axis, Z-axis, or a combination thereof, of the 3D placeholder and wherein the asset orientation is the desired orientation of the asset selected by publisher; store digital smart object data, including the asset, standard asset size information, asset positioning information, and asset data in a repository; and generate the 3D digital smart object by using the digital smart object data; wherein the 3D digital smart object can be placed within the 3D environment and wherein the 3D digital smart object collects data related to user interaction or viewability with the 3D digital smart object. In Example 12, the subject matter of Example 11 includes, wherein the hardware processing system is further configured to generate the 3D digital smart object by associating the digital smart object data with event triggers, wherein the event triggers are capable of determining user interaction with the 3D digital smart object, the event triggers transmitting data based on the user interaction that can be used to generate user viewability or interaction based metrics. In Example 13, the subject matter of Example 12 includes, wherein at least one event trigger can be configured by the publisher, and wherein at least another of the event trigger can be configured by an advertiser. In Example 14, the subject matter of Examples

12-13 includes, wherein the event triggers transmit user interaction including determining at least one of a user looking at the 3D digital smart object, the user interacting with the 3D digital smart object, a distance between the user and the 3D digital smart object, a percentage size of the 3D digital smart object in relationship to the size of the user interface, the percentage of the digital smart object that was viewed on the user's screen, or a period of time that the user interacted with the 3D digital smart object. In Example 15, the subject matter of Examples 11-14 includes, wherein the 3D placeholder is presented to the publisher via at least one of an Application Program Interface (API) or a software development kit (SDK), the asset being a generic 3D representation of geometric data, wherein the asset within the 3D placeholder provides a visual representation of the

3D digital smart object. In Example 16, the subject matter of Examples 11-15 includes wherein an advertiser can replace the asset with a branded object, the branded object related to a brand associated with the advertiser, and wherein the publisher can define a minimum and maximum polygon count value for the asset in the 3D digital smart object, and wherein the branded object can replace the asset only when the branded object has a polygon count within the defined minimum and maximum polygon count value, and wherein the minimum and maximum polygon count value is included in the digital smart object data. In Example 17, the subject matter of Example 16 includes, wherein the publisher can further identify the types of different branded objects that can replace the asset based on the asset category and asset type. In Example 18, the subject matter of Examples 11-17 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information is determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder. In Example 19, the subject matter of Examples 11-18 includes, wherein the anchor location is provided by the publisher, and wherein the digital smart object data is further associated with publisher identification data. In Example 20, the subject matter of Examples 11-19 includes, wherein the 3D digital smart object is used in medical training, and wherein data collected by the 3D digital smart object is associated with user movement and orientation of the 3D digital smart object.

4] Example 21 is a non-transitory computer readable medium comprising instructions, which when executed by a processing system executes a method to generate a three - dimensional (3D) digital smart object for use in an 3D environment, the method comprising: presenting a 3D placeholder to a publisher of the 3D environment; receiving an asset from the publisher to be placed in the 3D placeholder; receiving asset data, the asset data including asset category and asset type associated to the asset, and wherein the asset data further includes, a minimum and maximum asset polygon count value;

receiving standard asset size information of the asset in a 3D space, the standard asset size information including an X-axis, Y-axis, and Z-axis dimension of the asset; receiving an asset positioning information, the asset positioning information including an anchor location and an asset orientation, wherein the anchor location being at least one of the X- axis, Y-axis, Z-axis, or a combination thereof, of the 3D placeholder and wherein the asset orientation is the desired orientation of the asset selected by publisher; storing digital smart object data, including the asset, standard asset size information, asset positioning information, and asset data in a repository; and generating the 3D digital smart object by using the digital smart object data; wherein the 3D digital smart object can be placed within the 3D environment and wherein the 3D digital smart object collects data related to user interaction or viewability with the 3D digital smart object.

5] In Example 22, the subject matter of Example 21 includes, wherein generating the 3D digital smart object further includes associating the digital smart object data with event triggers, wherein the event triggers are capable of determining user interaction with the

3D digital smart object, the event triggers transmitting data based on the user interaction that can be used to generate user viewability or interaction based metrics. In Example 23, the subject matter of Example 22 includes, wherein at least one event trigger can be configured by the publisher, and wherein at least another of the event trigger can be configured by an advertiser. In Example 24, the subject matter of Examples 22-23 includes, wherein the event triggers transmit user interaction including determining at least one of a user looking at the 3D digital smart object, the user interacting with the 3D digital smart object, a distance between the user and the 3D digital smart object, a percentage size of the 3D digital smart object in relationship to the size of the user interface, the percentage of the digital smart object that was viewed on the user's screen, or a period of time that the user interacted with the 3D digital smart object. In Example 25, the subject matter of Examples 21-24 includes, wherein the 3D placeholder is presented to the publisher via at least one of an Application Program Interface (API) or a software development kit (SDK), the asset being a generic 3D representation of geometric data, wherein the asset within the 3D placeholder provides a visual representation of the

3D digital smart object. In Example 26, the subject matter of Examples 21-25 includes, wherein an advertiser can replace the asset with a branded object, the branded object related to a brand associated with the advertiser, and wherein the publisher can define a minimum and maximum polygon count value for the asset in the 3D digital smart object, and wherein the branded object can replace the asset only when the branded object has a polygon count within the defined minimum and maximum polygon count value, and wherein the minimum and maximum polygon count value is included in the digital smart object data. In Example 27, the subject matter of Example 26 includes, wherein the publisher can further identify the types of different branded objects that can replace the asset based on the asset category and asset type. In Example 28, the subject matter of

Examples 21-27 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information is determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder. In Example 29, the subject matter of Examples 21-28 includes wherein the anchor location is provided by the publisher, and wherein the digital smart object data is further associated with publisher identification data. In Example 30, the subject matter of Examples 21-29 includes, wherein the 3D digital smart object is used in medical training, and wherein data collected by the 3D digital smart object is associated with user movement and orientation of the 3D digital smart object.

[0096] Example 31 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-30. Example 32 is an apparatus comprising means to implement any of Examples 1-30. Example 33 is a system to implement any of Examples 1-30. Example 34 is a method to implement any of

Examples 1-30.

[0097] Example 35 is a system to generate data related to user interaction with a three

dimensional (3D) digital asset in a 3D environment, comprising: a client computer comprising a 3D engine configured to: determine whether the 3D digital asset is drawn on a culling mask of a camera in the 3D environment, the 3D digital asset comprising a collidable mesh, draw a line between the camera and the 3D digital asset using a ray casting based technique, determine that the line collides with the collidable mesh of the 3D digital asset, using a screen bounding function of the 3D engine, determine a proportion of the 3D digital asset on a graphical user interface of the client computer when it is determined that the line collides with the collidable mesh, obtain a percentage of the graphical user interface that is covered by the 3D digital asset based on the proportion, and generate data related to user interaction with the 3D digital asset in the 3D environment based on the percentage of the graphical user interface covered by the 3D digital asset, wherein the user interaction includes, at least one of tapping, touching, moving, viewing, or requesting a detailed description of the 3D digital asset; and a server computer configured to: receive the generated data related to user interaction with the 3D digital asset, wherein the generated data includes a time period associated with the percentage of the user graphical interface covered by the 3D digital asset.

[0098] In Example 36, the subject matter of Example 35 includes, wherein the 3D digital asset is bounded within a 3D placeholder, the 3D placeholder requested using an Application Programming Interface (API) or a Standard Development Kit (SDK) in the 3D environment being developed within the 3D development platform. In Example 37, the subject matter of Example 36 includes, wherein the 3D digital asset has a property to set a standard asset size information that provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information is determined when at least one of an X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder. In Example 38, the subject matter of Examples 36-37 includes, wherein the 3D digital asset can have a minimum and maximum polygon count value constraint provided by a developer of the 3D environment. In Example 39, the subject matter of Examples 35-38 includes, wherein the server computer further comprises an analytics engine configured to generate metrics related to the user interaction. In Example 40, the subject matter of Examples 35-39 includes, wherein the data related to user interaction is generated using event script by the client computer. In Example 41, the subject matter of Examples 35-40 includes, wherein the event triggers can determine at least one of the user viewing the 3D digital asset, the user interacting with the 3D digital asset, a distance between the user and the 3D digital asset, a percentage size the 3D digital asset in relationship to the size of the user interface, a period of time that the user interacted with the 3D digital asset. In Example 42, the subject matter of Example 41 includes, wherein the event script can be configured by another party. In Example 43, the subject matter of Examples 41-42 includes, wherein the event script is configured to at least gather data related to the graphical user interface screen covered by the 3D digital asset at a current time, determine whether the 3D digital asset is in view to the camera, determine geometry of camera view from the 3D digital asset by collision detection to determine a probability of distance of the camera view from the 3D digital asset, request details about the 3D digital asset from the server, determine a relative angle with which a user is interacting with the 3D digital asset, or determine a relative speed of the user, based on pixel traversed per seconds, in which the user is interacting with the 3D digital asset. In Example 44, the subject matter of Examples 41-43 includes, wherein the server maintains an array of user data interaction for calculating averages of the time the user interacted with the 3D digital asset. Example 46 is at least one machine -readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 35-45. Example 47 is an apparatus comprising means to implement of any of Examples 35-45. Example 48 is a system to implement of any of Examples 35-45. Example 49 is a method to implement of any of Examples 35-45.

9] Example 50 is a method of displaying a three-dimensional (3D) 3D digital smart object in a 3D environment, comprising: receiving, by a computing device, a request to present the 3D digital smart object in a game development environment of a game engine, the 3D digital smart object enclosed in a 3D placeholder cube; retrieving 3D digital smart object data from an asset repository, the 3D digital smart object data associated with an asset category and asset type, the 3D digital smart object data including an asset, asset anchor location, and standard asset size information of the asset in a 3D space;

transmitting the 3D digital smart object data to the game development environment of the game engine; receiving a position location for the 3D digital smart object in a game; receiving scaling information related to the 3D digital smart object, the scaling information providing a factor for each coordinate of the 3D digital smart object, wherein the factor determines the relative size of the 3D digital smart object in a game scene of the game; and storing, into the asset repository, the position location, and scaling information related to the 3D digital smart object displayed in the game; wherein the 3D digital smart object can be displayed at the position location when a player is interacting with the game at the game scene. In Example 51, the subject matter of Example 50 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information includes an X-axis, Y-axis, and Z-axis dimension of the asset, and wherein the standard asset size information is determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder cube. In Example 52, the subject matter of Examples 50-51 includes, wherein the position location including an

X-axis, Y-axis, and Z-axis coordinates of a location within a scene of the online game where the 3D digital smart object is intended to be placed. In Example 53, the subject matter of Examples 50-52 includes, wherein the 3D digital smart object is associated with advertisements that are to be analyzed, and wherein the 3D digital smart object can record different types of interaction of the 3D digital smart object with a user of the game and transmit user interaction information to the computing device. In Example 54, the subject matter of Examples 50-53 includes, wherein the asset at least one of a generic representation of an object or shape or a branded representation of an object or shape. In Example 55, the subject matter of Examples 50-54 includes, wherein the 3D digital smart object data further includes at least one of a minimum or maximum polygon count value of the asset. In Example 56, the subject matter of Examples 54-55 includes, wherein the asset can be replaced with a branded representation of another object or shape. In Example 57, the subject matter of Examples 50-56 includes, wherein the 3D environment is a 3D real estate environment, and wherein the game is an interactive environment displaying a 3D view of at least one property.

0] Example 58 is a non-transitory computer readable medium comprising instructions, which when executed by a processor comprising at least one core, implements a method of displaying a three-dimensional (3D) 3D digital smart object in a 3D environment, comprising: receiving a request to present the 3D digital smart object in a game development environment of a game engine, the 3D digital smart object enclosed in a 3D placeholder cube; retrieving 3D digital smart object data from an asset repository, the 3D digital smart object data associated with an asset category and asset type, the 3D digital smart object data including an asset, asset anchor location, and standard asset size information of the asset in a 3D space; transmitting the 3D digital smart object data to the game development environment of the game engine; receiving a position location for the 3D digital smart object in a game; receiving scaling information related to the 3D digital smart object, the scaling information providing a factor for each coordinate of the 3D digital smart object, wherein the factor determines the relative size of the 3D digital smart object in a game scene of the game; and storing, into the asset repository, the position location, and scaling information related to the 3D digital smart object displayed in the game; wherein the 3D digital smart object can be displayed at the position location when a player is interacting with the game at the game scene. In Example 59, the subject matter of Example 58 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information includes an X-axis, Y-axis, and Z-axis dimension of the asset, and wherein the standard asset size information is determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder cube. In Example 60, the subject matter of Examples 58-59 includes, wherein the position location including an X-axis, Y-axis, and Z-axis coordinates of a location within a scene of the online game where the 3D digital smart object is intended to be placed. In Example 61, the subject matter of Examples 58-60 includes, wherein the 3D digital smart object is associated with advertisements that are to be analyzed, and wherein the 3D digital smart object can record different types of interaction of the 3D digital smart object with a user of the game and transmit user interaction information to the computing device. In Example 62, the subject matter of Examples 58-61 includes, wherein the asset at least one of a generic representation of an object or shape or a branded representation of an object or shape. In Example 63, the subject matter of Examples 58-62 includes, wherein the 3D digital smart object data further includes at least one of a minimum or maximum polygon count value of the asset. In Example 64, the subject matter of Examples 62-63 includes, wherein the asset can be replaced with a branded representation of another object or shape. In Example 65, the subject matter of

Examples 58-64 includes, wherein the 3D environment is a 3D real estate environment, and wherein the game is an interactive environment displaying a 3D view of at least one property.

1] Example 66 is a system to display a three-dimensional (3D) 3D digital smart object in a 3D environment , comprising: a memory device; a processing device comprising one or more cores, coupled to the memory device, configured to: receive a request to present the 3D digital smart object in a game development environment of a game engine, the 3D digital smart object enclosed in a 3D placeholder cube; retrieve 3D digital smart object data from an asset repository, the 3D digital smart object data associated with an asset category and asset type, the 3D digital smart object data including an asset, asset anchor location, and standard asset size information of the asset in a 3D space; transmit the 3D digital smart object data to the game development environment of the game engine; receive a position location for the 3D digital smart object in a game; receive scaling information related to the 3D digital smart object, the scaling information providing a factor for each coordinate of the 3D digital smart object, wherein the factor determines the relative size of the 3D digital smart object in a game scene of the game; and store, into the asset repository, the position location, and scaling information related to the 3D digital smart object displayed in the game; wherein the 3D digital smart object is displayed at the position location when a player is interacting with the game at the game scene. In Example 67, the subject matter of Example 66 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information includes an X-axis, Y-axis, and Z-axis dimension of the asset, and wherein the standard asset size information is determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder cube. In Example 68, the subject matter of Examples 66-67 includes, wherein the position location including an X-axis, Y-axis, and Z-axis coordinates of a location within a scene of the online game where the 3D digital smart object is intended to be placed. In Example 69, the subject matter of Examples 66-68 includes, wherein the 3D digital smart object is associated with advertisements that are to be analyzed, and wherein the 3D digital smart object can record different types of interaction of the 3D digital smart object with a user of the game and transmit user interaction information to the computing device. In Example 70, the subject matter of Examples 66-69 includes, wherein the asset at least one of a generic representation of an object or shape or a branded representation of an object or shape, and wherein the asset can be replaced with a branded representation of another object or shape. In Example 71, the subject matter of Examples 66-70 includes, wherein the 3D digital smart object data further includes at least one of a minimum or maximum polygon count value of the asset. In Example 72, the subject matter of Examples 66-71 includes, wherein the 3D environment is a 3D real estate environment, and wherein the game is an interactive environment displaying a 3D view of at least one property. Example 73 is at least one machine -readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 50-72. Example 74 is an apparatus comprising means to implement of any of Examples 50-72. Example 75 is a system to implement of any of Examples 50-72. Example 76 is a method to implement of any of Examples 50-72.

2] Example 77 is a system for determining user based interaction data in a virtual environment, comprising: an asset repository comprising a plurality of 3D digital assets, wherein each of the plurality of 3D digital assets can be associated with at least one script that can transmit user interaction with each of the plurality of 3D digital assets when displayed within a virtual environment in a client machine, wherein each 3D digital asset is associated with asset data, wherein the asset data including an asset anchor location and a standard asset size information, position location, and scaling information of the 3D digital asset in the virtual environment; and a 3D digital asset processing system, coupled to the asset repository, configured to: receive user interaction data related to the 3D digital asset from the client machine; generate metrics related to user interaction, including tapping, touching, moving, time spent, viewing, requesting detailed description related to the 3D digital asset; and save the generated metric data associated with the position location of the 3D digital asset to the asset repository. In Example 78, the subject matter of Example 77 includes, wherein user interaction data is generated by the client machine, the client machine further configured to: determine whether the 3D digital asset is drawn on a culling mask of a camera in the 3D environment, wherein the 3D digital asset comprising a collidable mesh; using ray casting, draw a line between the camera and the 3D digital asset; determine that the line collides with the collidable mesh of the 3D digital asset; using a screen bounding function of the 3D engine, determine a proportion of the 3D digital asset on a graphical user interface of the client computer when it is determined that the line collides with the collidable mesh; and obtain a percentage of the graphical user interface that is covered by the 3D digital asset based on the proportion; and generate data related to user interaction with the 3D digital asset in the 3D environment based on the percentage of the graphical user interface covered by the 3D digital asset.

3] In Example 79, the subject matter of Examples 77-78 includes, a 3D digital asset placement system, coupled to the asset repository, the 3D digital asset placement system configured to: receive a request to present a 3D digital asset out of the plurality of 3D digital assets, within a 3D placeholder in a 3D development environment; retrieve the 3D digital asset and associated asset data from the asset repository, the associated asset data further associated with an asset category and asset type; transmit the 3D digital asset and associated asset data to the game development environment; receive the position location for the 3D digital asset in the 3D environment, receive the scaling information related to the 3D digital asset, the scaling information providing a factor for each coordinate of the 3D digital asset within the 3D environment, wherein the factor determines the relative size of the 3D digital asset in a scene of the 3D environment; and store, into the asset repository, the position location, and scaling information related to the 3D digital asset displayed in the 3D environment. In Example 80, the subject matter of Examples 77-79 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information includes an X-axis, Y-axis, and Z-axis dimension of the asset, and wherein the standard asset size information is determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder. [0104] In Example 81, the subject matter of Examples 77-80 includes, wherein the position location including an X-axis, Y-axis, and Z-axis coordinates of a location within a scene of the online game where the 3D digital asset is intended to be placed. In Example 82, the subject matter of Examples 77-81 includes, wherein the 3D digital asset is at least one of a generic representation of an object or shape or a branded representation of an object or shape. In Example 83, the subject matter of Examples 77-82 includes, wherein the 3D digital asset data further includes at least one of a minimum or maximum polygon count value of the asset.

[0105] Example 84 is a non-transitory computer readable medium comprising instructions which when executed by a processing system comprising at least one hardware processing core, executes a method for determining user based interaction data in a virtual environment, comprising: receiving user interaction data related to the 3D digital asset from a client machine, wherein the user interaction data is received from a 3D digital asset, wherein the 3D digital assets can be associated with at least one script that can transmit user interaction when displayed within a virtual environment in the client machine, wherein the 3D digital asset is associated with asset data, wherein the asset data includes, an asset anchor location and a standard asset size information, position location, and scaling information of the 3D digital asset in the virtual environment; generating metrics related to user interaction, including tapping, touching, moving, time spent, viewing, requesting detailed description related to the 3D digital asset; and saving the generated metric data associated with the position location to the asset repository, wherein a 3D digital asset processing system configured. In Example 85, the subject matter of Example 84 includes, wherein the client machine generates user interaction data by: determining whether the 3D digital asset is drawn on a culling mask of a camera in the 3D environment, wherein the 3D digital asset comprising a collidable mesh; using ray casting, drawing a line between the camera and the 3D digital asset; determining that the line collides with the collidable mesh of the 3D digital asset; using a screen bounding function of the 3D engine, determining a proportion of the 3D digital asset on a graphical user interface of the client computer when it is determined that the line collides with the collidable mesh; obtaining a percentage of the graphical user interface that is covered by the 3D digital asset based on the proportion; and generating data related to user interaction with the 3D digital asset in the 3D environment based on the percentage of the graphical user interface covered by the 3D digital asset. In Example 86, the subject matter of Examples 84-85 includes, further comprising: receiving a request to present a 3D digital asset out of the plurality of 3D digital assets, within a 3D placeholder in a 3D development environment; retrieving the 3D digital asset and associated asset data from the asset repository, the associated asset data further associated with an asset category and asset type; transmitting the 3D digital asset and associated asset data to the game development environment; receiving the position location for the 3D digital asset in the 3D environment; receiving the scaling information related to the 3D digital asset, the scaling information providing a factor for each coordinate of the 3D digital asset within the 3D environment, wherein the factor determines the relative size of the 3D digital asset in a scene of the 3D environment; and storing, into the asset repository, the position location, and scaling information related to the 3D digital asset displayed in the 3D environment. In Example 87, the subject matter of Examples 84-86 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information includes an X-axis, Y- axis, and Z-axis dimension of the asset, and wherein the standard asset size information is determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder. In Example 88, the subject matter of Examples 84-87 includes, wherein the position location including an X- axis, Y-axis, and Z-axis coordinates of a location within a scene of the online game where the 3D digital asset is intended to be placed. In Example 89, the subject matter of

Examples 84-88 includes, wherein the 3D digital asset is at least one of a generic representation of an object or shape or a branded representation of an object or shape. In Example 90, the subject matter of Examples 84-89 includes, wherein the 3D digital asset data further includes at least one of a minimum or maximum polygon count value of the asset.

6] Example 91 is a method for determining user based interaction data in a virtual environment, comprising: receiving, by a computing device, user interaction data related to the 3D digital asset from a client machine, wherein the user interaction data is received from a 3D digital asset, wherein the 3D digital assets can be associated with at least one script that can transmit user interaction when displayed within a virtual environment in the client machine, wherein the 3D digital asset is associated with asset data, wherein the asset data includes, an asset anchor location and a standard asset size information, position location, and scaling information of the 3D digital asset in the virtual environment; generating, by the computing device, metrics related to user interaction, including tapping, touching, moving, time spent, viewing, requesting detailed description related to the 3D digital asset; and saving, by the computing device, the generated metric data associated with the position location to the asset repository, wherein a 3D digital asset processing system configured. In Example 92, the subject matter of Example 91 includes, wherein the client machine generates user interaction data by: determining whether the 3D digital asset is drawn on a culling mask of a camera in the 3D

environment, wherein the 3D digital asset comprising a collidable mesh; using ray casting, drawing a line between the camera and the 3D digital asset; determining that the line collides with the collidable mesh of the 3D digital asset; using a screen bounding function of the 3D engine, determining a proportion of the 3D digital asset on a graphical user interface of the client computer when it is determined that the line collides with the collidable mesh; obtaining a percentage of the graphical user interface that is covered by the 3D digital asset based on the proportion; and generating data related to user interaction with the 3D digital asset in the 3D environment based on the percentage of the graphical user interface covered by the 3D digital asset. In Example 93, the subject matter of Examples 91-92 includes, receiving a request to present a 3D digital asset out of the plurality of 3D digital assets, within a 3D placeholder in a 3D development environment; retrieving the 3D digital asset and associated asset data from the asset repository, the associated asset data further associated with an asset category and asset type; transmitting the 3D digital asset and associated asset data to the game development environment; receiving the position location for the 3D digital asset in the 3D environment; receiving the scaling information related to the 3D digital asset, the scaling information providing a factor for each coordinate of the 3D digital asset within the 3D environment, wherein the factor determines the relative size of the 3D digital asset in a scene of the 3D

environment; and storing, into the asset repository, the position location, and scaling information related to the 3D digital asset displayed in the 3D environment. In Example 94, the subject matter of Examples 91-93 includes, wherein the standard asset size information provides the maximum 3D size of the asset relative to the 3D placeholder, and wherein the standard asset size information includes an X-axis, Y-axis, and Z-axis dimension of the asset, and wherein the standard asset size information is determined when at least one of the X-axis, Y-axis, or Z-axis dimension of the asset equals to its corresponding axis dimension of the 3D placeholder. In Example 95, the subject matter of Examples 91-94 includes, wherein the position location including an X-axis, Y-axis, and Z-axis coordinates of a location within a scene of the online game where the 3D digital asset is intended to be placed. In Example 96, the subject matter of Examples 91-95 includes, wherein the 3D digital asset is at least one of a generic representation of an object or shape or a branded representation of an object or shape, and wherein the 3D digital asset data further includes at least one of a minimum or maximum polygon count value of the asset. Example 97 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 77-96. Example 98 is an apparatus comprising means to implement of any of Examples 77-96. Example 99 is a system to implement of any of Examples 77-96. Example 100 is a method to implement of any of Examples 77-96.