CN117377958A

CN117377958A - System and method for managing non-replaceable tokens and corresponding digital assets

Info

Publication number: CN117377958A
Application number: CN202280037580.4A
Authority: CN
Inventors: W·J·霍兰; J·基斯; B·福格尔桑; A·比塞恩; W·怀特; M·F·塔维拉
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2021-06-04
Filing date: 2022-06-04
Publication date: 2024-01-09

Abstract

Systems and techniques for context token associated media output are described. The system receives sensor data captured by at least one sensor of the media device. The system identifies a relationship between the media device and an anchor element associated with the token based on the sensor data. The system identifies the token in the payload of at least one tile of the distributed ledger. The token corresponds to media content according to the distributed ledger. The system generates a representation of the media content corresponding to the token. In response to identifying the relationship between the media device and the anchor element, the system outputs a representation of the media content.

Description

System and method for managing non-replaceable tokens and corresponding digital assets

Technical Field

The present application relates to management of digital assets. For example, aspects of the present application relate to various techniques for creating, modifying, tracking, authenticating, transferring, and/or managing non-replaceable tokens and/or digital assets that may be associated with a device.

Background

People often find it interesting to own, use or trade unique or rare items related to celebrities, activities or places that are respected by the person. For example, people often seek to obtain signatures on clothing or music albums from well-known musicians at concerts to commemorate participation in such concerts, turning the signed clothing or music albums into unique items. Similarly, people often seek to purchase packages, props, animation episodes, and other items for producing movies or television programs.

Digital assets may include, for example, images, videos, audio clips, three-dimensional models, and the like. In general, digital assets are replaceable, meaning that any one copy of a given digital asset can be interchanged with any other copy of the same digital asset.

An extended reality (XR) device is a device that displays an environment to a user, for example, through a Head Mounted Display (HMD), glasses, a mobile handheld device, or other device. The environment is at least partially different from the real world environment in which the user is located. Users may typically interactively change their view of the environment, such as by tilting or moving the HMD (e.g., by moving the user's head, etc.) or other device. Virtual Reality (VR), augmented Reality (AR), and Mixed Reality (MR) are examples of XR.

Disclosure of Invention

In some examples, systems and techniques for creating, modifying, tracking, authenticating, and/or transferring non-replaceable digital assets associated with a device location are described. The media device may include a sensor, such as an image sensor and/or a positioning sensor. The media device may use its sensor to capture sensor data. In some examples, a system receives media content based on sensor data captured by at least one sensor of a media device. The system determines a location of the media device (e.g., based on sensor data). The system determines (e.g., based on sensor data) that the location of the media device is within a geographic region. In response to determining that the location of the media device is within a geographic region, the system generates a token corresponding to the media content. The payload of at least one tile of the distributed ledger identifies the token.

In some examples, a system receives sensor data captured by at least one sensor of a media device. The system identifies interactions between the media device and anchor elements associated with the token based on the sensor data. The system identifies the token in a payload of at least one tile of the distributed ledger. The token corresponds to media content according to the distributed ledger. The system generates a representation of media content corresponding to the token. In response to identifying interactions between the media device and the anchor element, the system outputs a representation of the media content.

In some examples, the system identifies a token corresponding to the media content in a payload of at least one tile of the distributed ledger. Parameters of the token in the distributed ledger indicate that the token is associated with a first user. The system identifies devices associated with the token and the media content. The apparatus is also associated with the first user. The system identifies that the device has been relocated to an area associated with a second user. In response to identifying that the device has been relocated to the area, the system causes the parameters of the tokens in the distributed ledger to be modified from indicating that tokens are associated with the first user to indicating that tokens are associated with the second user.

In some examples, systems and techniques for token generation are described. Systems, apparatuses, methods, and computer-readable media for token generation are disclosed. According to at least one example, an apparatus for token generation is provided that includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to: receiving media content based on sensor data captured by at least one sensor of a media device; determining a location of the media device; determining that the location of the media device is within a geographic region; and generating a token corresponding to the media content in response to determining that the location of the media device is within the geographic area, wherein a payload of at least one tile of the distributed ledger identifies the token.

In another example, a method for token generation is provided. The method comprises the following steps: receiving media content based on sensor data captured by at least one sensor of a media device; determining a location of the media device; determining that the location of the media device is within a geographic region; and generating a token corresponding to the media content in response to determining that the location of the media device is within the geographic area, wherein a payload of at least one tile of the distributed ledger identifies the token.

In another example, a non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to: receiving media content based on sensor data captured by at least one sensor of a media device; determining a location of the media device; determining that the location of the media device is within a geographic region; and generating a token corresponding to the media content in response to determining that the location of the media device is within the geographic area, wherein a payload of at least one tile of the distributed ledger identifies the token.

In another example, an apparatus for token generation is provided. The device comprises: means for receiving media content based on sensor data captured by at least one sensor of a media device; means for determining a location of the media device; determining that the location of the media device is within a geographic region; and means for generating a token corresponding to the media content in response to determining that the location of the media device is within a geographic area, wherein a payload of at least one tile of the distributed ledger identifies the token.

In another example, an apparatus for context token associated media output is provided that includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

In another example, a method for context token associated media output is provided. The method comprises the following steps: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

In another example, a non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

In another example, an apparatus for context token associated media output is provided. The device comprises: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor configured to: means for receiving sensor data captured by at least one sensor of a media device; means for identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; means for generating a representation of the media content corresponding to the token; and means for outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

In another example, an apparatus for token device transfer management is provided that includes at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to: identifying a token corresponding to media content in a payload of at least one tile of a distributed ledger, wherein a parameter of the token in the distributed ledger indicates that the token is associated with a first user; identifying a device associated with the token and the media content, wherein the device is associated with the first user; identifying that the device has been relocated to an area associated with a second user; and in response to identifying that the device has been relocated to the area, causing the parameter of the token in the distributed ledger to be modified from indicating that the token is associated with the first user to indicating that the token is associated with the second user.

In another example, a method for token device transfer management is provided. The method comprises the following steps: identifying a token corresponding to media content in a payload of at least one tile of a distributed ledger, wherein a parameter of the token in the distributed ledger indicates that the token is associated with a first user; identifying a device associated with the token and the media content, wherein the device is associated with the first user; identifying that the device has been relocated to an area associated with a second user; and in response to identifying that the device has been relocated to the area, causing the parameter of the token in the distributed ledger to be modified from indicating that the token is associated with the first user to indicating that the token is associated with the second user.

In another example, a non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to: identifying a token corresponding to media content in a payload of at least one tile of a distributed ledger, wherein a parameter of the token in the distributed ledger indicates that the token is associated with a first user; identifying a device associated with the token and the media content, wherein the device is associated with the first user; identifying that the device has been relocated to an area associated with a second user; and in response to identifying that the device has been relocated to the area, causing the parameter of the token in the distributed ledger to be modified from indicating that the token is associated with the first user to indicating that the token is associated with the second user.

In another example, an apparatus for token device transfer management is provided. The device comprises: identifying a token corresponding to media content in a payload of at least one tile of a distributed ledger, wherein a parameter of the token in the distributed ledger indicates that the token is associated with a first user; identifying a device associated with the token and the media content, wherein the device is associated with the first user; identifying that the device has been relocated to an area associated with a second user; and means for causing the parameter of the token in the distributed ledger to be modified from indicating that the token is associated with the first user to indicating that the token is associated with the second user in response to identifying that the device has been relocated to the area.

In some aspects, the media content includes at least a portion of the sensor data. In some aspects, the media content includes a modified variant of at least a portion of the sensor data.

In some aspects, the sensor data includes at least one image captured by at least one image sensor of the at least one sensor of the media device, and wherein the media content is based on at least one image of the at least one image. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: detecting at least a portion of an environment in the at least one image; and determining the location of the media device based at least in part on the detection of at least the portion of the environment in the at least one image. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: at least a portion of an environment in the at least one image is detected, and it is determined that at least the portion of the environment is located within the geographic area. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: detecting at least a portion of an individual in the at least one image; determining the identity of the individual; and setting a parameter of the token to indicate that the token is associated with the identity.

In some aspects, the sensor data includes positioning data based on receipt of at least one wireless signal by the at least one sensor, and wherein determining the location of the media device includes determining the location of the media device based at least in part on the positioning data. In some aspects, the at least one wireless signal comprises a short range wireless signal from a local device that is within a transmission range of the media device at least during receipt of the at least one wireless signal by the at least one sensor. In some aspects, the at least one wireless signal includes a Global Navigation Satellite System (GNSS) signal from a GNSS satellite.

In some aspects, the media content includes a map of the geographic area.

In some aspects, determining that the location of the media device is within the geographic area comprises: a location of the media device is determined to be within the geographic area based on at least one communication between the media device and a local device associated with the geographic area.

In some aspects, the method is performed using an apparatus comprising the local device. In some aspects, the method is performed using an apparatus comprising the media device. In some aspects, the method is performed using a device in the geographic region.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: generating the at least one tile in response to determining that the location of the media device is within the geographic area; and causing the at least one tile to be attached to the distributed ledger. In some aspects, the at least one chunk includes a hash of at least a portion of a previous chunk of the distributed ledger. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: the distributed ledger is generated in response to determining that the location of the media device is within the geographic area. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: in response to determining that the location of the media device is within the geographic region, sending a request to a computing device to generate at least one tile; receiving the at least one block; and attaching the at least one tile to the distributed ledger.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: parameters of the token are set to indicate that the token is associated with a user with whom the media device is associated.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: determining that the geographic area includes at least a threshold amount of people, wherein generating the token corresponding to the media content is performed in response to determining that the geographic area includes at least a threshold amount of people.

In some aspects, the sensor data includes image data captured by at least one image sensor of at least one sensor of the media device, wherein the anchor element includes an object, and wherein identifying a relationship between the media device and the anchor element includes identifying that the image data depicts the object. In some aspects, the object comprises an optical glyph, wherein the information indicative of the token is optically encoded based on the optical glyph. In some aspects, reference image data depicting the object is stored in a data store, and wherein identifying the image data to depict the object includes comparing the image data to the reference image data.

In some aspects, the sensor data includes location data indicating a location of a media device, wherein the anchor element includes an area, and wherein identifying a relationship between the media device and the anchor element includes identifying that the location of the media device is within the area. In some aspects, the sensor data includes location data indicating a location of the media device, wherein the anchor element includes a place, and wherein identifying a relationship between the media device and the anchor element includes identifying that the location of the media device is within a threshold range of the place.

In some aspects, the sensor data comprises audio data captured by at least one microphone in at least one sensor of the media device, wherein the anchor element comprises sound, and wherein identifying a relationship between the media device and the anchor element comprises identifying that the audio data comprises the sound.

In some aspects, outputting the representation of the media content includes causing a display to display at least a portion of the media content.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: identifying a media device pose of the media device based on the sensor data; and determining a media content pose for the media content based on the media device pose of the media device, wherein outputting the representation of the media content comprises outputting the representation of the media content that is posed (posed) according to the media content pose.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: identifying, based on the distributed ledger, that a parameter of the token indicates that the token is associated with a first user; determining a visual effect for the media content based on a parameter of the token indicating that the token is associated with a first user; and applying the visual effect to the media content, wherein outputting the representation of the media content comprises outputting a representation of the media content with the applied visual effect.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: determining that the first user and second user are associated according to a relationship type based on a data store, wherein the media device is associated with the second user, and wherein the visual effect for the media content corresponds to the relationship type. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: determining that the media device is associated with the first user, and wherein the visual effect for the media content corresponds to the first user. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: the method further includes determining that the first user is a celebrity based on a data store, and wherein the visual effect for the media content corresponds to the first user being the celebrity. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: a rating associated with the media content is determined based on a data store, and wherein the visual effect for the media content corresponds to the rating.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: determining that the token is identified in a data store, and wherein the visual effect for the media content corresponds to the data store. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: retrieving information about the token from the distributed ledger; and outputting the information about the token. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: outputting information about the token includes causing a display to display at least a portion of the information.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a first user, wherein the information identifies the first user. In some aspects, the information identifies a distributed ledger. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a smart contract, wherein the information identifies the smart contract. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: identifying based on the distributed ledger, wherein the information identifies a number of instances of the token. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: identifying a transfer platform configured for token transfer; and outputting an interface element corresponding to the media content, wherein the interface element is configured to initiate transfer of the token using the transfer platform upon interaction with the interface element.

In some aspects, the device is configured to present the media content.

In some aspects, an identifier of the device is stored in the distributed ledger, and wherein identifying the device is based on the identifier.

In some aspects, the device includes an interactive element that indicates the token, and wherein identifying the token is based on interactions with the interactive element. In some aspects, the interaction comprises an optical glyph, and wherein the identifier of the token is optically encoded based on the optical glyph.

In some aspects, image data is received; detecting that the device is represented in the image data; and identifying the token based on detecting that the device is represented in the image data.

In some aspects, identifying that the device has been relocated to an area associated with the second user includes: it is identified that the device has been relocated from a first area associated with the first user. In some aspects, identifying that the device has been relocated to an area associated with the second user includes: one or more additional devices located in the area are identified as being associated with the second user. In some aspects, identifying that the device has been relocated to an area associated with the second user includes: a Wireless Local Area Network (WLAN) in the area is identified as being associated with the second user. In some aspects, identifying that the device has been relocated to the area associated with the second user includes: determining location data from at least one location sensor of the device indicates that the device is located in the area, and wherein the area is a geographic area. In some aspects, identifying that the device has been relocated to an area associated with the second user includes: determining that the location data from the at least one location sensor of the device indicates that the device is within a range of the location of the second user, wherein the area associated with the second user is within a range of the location of the second user.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: causing parameters of the tokens in the distributed ledger to be modified includes: causing a new chunk to be appended to the distributed ledger, wherein parameters of tokens in the distributed ledger are modified based on a payload of the new chunk.

In some aspects, causing the new tile to be appended to the distributed ledger includes generating the new tile.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: sending, to a first user device associated with the first user, a request to modify parameters of the token in the distributed ledger from indicating that the token is associated with the first user to indicating that the token is associated with the second user; and receiving the authorization from the first user device. In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: sending a request to a second user device associated with the second user to modify parameters of the token in the distributed ledger from indicating that the token is associated with the first user to indicating that the token is associated with the second user; and receiving the authorization from the second user device.

In some aspects, one or more of the above methods, apparatus, and computer-readable media further comprise: identifying, in the distributed ledger, a smart contract associated with the token, wherein the smart contract indicates that parameters of the token are modified in response to a condition, wherein causing parameters of the token in the distributed ledger to be modified comprises: the smart contract is executed in response to identifying the condition, wherein identifying the condition is based on identifying that the device has been relocated to an area associated with the second user.

In some aspects, the device comprises a head mounted display. In some aspects, the apparatus comprises a mobile handset. In some aspects, the apparatus comprises a wireless communication device. In some aspects, the apparatus comprises a wearable device. In some aspects, the apparatus comprises a server. In some aspects, the device is in a geographic region.

In some aspects, the apparatus is, and/or comprises a wearable device, an augmented reality device (e.g., a Virtual Reality (VR) device, an Augmented Reality (AR) device, or a Mixed Reality (MR) device), a mobile device (e.g., a mobile phone or so-called "smart phone" or other mobile device), a camera, a personal computer, a laptop computer, a server computer, a computing device or component of a vehicle or vehicle, or other device. In some aspects, the apparatus includes one or more cameras for capturing one or more images. In some aspects, the apparatus further comprises a display for displaying one or more images, notifications, and/or other displayable data. In some aspects, the above-described apparatus may include one or more sensors (e.g., one or more Inertial Measurement Units (IMUs), such as one or more gyroscopes, one or more accelerometers, any combination thereof, and/or other sensors).

This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in isolation to determine the scope of the claimed subject matter. The subject matter should be understood with reference to appropriate portions of the entire specification of this patent, any or all of the accompanying drawings, and each claim.

The foregoing and other features and embodiments will become more fully apparent upon reference to the following description, claims and accompanying drawings.

Drawings

Illustrative embodiments of the present application are described in detail below with reference to the following drawings:

FIG. 1 is a block diagram illustrating an example architecture of an image capture and processing system according to some examples;

FIG. 2 is a block diagram illustrating an example architecture of a digital asset tracking system that may be used to track digital assets associated with a location according to some examples;

FIG. 3A is a perspective view illustrating a Head Mounted Display (HMD) used as a media device as part of a digital asset tracking system according to some examples;

fig. 3B is a perspective view illustrating the Head Mounted Display (HMD) of fig. 3A worn by a user according to some examples;

FIG. 4A is a perspective view showing a front surface of a mobile handset that includes a front facing camera and that may be used as a media device as part of a digital asset tracking system, according to some examples;

FIG. 4B is a perspective view showing a rear surface of a mobile handset including a read-facing camera and that may be used as a media device as part of a digital asset tracking system, according to some examples;

FIG. 5 is a block diagram illustrating three consecutive blocks of a blockchain ledger that may be used to track digital assets associated with locations in a geographic area according to some examples;

FIG. 6 is a block diagram illustrating an example token that may be non-replaceable and that may represent digital assets associated with locations in a geographic area tracked in a distributed ledger, according to some examples;

FIG. 7 is a block diagram illustrating a Directed Acyclic Graph (DAG) ledger configured to track digital assets associated with locations in a geographic area, according to some examples;

FIG. 8A is a perspective view illustrating a user using a media device to capture a digital asset (image) of a portrait in a museum according to some examples;

FIG. 8B is a conceptual diagram illustrating information about a token associated with the digital asset of FIG. 8A according to some examples;

FIG. 9A is a perspective view illustrating a user using a media device to capture digital assets (images) of a number of people including individuals identified as Bob, according to some examples;

FIG. 9B is a conceptual diagram illustrating information about a token associated with the digital asset of FIG. 9A according to some examples;

FIG. 10A is a perspective view illustrating a user using a media device to generate a digital asset (image) including virtual objects synthesized into a real scene according to some examples;

FIG. 10B is a conceptual diagram illustrating information about a token associated with the digital asset of FIG. 10A according to some examples;

FIG. 11A is a perspective view illustrating a user using a media device to generate a digital asset (map) of a hiking path according to some examples;

FIG. 11B is a conceptual diagram illustrating information about a token associated with the digital asset of FIG. 11A according to some examples;

FIG. 12A is a perspective view showing a digital asset (image) of a user using an ownership device to purchase portraits in a museum according to some examples;

FIG. 12B is a conceptual diagram illustrating information about a token associated with the digital asset of FIG. 12A according to some examples;

FIG. 13 is a conceptual diagram illustrating an anchor element associated with a token and detection of the anchor element by a media device triggering display of a digital asset corresponding to the token on the media device, according to some examples;

FIG. 14 is a conceptual diagram illustrating a token device associated with a token in a distributed ledger and transferring the token device from a first user to a second user according to some examples;

FIG. 15A is a conceptual diagram illustrating the generation and input of smart contracts into a distributed ledger according to some examples;

FIG. 15B is a conceptual diagram illustrating execution of a smart contract according to an aspect of the present disclosure, according to some examples;

FIG. 16A is a flowchart illustrating operations for context token generation according to some examples;

FIG. 16B is a flowchart illustrating operations for tracking digital assets associated with a location according to some examples;

FIG. 17 is a flow diagram illustrating a process for context token associated media output according to some examples;

FIG. 18 is a flow diagram illustrating a process for token device transfer management according to some examples; and

FIG. 19 is a diagram illustrating an example of a computing system for implementing certain aspects described herein.

Detailed Description

Certain aspects and embodiments of the disclosure are provided below. Some of these aspects and embodiments may be applied independently, and some of them may be applied in combination, as will be apparent to those skilled in the art. In the following description, for purposes of explanation, specific details are set forth in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, that the various embodiments may be practiced without these specific details. The drawings and description are not intended to be limiting.

The following description merely provides exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It being understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the application as set forth in the appended claims.

People often find it interesting to own, use or trade unique or rare items related to celebrities, activities or places that are respected by the person. For example, people often attempt to be signed by concerts with their clothing or music albums by well-known musicians to commemorate participation in such concerts, thereby turning the signed clothing or music albums into unique items. Similarly, people often seek to purchase packages, props, animation episodes, and other items for creating movies or television programs.

A camera is a device that receives light using an image sensor and captures image frames, such as still images or video frames. The terms "image," "image frame," and "frame" are used interchangeably herein. The camera may be configured with various image capturing and image processing settings. Different settings result in images with different appearances. Some camera settings are determined and applied prior to or during capturing one or more image frames, such as ISO, exposure time, aperture size, f-stop (f/stop), shutter speed, focus, and gain. For example, settings or parameters may be applied to an image sensor that captures one or more image frames. Other camera settings may configure post-processing of one or more image frames, such as changes to contrast, brightness, saturation, sharpness, color level (levels), curve, or color. For example, settings or parameters may be applied to a processor (e.g., an image signal processor or ISP) for processing one or more image frames captured by an image sensor.

The digital assets may include, for example, images or video captured by a camera, audio clips captured by a microphone, three-dimensional point clouds and/or models from distance sensors, and so forth. In general, digital assets are replaceable, meaning that any one copy of a given digital asset is interchangeable with any other copy of the same digital asset.

In some examples, systems and techniques for creating, modifying, tracking, authenticating, and/or transferring non-replaceable digital assets associated with a device location are described herein. The media device may include sensors such as image sensors, positioning sensors (e.g., accelerometers, gyroscopes, inertial Measurement Units (IMUs), global Navigation Satellite System (GNSS) receivers), distance sensors (e.g., light detection and ranging (LIDAR) sensors, radio detection and ranging (RADAR) sensors, sound detection and ranging (SODAR) sensors, sound navigation and ranging (sonor) sensors, time of flight (ToF) sensors, structured light sensors), microphones, other sensors described herein, or combinations thereof. The media device may capture sensor data using its sensors. The media device may generate and/or obtain media data based on its sensor data. The media data may include sensor data. In some examples, the media data may include processed and/or modified variants of the sensor data. For example, the media data may include virtual content (e.g., virtual objects) generated for XR output. The media data may include a map generated based on positioning data from the positioning sensor. The media data may include a High Dynamic Range (HDR) image generated by combining a plurality of images.

Positioning data indicative of the pose of the media device during capture of the sensor data may be obtained from the media device, e.g., from a positioning sensor of the media device and/or based on one or more short-range wireless communications between the media device and the local device. Positioning data indicative of the pose of the media device during capture of the sensor data may be obtained from a local device in communication with the media device using one or more short-range wireless communications. The media device may send media data to the network device. Based on the positioning data, the network device may verify that the media device is in a predetermined geographic region during capture of the sensor data. The geographical area may be, for example, a museum, a stadium, a concert venue, or the like. In some cases, the geographic area may be defined by a range of the range of short-range wireless communications of the local device, and verification of the location of the media device may be based on verifying that communications sent between the media device and the local device were accurately received by the media device and/or the local device. In response to verifying that the media device is in a predetermined geographic region during capture of the sensor data, the network device may generate a token for the media data. The network device may input tokens into a distributed ledger (such as a blockchain ledger) by generating a tile with tokens in its payload and appending the tile to the distributed ledger, or by requesting the tile generating device to generate a tile with tokens in its payload and appending the tile to the distributed ledger. The token may be associated with an intelligent contract stored in the distributed ledger that controls the transfer of tokens associated with the media data. In some cases, the network device may be part of a media device.

In some examples, the media device may be an extended reality (XR) device. An XR device is a device that displays an environment to a user, and may include, for example, a Head Mounted Display (HMD), glasses (e.g., augmented Reality (AR) glasses), a mobile handheld device, or other device. The environment is at least partially different from the real world environment in which the user and the device are located, and may for example include virtual content. In some examples, the environment displayed to the user by the XR device may be at least partially virtual. In some cases, a user may interactively change the view of the environment displayed by the XR device, for example, by tilting the XR device and/or moving the XR device laterally. Tilting the XR device may include tilting or rotating along a pitch axis, a yaw axis, a roll axis, or a combination thereof. Lateral movement of the XR device may include lateral movement along a path mapped within a three-dimensional volume having 3 perpendicular axes, such as the X, Y axis and the Z axis. An XR device that tracks only the rotation of the XR device may be referred to as an XR device having three degrees of freedom (3 DoF). An XR device that tracks both tilting and lateral movement of the XR device may be referred to as an XR device having six degrees of freedom (6 DoF). The augmented reality (XR) may include Virtual Reality (VR), augmented Reality (AR), mixed Reality (MR), or a combination thereof.

Generating tokens corresponding to media data and entering the tokens into a distributed ledger may provide technical advantages over ordinary transfer of images or other digital assets. The token transitions the media data from the replaceable state to the non-replaceable state, allowing individual copies or instances of the media data to be tracked, owned, transferred, rented, licensed, etc., safely, efficiently, and automatically. Having the token generated is based on verifying that the location of the media device may provide additional security and verification in the geographic region during capture of the sensor data that the representation of the object, environment, or individual in the media data is authentic.

Various aspects of the present application will be described with reference to the accompanying drawings. Fig. 1 is a block diagram showing the architecture of an image capturing and processing system 100. The image capture and processing system 100 includes various components for capturing and processing images of a scene (e.g., images of the scene 110). The image capture and processing system 100 may capture individual images (or photographs) and/or may capture video comprising a plurality of images (or video frames) in a particular sequence. The lens 115 of the system 100 faces the scene 110 and receives light from the scene 110. The lens 115 bends the light toward the image sensor 130. The light received by lens 115 passes through an aperture controlled by one or more control mechanisms 120 and is received by image sensor 130.

One or more control mechanisms 120 may control exposure, focus, and/or zoom based on information from image sensor 130 and/or based on information from image processor 150. One or more control mechanisms 120 may include a plurality of mechanisms and components; for example, control mechanism 120 may include one or more exposure control mechanisms 125A, one or more focus control mechanisms 125B, and/or one or more zoom (zoom) control mechanisms 125C. One or more of control mechanisms 120 may include additional control mechanisms other than those shown, such as control mechanisms that control analog gain, flash, HDR, depth of field, and/or other image capture attributes.

Focus control mechanism 125B in control mechanism 120 may achieve a focus setting. In some examples, focus control mechanism 125B stores the focus setting in a memory register. Based on the focus setting, the focus control member 125B can adjust the position of the lens 115 with respect to the position of the image sensor 130. For example, based on the focus setting, the focus control member 125B may move the lens 115 closer to the image sensor 130 or farther from the image sensor 130 by driving a motor or a servo, thereby adjusting the focus. In some cases, additional lenses may be included in the system 100, such as one or more microlenses over each photodiode of the image sensor 130, each of which bends light received from the lens 115 toward the corresponding photodiode before the light reaches the photodiode. The focus setting may be determined via Contrast Detection Autofocus (CDAF), phase Detection Autofocus (PDAF), or some combination thereof. Focus settings may be determined using control 120, image sensor 130, and/or image processor 150. The focus setting may be referred to as an image capture setting and/or an image processing setting.

The exposure control mechanism 125A in the control mechanism 120 can obtain an exposure setting. In some cases, exposure control mechanism 125A stores the exposure settings in a memory register. Based on the exposure setting, the exposure control mechanism 125A may control the size of the aperture (e.g., aperture size or f-stop), the duration of the aperture opening (e.g., exposure time or shutter speed), the sensitivity of the image sensor 130 (e.g., ISO speed or film speed), the analog gain applied by the image sensor 130, or any combination thereof. The exposure settings may be referred to as image capture settings and/or image processing settings.

The zoom control mechanism 125C in the control mechanism 120 can obtain a zoom setting. In some examples, scaling control 125C stores the scaling settings in a memory register. Based on the zoom setting, the zoom control mechanism 125C may control the focal length of a combination of lens elements (lens assembly) including the lens 115 and one or more additional lenses. For example, the zoom control mechanism 125C may control the focal length of the lens assembly by driving one or more motors or servos to move one or more lenses relative to each other. The zoom settings may be referred to as image capture settings and/or image processing settings. In some examples, the lens assembly may include a confocal zoom lens or a zoom lens. In some examples, the lens assembly may include a focusing lens (which may be lens 115 in some cases) that first receives light from the scene 110, and then the light passes through an afocal zoom system between the focusing lens (e.g., lens 115) and the image sensor 130 before the light reaches the image sensor 130. In some cases, afocal scaling systems may include two positive (e.g., converging, convex) lenses having equal or similar focal lengths (e.g., within a threshold difference), with a negative (e.g., diverging, concave) lens therebetween. In some cases, zoom control mechanism 125C moves one or more of the lenses in the afocal zoom system, such as one or both of the positive lenses and the negative lens.

The image sensor 130 includes one or more arrays of photodiodes or other photosensitive elements. Each photodiode measures the amount of light that ultimately corresponds to a particular pixel in the image produced by the image sensor 130. In some cases, different photodiodes may be covered by different color filters, and thus light matching the color of the color filter covering the photodiodes may be measured. For example, a Bayer (Bayer) filter includes a red filter, a blue filter, and a green filter, wherein each pixel of an image is generated based on red light data from at least one photodiode covered in the red filter, blue light data from at least one photodiode covered in the blue filter, and green light data from at least one photodiode covered in the green filter. Instead of or in addition to red, blue and/or green color filters, other types of color filters may use yellow, magenta and/or cyan (also referred to as "emerald") color filters. Some image sensors may not have color filters at all, but may instead use different photodiodes (in some cases vertically stacked) throughout the pixel array. Different photodiodes throughout the pixel array may have different spectral sensitivity curves and thus respond to different wavelengths of light. Monochrome image sensors may also lack color filters and thus color depth.

In some cases, the image sensor 130 may alternatively or additionally include opaque and/or reflective masks that block light from reaching certain photodiodes or portions of certain photodiodes at certain times and/or from certain angles, which may be used for Phase Detection Autofocus (PDAF). The image sensor 130 may also include an analog gain amplifier to amplify the analog signal output by the photodiode and/or an analog-to-digital converter (ADC) to convert the analog signal output of the photodiode (and/or amplified by the analog gain amplifier) to a digital signal. In some cases, certain components or functions discussed with respect to one or more control mechanisms 120 may alternatively or additionally be included in image sensor 130. The image sensor 130 may be a Charge Coupled Device (CCD) sensor, an electron multiplying CCD (EMCCD) sensor, an Active Pixel Sensor (APS), a Complementary Metal Oxide Semiconductor (CMOS), an N-type metal oxide semiconductor (NMOS), a hybrid CCD/CMOS sensor (e.g., sCMOS), or some other combination thereof.

Image processor 150 may include one or more processors, such as one or more of one or more Image Signal Processors (ISPs) (including ISP 154), one or more host processors (including host processor 152), and/or any other type of processor 1019 discussed with respect to computing system 0019. The host processor 152 may be a Digital Signal Processor (DSP) and/or other type of processor. In some implementations, the image processor 150 is a single integrated circuit or chip (e.g., referred to as a system on a chip or SoC) that includes the host processor 152 and the ISP 154. In some cases, the chip may also include one or more input/output ports (e.g., input/output (I/O) ports 156), a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a broadband modem (e.g., 3G, 4G or LTE, 5G, etc.), memory, connection components (e.g., bluetooth, global Positioning System (GPS), etc.), any combination thereof, and/or other components. The I/O ports 156 may include any suitable input/output ports or interfaces in accordance with one or more protocols or specifications, such as an inter-integrated circuit 2 (I2C) interface, an inter-integrated circuit 3 (I3C) interface, a Serial Peripheral Interface (SPI) interface, a serial general purpose input/output (GPIO) interface, a Mobile Industrial Processor Interface (MIPI) (such as a MIPI CSI-2 Physical (PHY) layer port or interface, an advanced high performance bus (AHB) bus, any combination thereof, and/or other input/output ports.

The image processor 150 may perform a number of tasks such as demosaicing, color space conversion, image frame downsampling, pixel interpolation, automatic Exposure (AE) control, automatic Gain Control (AGC), CDAF, PDAF, automatic white balancing, merging of image frames to form an HDR image, image recognition, object recognition, feature recognition, receipt of input, management output, management memory, or some combination thereof. The image processor 150 may store the image frames and/or the processed images in Random Access Memory (RAM) 140 and/or 2019, read Only Memory (ROM) 145 and/or 2519, a cache, a memory unit, another storage device, or some combination thereof.

Various input/output (I/O) devices 160 may be connected to the image processor 150. The I/O device 160 may include a display screen, a keyboard, a keypad, a touch screen, a touch pad, a touch sensitive surface, a printer, any other output device 3519, any other input device 4519, or some combination thereof. In some cases, subtitles may be input into the image processing device 105B through a physical keyboard or keypad of the I/O device 160, or through a virtual keyboard or keypad of a touch screen of the I/O device 160. I/O160 may comprise one or more ports, jacks, or other connectors that enable wired connections between system 100 and one or more peripheral devices, through which system 100 may receive data from and/or transmit data to one or more peripheral devices. The I/O160 may include one or more wireless transceivers that enable a wireless connection between the system 100 and one or more peripheral devices, from which the system 100 may receive data and/or transmit data to the one or more peripheral devices over the wireless connection. Peripheral devices may include I/O devices 160 of any of the types previously described, and may themselves be considered I/O devices 160 once they are coupled to ports, jacks, wireless transceivers, or other wired and/or wireless connectors.

In some cases, the image capture and processing system 100 may be a single device. In some cases, the image capture and processing system 100 may be two or more separate devices, including an image capture device 105A (e.g., a camera) and an image processing device 105B (e.g., a computing device coupled to the camera). In some implementations, the image capture device 105A and the image processing device 105B may be coupled together wirelessly, e.g., via one or more wires, cables, or other electrical connectors, and/or via one or more wireless transceivers. In some implementations, the image capture device 105A and the image processing device 105B may be disconnected from each other.

As shown in fig. 1, a vertical dashed line divides the image capturing and processing system 100 of fig. 1 into two parts representing the image capturing device 105A and the image processing device 105B, respectively. Image capturing device 105A includes lens 115, control mechanism 120, and image sensor 130. The image processing device 105B includes an image processor 150 (including ISP 154 and host processor 152), RAM 140, ROM 145 and I/O160. In some cases, certain components shown in image capture device 105A (such as ISP 154 and/or host processor 152) may be included in image capture device 105A.

The image capture and processing system 100 may include an electronic device such as a mobile or stationary telephone mobile handset (e.g., smart phone, cellular phone, etc.), desktop computer, laptop or notebook computer, tablet computer, set-top box, television, camera, display device, digital media player, video game console, video streaming device, internet Protocol (IP) camera, or any other suitable electronic device. In some examples, the image capture and processing system 100 may include one or more wireless transceivers for wireless communications, such as cellular network communications, 802.11Wi-Fi communications, wireless Local Area Network (WLAN) communications, or some combination thereof. In some implementations, the image capture device 105A and the image processing device 105B may be different devices. For example, the image capture device 105A may include a camera device and the image processing device 105B may include a computing device, such as a mobile handheld device, desktop computer, or other computing device.

Although image capture and processing system 100 is shown as including certain components, those skilled in the art will appreciate that image capture and processing system 100 may include more components than those shown in FIG. 1. The components of the image capture and processing system 100 may include software, hardware, or one or more combinations of software and hardware. For example, in some implementations, components of image capture and processing system 100 may include and/or be implemented using electronic circuitry or other electronic hardware, which may include one or more programmable electronic circuits (e.g., microprocessors, GPU, DSP, CPU, and/or other suitable electronic circuits), and/or may include and/or be implemented using computer software, firmware, or any combination thereof to perform the various operations described herein. The software and/or firmware may include one or more instructions stored on a computer-readable storage medium and executable by one or more processors of the electronic device to implement the image capture and processing system 100.

FIG. 2 is a block diagram illustrating an example architecture of a digital asset tracking system 200 that may be used to track digital assets associated with a location according to some examples. The digital asset tracking system 200 includes a media device 205. The media device 205 may be a computing system 0019. The media device 205 may be the image capture device 105A, the image processing device 105B, and/or the image capture and processing system 100. In some aspects, the media device 205 may be an extended reality (XR) device. In some examples, the media device 205 may be a mobile handheld device 410, a smart phone, a media player device, a camera, a Head Mounted Display (HMD) 310, a fitness tracker device, a smart watch, a wearable device, or a combination thereof.

The media device 205 includes one or more sensors 210. The sensors 210 may include, for example, one or more gesture sensors 215 and one or more media sensors 220. The one or more attitude sensors 215 may include, for example, one or more accelerometers, gyroscopes, inertial Measurement Units (IMUs), global Navigation Satellite System (GNSS) receivers, or combinations thereof. The one or more media sensors 220 may include, for example, one or more image sensors, distance sensors, microphones, other sensors described herein, or a combination thereof. The distance sensor may include a light detection and ranging (LIDAR) sensor, a radio detection and ranging (RADAR) sensor, a sound detection and ranging (SODAR) sensor, a sound navigation and ranging (SONAR) sensor, a time-of-flight (ToF) sensor, a structured light sensor, or a combination thereof. The media device 205 may use the sensor 210 to capture pose data 225 that identifies the pose of the media device 205. In some cases, the pose data 225 may be referred to as position data or location data. The pose data 225 of the media device may include a location (e.g., latitude, longitude, and altitude, or coordinates in another form of 3D space) of the media device 205, an orientation (e.g., pitch, yaw, and/or roll) of the media device, or a combination thereof. In some examples, the media device 205 may use the data captured by the gesture sensor 215 to capture the gesture data 225 at least in part by identifying movement of the media device 205 based on an output of the gesture sensor 215 indicative of the movement of the media device 205. In some examples, the media device 205 may use data captured by the media sensor 220 (e.g., an image captured by the image sensor) to capture gesture data 225 and/or positioning data at least in part by identifying movement of the media device 205 based on a field of view (FOV) of the media sensor 220 (e.g., a FOV of an environment depicted in the data captured by the media sensor 220) changing or shifting in a manner that indicates movement of the media device 205. In some examples, the data captured by the media sensor 220 (e.g., camera data captured by the image sensor) may be pose data 225 and/or positioning data, and/or may be the basis of the pose data 225 and/or positioning data. In some examples, the media device 205 may identify 3D coordinates of features depicted in one or more images or other data captured by the media sensor 220, for example, by feature detection, feature extraction, feature tracking, feature mapping, stereo mapping, environmental mapping, visual localization, positioning, or a combination thereof. In some examples, the media device 205 may generate a map of the environment based on one or more features detected, extracted, tracked, and/or mapped by the media device 205.

The media device 205 may capture sensor data 230 using the sensor 210. In some examples, the sensor data 230 may include images, videos, depth map images, depth map videos, audio clips, or combinations thereof captured by the media sensor 220. In some cases, the sensor data 230 may identify metadata, for example, a timestamp identifying the capture and/or image capture settings, such as aperture speed, aperture size, exposure time, ISO, focal length, focus, flash, zoom, analog gain, digital gain, automatic White Balance (AWB) settings, or a combination thereof. The media device 205 may capture the gesture data 225 at a time concurrent with the capture of the sensor data 230. The media device 205 may capture the sensor data 230 at the same time as the gesture data 225 is captured. The media device 205 may capture the gesture data 225 at a time during the capture of the sensor data 230. The media device 205 may capture the sensor data 230 at a time during the capture of the gesture data 225.

The media device 205 may include a media processor 235. Using the media processor 235, the sensor data 230, and/or the gesture data 225, the media device 205 can generate and/or obtain media data 250. In some examples, the media data may be or include sensor data 230, gesture data 225, or both. In such examples, the media device 205 may obtain the media data 250 directly from the sensor 210 and/or indirectly through the media processor 235, the media processor 235 may append additional data (e.g., headers), place the data 225-230 from the sensor 210 into one or more container files (e.g., ISO container format or ISO-based container format), merge the gesture data 225 with the sensor data 230 and/or with metadata (corresponding to the sensor data 230 and/or gesture data 225), or a combination thereof. In some examples, the media processor 235 may process the sensor data 230 and/or the pose data 225, for example, by performing any of the processing operations generally discussed with respect to the image processing device 105B or the image capture and processing system 100. For example, the media processor 235 may perform demosaicing, noise reduction, sharpening, saturation adjustment, brightness adjustment, contrast adjustment, chroma adjustment, hue adjustment, gain, other processing tasks discussed herein, or a combination thereof. In some examples, media processor 235 may include image processor 150, ISP 154, host processor 152, processor 1910, or a combination thereof. In some examples, media processor 235 may combine multiple pieces of sensor data 230, for example, by merging multiple images into a High Dynamic Range (HDR) image that is at least a portion of media data 250. In some examples, as part of generating media data 250, media processor 235 may apply one or more filters to sensor data 230.

The media processor 235 may also include specialized elements related to augmented reality (XR) operations, for example, where the media device 205 is an XR device. For example, the media processor 235 may include a virtual content generator 240 that may generate virtual content, such as virtual objects, virtual characters, virtual environments, virtual equipment, virtual apparel, virtual items, virtual sports equipment, virtual weapons, and the like. Virtual content may include virtual objects, characters, environments, equipment, apparel, items, sporting equipment, weapons, and/or other content related to one or more video games or other XR experiences. Examples of virtual content generated by virtual content generator 240 include virtual object 1045 (virtual dog) of fig. 10A-10B. The media processor 235 may include an image compositor 245, and the image compositor 245 may generate media data 250 by merging virtual content generated by the virtual content generator 240 with the sensor data 230. For example, the image synthesizer 245 may overlay the virtual content generated by the virtual content generator 240 over portions of the sensor data 230. In some examples, the image synthesizer 245 may adjust the pose (e.g., position and/or orientation) of the virtual content to match the environment depicted in the sensor data 230 and/or adjust the pose of the virtual content based on the pose data 225 (e.g., to make the virtual content appear to rest on a surface in the real environment depicted in the sensor data 230). In some examples, the image compositor 245 may adjust the illumination and/or shading of the virtual content to match the environment depicted in the sensor data 230 and/or adjust the illumination and/or shading of the virtual content based on the gesture data 225 (e.g., to match the illumination and/or shading of the virtual object with the real illumination of the real environment depicted in the sensor data 230). In some examples, if image compositor 245 determines that the real world object depicted in sensor data 230 is in front of the location at which image compositor 245 locates the virtual content in the real environment depicted in sensor data 230, image compositor 245 may at least partially occlude the virtual content with the real world object depicted in sensor data 230. For example, a person may appear to walk "in front of" the virtual content, and the image compositor 245 may realistically occlude a view of the virtual content in the media data 250. Examples of media data 250 including virtual content include digital assets 1040 of fig. 10A-10B, which depict virtual objects 1045 (virtual dogs) overlaid on a real environment.

The media processor 235 may also include a map generator 247, and the map generator 247 may generate one or more maps based on the gesture data 225 and/or the sensor data 230. Such a map may identify one or more routes along which the media device 205 moves across one or more time periods. In some examples, the map may show routes taken by a user carrying the media device 205, such as hiking routes, walking routes, jogging routes, running routes, bicycle routes, skateboard routes, bus routes, driving routes, routes moved during athletic activity, and the like. The media data 250 generated by the media processor 235 may include a map. For example, the digital assets 1140 of fig. 11A-11B are examples of media data 250 including maps generated by the map generator 247.

Media device 205 may include a communication interface 255, and communication interface 255 may include one or more communication interfaces 1940. Communication interface 255 may include a short-range wireless transceiver 260. Short-range wireless transceiver 260 may receive and/or transmit communications 272 with short-range wireless transceiver 275 of local device 270 via one or more short-range communication signals that conform to a short-range communication protocol. Either or both of the short-range wireless transceivers 260 and 275 may include, for example Transceiver, < >>Low-power consumption (BLE) transceiver, < >>Transceiver, near Field Communication (NFC) transceiver, radio Frequency Identification (RFID) transceiver, radio transceiver, microwave transceiver, visible lightCommunication (VLC) transceivers, wi-Fi transceivers, personal Area Network (PAN) transceivers, wireless Local Area Network (WLAN) transceivers, wide Area Network (WAN) transceivers, cellular network transceivers, ultrasonic transceivers, subsonic transceivers, sonic transceivers, any type of transceiver identified with respect to network transceivers 265 and 285, and other types of transceivers, or combinations thereof. In some examples, as part of capturing gesture data 225, media device 205 may receive and/or transmit one or more of communications 272 with local device 270. For example, the local device 270 may have a verified location and may be, for example, a local device 270 set and managed by a venue such as a museum, concert venue, movie theatre, stadium, or the like. If the media device 205 and the local device 270 are within short range wireless communication signals of each other (e.g., within successful transmission and reception of one or more communications 272), then the media device 205 is in the vicinity of the local device 270.

Local device 270 may determine and/or store communication 272 (block 277). For example, the local device 270 may determine the content of any communication 272 that the local device 270 sends to the media device 205, and may store the content. Also, the local device 270 can determine the content of any communication 272 that the local device 270 receives from the media device 205, and can store the content. The media device 205 may determine and/or store the communication 272 (block 278). For example, the media device 205 can determine the content of any communication 272 that the media device 205 sends to the local device 270, and can store the content. Likewise, the media device 205 can determine the content of any communication 272 that the media device 205 receives from the local device 270 and can store the content. Ensuring that the stored content of these communications 272 matches the content stored at the media device 205 and at the local device 270 may be used to verify that the pose of the media device 205 is in the geographic region associated with the local device 270 (block 290). In some examples, the media device 205 may send communications 272 with a plurality of local devices 270. In some examples, local device 270 may be a beacon device with a known location. In some examples, the local device 270 may be a wireless network access point (e.g., wi-Fi, WLAN) with a known location. In some examples, the local device 270 may be a cellular network access point (e.g., a cellular tower) with a known location.

The communication interface 255 of the media device 205 may include a network transceiver 265. The network transceiver 265 may transmit communications 282 along a network to one or more network transceivers 285 of one or more network devices 280 and/or receive communications 282 from one or more network transceivers 285 to one or more network devices 280. Either or both of the network transceivers 265 and/or 285 may include one or more wired transceivers, one or more wireless transceivers, or a combination thereof. Either or both of the network transceivers 265 and/or 285 may include, for example, one or more ethernet transceivers, wi-Fi transceivers, wireless Local Area Network (WLAN) transceivers, wide Area Network (WAN) transceivers, cellular network transceivers, any type of transceiver identified with respect to the short-range wireless transceivers 260 and 275, and other types of transceivers, or combinations thereof. The media device 205 may send media data 250 and/or gesture data 225 to the network device 280 via the communication 282. The network device 280 may verify that the pose of the media device 205 is in the geographic region (block 290). In some aspects, a geographic area may be associated with local device 270. For example, the local device 270 may be located in or near a geographic area. At least a portion of the geographic area may include short range wireless signal transmission and/or reception ranges for each of the one or more local devices 270. In some examples, verifying that the pose of the media device 205 is in the geographic region associated with the local device 270 (block 290) may include verifying that the content of the communication 272 matches as stored at the local device 270 (block 278) and as stored at the media device 205 (block 278). For example, the content of communication 272 sent from local device 270 to media device 205 matches and is therefore stored on both devices (blocks 277 and 278), and/or the content of communication 272 sent from media device 205 to local device 270 matches because of being stored on both devices (blocks 277 and 278). In some examples, the network device 280 may verify that the pose of the media device 205 is in the geographic area at least in part by verifying that the location of the media device 205 indicated by the pose data 225 is within a predetermined boundary or geofence of the geographic area (block 290). In some examples, the geographic area may correspond to an interior of one or more buildings corresponding to a museum, movie theatre, shopping mall, or another indoor venue. In some examples, the geographic area may correspond to an interior of an outdoor venue (e.g., an outdoor concert venue, an outdoor sports venue), such as within a fence, enclosure, seating layout, or other boundary marker of the venue. In some examples, the geographic area may correspond to an outdoor area including one or more indoor areas, such as an outdoor food plaza area with a plurality of restaurants, or an outdoor theme park with a plurality of attractions, some of which may be indoor attractions.

In some examples, the transmit time and receive time of one or more of the communications 272 may be identified and/or stored (e.g., in the stored communications of block 277 and/or the stored communications of block 278). In some examples, the transmit time and the receive time of one or more of the communications 272 may be used to identify the location of the media device 205 (e.g., may be used as positioning data) and/or may be used to verify that the pose of the media device 205 is in a geographic area (block 290). For example, the transmit time and receive time of one or more of the communications 272 may be subtracted to identify the duration of communication 272 propagation, which may be used to determine the distance between the media device 205 and the local device 270.

In some examples, the signal transmission frequency and the signal reception frequency of one or more of the communications 272 may be identified and/or stored (e.g., in the stored communications of block 277 and/or the stored communications of block 278). In some examples, the signal transmission frequency and signal reception frequency of one or more of the communications 272 may be used to identify the location of the media device 205 (e.g., may be used as positioning data) and/or may be used to verify that the pose of the media device 205 is in a geographic area (block 290). For example, the signal transmission frequency and signal reception frequency of one or more of the communications 272 may be subtracted to identify the difference in signal frequency as the communications 272 propagate, which may be used to determine the distance between the media device 205 and the local device 270.

The location of the media device 205 may be identified as along a circle drawn around the local device 270, the circle having a radius of the length of the identified distance (e.g., based on the transmit time and the receive time, and/or based on the signal transmit frequency and the signal receive frequency). Based on the point at which the resulting circles intersect, the more local devices 270 that are used, the more accurately the location of the media device 205 can be identified. If three or more local devices 270 are used, the location of the media device 205 may be scaled down to a single point, which may be referred to as triangulation. Thus, triangulation based on signals from multiple local devices 270 may be used to identify the location of the media device 205 (e.g., may be used as positioning data) and/or may be used to verify that the pose of the media device 205 is in a geographic area (block 290).

In response to verifying that the pose of media device 205 is in the geographic area (block 290), network device 280 may generate one or more tokens corresponding to media data 250, may generate one or more tiles in distributed ledger 295 to store the tokens therein, and/or may generate distributed ledger 295 itself (block 292). Examples of tokens may include token 600, token 860, token 960, token 1060, token 1160, and token 1260. Examples of distributed ledgers 295 may include blockchain ledgers 500 and/or Distributed Acyclic Graph (DAG) ledgers 700. Network device 280 may store a copy of distributed ledger 295. In some examples, the distributed network of other devices (in addition to network device 280) may also store copies of distributed ledger 295, such as media device 205, local device 270, and/or additional devices 297. In some examples, other devices in the distributed network may also verify that the pose of the media device 205 is in the geographic region (block 290), may verify that the token is correct, that the verification block is correct (e.g., the merck (Merkle) root accurately reflects the payload and the hash accurately reflects the previous chunk), or a combination thereof. Generating and verifying that the tile is correct may be followed by appending the tile to the distributed ledger 295 and sending the tile to other devices in the distributed network to append the tile to all copies of the distributed ledger 295.

In some examples, verifying that the pose of the media device 205 is in the geographic area (block 290) may also include receiving recorded audio information recorded by one or more microphones of the media device 205 and comparing the recorded audio information to trusted audio information known to be from the geographic area. In some examples, the trusted audio information may be recorded by one or more microphones of local device 270. In some examples, the trusted audio information may be generated and/or output by one or more speakers of the local device 270. In an illustrative example, the media device 205 may capture an image (an example of sensor data 230) at a concert venue during a concert, and simultaneously record an audio clip of audio at the concert. The network device 280 may receive recorded audio clips and media data 250 including images and/or based on the images from the media device 205. The network device 280 may also receive trusted audio clips from a concert at a concert venue and/or from the local device 270. The trusted audio clip may include audio from the same time period as the recorded audio clip. The trusted audio clip may have been recorded at the concert venue by one or more microphones of the local device 270. The trusted audio clip may have been output at the concert venue by a speaker coupled to the local device 270. To perform verification of the pose of the media device 205 in the geographic area (block 290), the network device 280 may compare the recorded audio clip from the media device 205 with the trusted audio clip from the local device 270. If at least a portion of the recorded audio clips match at least a portion of a trusted audio clip (e.g., the same song is played at a concert in both audio clips), verification that the pose of the media device 205 is in the geographic area (block 290) is successful because the pose of the media device 205 is verified as being in the geographic area. If no portion (or less than a threshold portion) of the recorded audio clip matches at least any portion of the trusted audio clip (e.g., there is no overlapping audio in the audio clip), verification in the geographic area regarding the pose of the media device 205 fails (block 290) because the pose of the media device 205 is not verified as being in the geographic area and/or in some cases the pose of the media device 205 may be verified as not being in the geographic area.

In some aspects, certain devices shown as separate devices in the digital asset tracking system 200 may be combined. In some examples, local device 270 and network device 280 may be combined. For example, some of the communications 272 may include some of the communications 282, and/or some of the communications 282 may include some of the communications 272, 282. In some examples, the media device 205 and the network device 280 may be combined. For example, the communication 282 may be internal to the media device 205. The media device 205 may independently verify that the pose of the media device 205 is in the geographic area (block 290). Media device 205 may generate one or more tokens corresponding to media data 250 alone, may generate one or more blocks in distributed ledger 295 to store tokens therein, and/or may generate distributed ledger 295 itself (block 292). In some examples, the media device 205 and the local device 270 may be combined. For example, the media device 205 may be a kiosk (kiosk) device with a sensor that may have a known location in and/or near a geographic area and/or may be associated with the geographic area (e.g., owned or rented or used by a venue corresponding to the geographic area) and be capable of self-verifying that its location is in the geographic area (block 290).

In some aspects, certain devices illustrated as single devices in the digital asset tracking system 200 may be separated into multiple devices. In some examples, these multiple devices may operate together, for example, by sending data between each other. For example, the media device 205 may include more than one device. In an illustrative example, the media device 205 may include a mobile handheld device (e.g., mobile handheld device 410), a Head Mounted Display (HMD) (e.g., HMD 310), a smart watch, a pair of wireless headphones, a fitness tracker, another wearable apparatus, or a combination thereof.

In some examples, the digital asset tracking system 200 may include a token device (not shown as a separate element). The token device may be an example of a local device 270, a network device 280, a media device 205, one of the additional devices 297, a data store 298, an anchor element 299, a token device 1405, a computing system 1900, or a combination thereof. The token device may be associated with a token (e.g., token 600) associated with a digital asset (e.g., digital asset 605). The token device may include an output device such as a display and/or a speaker. The token device may output the digital asset associated with the token, for example, by displaying visual content (e.g., images, video) of the digital asset using a display of the token device and/or by playing audio content (e.g., sound, music) of the digital asset using a speaker of the token device. In some examples, the token device may be a physical representation of a token with which the token device is associated. Examples of token devices include token device 1405 of fig. 14.

In some examples, digital asset tracking system 200 may include data store 298. Data store 298 may include any type of data structure, including for example data structure 650. In some examples, data store 298 includes customization, personalization, and/or modification of digital assets (e.g., digital asset 605) associated with a token (e.g., token 600). For example, in some examples, the digital asset may be immutable, while customization, personalization, and/or modification of the digital asset may be applied, removed, and/or modified. An example of a data store 298 for customizing, personalizing, and/or modifying digital assets is shown with respect to data store 1370 of FIG. 13.

In some examples, digital asset tracking system 200 may include anchor element 299. In some examples, the anchor element 299 may include objects associated with the token in a real-world environment. For example, detection of the anchor element 299 by the media device 205 using the sensor 210 may cause the media device 205 to output (e.g., display and/or play) a digital asset (e.g., digital asset 605) corresponding to a token (e.g., token 600) corresponding to the anchor element 299 detected by the media device 205. In some examples, the anchor element 299 includes an optical glyph, such as a Quick Response (QR) code, a bar code, an Aztec code, a dot code, a data matrix, a lens code, or a combination thereof. In some examples, the anchor element 299 may include a designated area, and detection by the media device 205 using the sensor 210 that the media device 205 is located in the designated area may cause the media device 205 to output a digital asset corresponding to a token corresponding to the anchor element 299. In some examples, the anchor element 299 may include a specified location, and detection by the media device 205 using the sensor 210 that the media device 205 is located in a threshold range of the specified location may cause the media device 205 to output a digital asset corresponding to a token corresponding to the anchor element 299. In some examples, the token device may be an anchor element 299.

Fig. 3A is a perspective view 300 showing a Head Mounted Display (HMD) 310 used as a media device 205 as part of the digital asset tracking system 200. HMD 310 may be, for example, an Augmented Reality (AR) headset, a Virtual Reality (VR) headset, a Mixed Reality (MR) headset, an augmented reality (XR) headset, or some combination thereof. The HMD 310 includes a first camera 330A and a second camera 330B along a front of the HMD 310. The first camera 330A and the second camera 330B (and/or image sensors thereof) may be examples of the media sensor 220 of the media device 205. In some examples, HMD 310 may have only a single camera with a single image sensor. In some examples, HMD 310 may include one or more additional cameras in addition to first camera 330A and second camera 330B. One or more additional cameras (and/or image sensors thereof) may also be examples of the media sensor 220 of the media device 205. In some examples, in addition to the first camera 330A and the second camera 330B, the HMD 310 may include one or more additional sensors, which may include other types of media sensors 220, the pose sensor 215 of the media device 205, and/or other sensors of the media device 205 described herein.

HMD 310 may include one or more displays 340 visible to user 320 wearing HMD 310 on the head of user 320. In some examples, HMD 310 may include one display 340 and two viewfinders. The two viewfinders may include a left viewfinder for the left eye of the user 320 and a right viewfinder for the right eye of the user 320. The left viewfinder may be oriented so that the left eye of the user 320 sees the left side of the display. The right viewfinder may be oriented so that the left eye of the user 320 sees the right side of the display. In some examples, HMD 310 may include two displays 340, including a left display to display content to the left eye of user 320 and a right display to display content to the right eye of user 320.

HMD 310 may include one or more headphones 335, which may act as speakers and/or headphones that output audio to one or more ears of a user of HMD 310. One headset 335 is shown in fig. 3A and 3B, but it should be understood that HMD 310 may include two headsets, one for each ear (left and right) of the user. In some examples, HMD 310 may also include one or more microphones (not shown). In some examples, audio output by HMD 310 to a user through one or more headphones 335 may include or be based on audio recorded using one or more microphones.

Fig. 3B is a perspective view 350 showing the Head Mounted Display (HMD) of fig. 3A worn by a user 320. The user 320 wears the HMD 310 on the head of the user 320 over the eyes of the user 320. HMD 310 may capture images with first camera 330A and second camera 330B. In some examples, HMD 310 displays one or more output images to the eyes of user 320. The output image may, for example, include sensor data 230, media data 250, or both. The output image may be based on images captured by the first camera 330A and the second camera 330B. The output image may provide a stereoscopic view of the environment, with overlaid information and/or with other modifications in some cases. For example, HMD 310 may display a first display image to the right eye of user 320, the first display image based on the image captured by first camera 330A. HMD 310 may display a second display image to the left eye of user 320, the second display image based on the image captured by second camera 330B. For example, HMD 310 may provide overlay information in a display image overlaid on images captured by first camera 330A and second camera 330B. Headphones 335 of HMD 310 are shown in the ear of user 320. HMD 310 may output audio to user 320 via headphones 335 and/or via another headphone (not shown) of HMD 310 in the other ear (not shown) of user 320.

Fig. 4A is a perspective view 400 showing a front surface of a mobile handset 410 that includes a front facing camera and that may be used as a media device 205 as part of the digital asset tracking system 200. The mobile handset 410 may be an example of the media device 205. The mobile handheld device 410 may be, for example, a cellular telephone, satellite telephone, portable game console, music player, health tracking device, wearable device, wireless communication device, laptop computer, mobile device, any other type of computing device or computing system discussed herein, or a combination thereof.

The front surface 420 of the mobile handset 410 includes a display 440. In some examples, display 440 may display sensor data 230, media data 250, or both. The front surface 420 of the mobile handset 410 includes a first camera 430A and a second camera 430B. The first camera 430A and the second camera 430B (and/or image sensors thereof) may be examples of the media sensor 220 of the media device 205. The first camera 430A and the second camera 430B are shown in a bezel surrounding the display 440 on the front surface 420 of the mobile handset 410. In some examples, the first camera 430A and the second camera 430B may be positioned in a notch or cutout cut from the display 440 on the front surface 420 of the mobile handset 410. In some examples, the first camera 430A and the second camera 430B may be an off-screen camera positioned between the display 440 and the rest of the mobile handset 410 such that light passes through a portion of the display 440 before reaching the first camera 430A and the second camera 430B. The first camera 430A and the second camera 430B of the perspective view 400 are front facing cameras. The first camera 430A and the second camera 430B face in a direction perpendicular to the planar surface of the front surface 420 of the mobile handset 410. The first camera 430A and the second camera 430B may be two of the one or more cameras of the mobile handset 410. The first camera 430A and the second camera 430B may be examples of the media sensor 220 of the media device 205. In some examples, the front surface 420 of the mobile handset 410 may have only a single camera. In some examples, the mobile handset 410 may include one or more additional cameras in addition to the first camera 430A and the second camera 430B. One or more additional cameras (and/or image sensors thereof) may also be examples of the media sensor 220 of the media device 205. In some examples, the mobile handset 410 may include one or more additional sensors in addition to the first camera 430A and the second camera 430B. The one or more additional sensors may also be examples of other types of media sensors 220 and/or gesture sensors 215 of the media device 205. The front surface 420 of the mobile handset 410 also includes a display 440. In some cases, the front surface 420 of the mobile handset 410 includes more than one display 440.

The mobile handset 410 may include one or more speakers 435A and/or other audio output devices (e.g., headphones or earphones or connectors thereto) that may output audio to one or more ears of the user of the mobile handset 410. One speaker 435A is shown in fig. 4A, but it should be understood that the mobile handset 410 may include more than one speaker and/or other audio device. In some examples, the mobile handset 410 may also include one or more microphones (not depicted). In some examples, the audio output to the user by the mobile handset 410 through the one or more speakers 435A and/or other audio output devices may include or be based on audio recorded using one or more microphones.

Fig. 4B is a perspective view 450 showing a rear surface 460 of a mobile handset that includes a read-facing camera and that can be used as a media device 205 as part of the digital asset tracking system 200. The mobile handset 410 includes a third camera 430C and a fourth camera 430D on a back surface 460 of the mobile handset 410. The third camera 430C and the fourth camera 430D of the perspective view 450 are rear facing. The third camera 430C and the fourth camera 430D (and/or image sensors thereof) may be examples of the media sensor 220 of the media device 205. The third camera 430C and the fourth camera 430D face in a direction perpendicular to the planar surface of the rear surface 460 of the mobile handset 410. While the back surface 460 of the mobile handset 410 does not have the display 440 as shown in the perspective view 450, in some examples the back surface 460 of the mobile handset 410 may include one or more back displays. In some examples, one or more rear displays may display sensor data 230, media data 250, or both. If the back surface 460 of the mobile handset 410 includes one or more back displays, any positioning arrangement of the third camera 430C and the fourth camera 430D relative to the one or more back displays may be used, as discussed with respect to the display 440 of the first camera 430A and the second camera 430B relative to the front surface 420 of the mobile handset 410.

The third camera 430C and the fourth camera 430D may be two of the one or more cameras of the mobile handset 410. In some examples, the back surface 460 of the mobile handset 410 may have only a single camera. In some examples, the mobile handset 410 may include one or more additional cameras in addition to the first camera 430A, the second camera 430B, the third camera 430C, and the fourth camera 430D. One or more additional cameras (and/or image sensors thereof) may also be examples of the media sensor 220 of the media device 205. In some examples, the mobile handset 410 may include one or more additional sensors in addition to the first camera 430A, the second camera 430B, the third camera 430C, and the fourth camera 430D. The one or more additional sensors may also be examples of other types of media sensors 220 and/or gesture sensors 215 of the media device 205.

The mobile handset 410 may include one or more speakers 435B and/or other audio output devices (e.g., headphones or earphones or connectors thereto) that may output audio to one or more ears of the user of the mobile handset 410. One speaker 435B is shown in fig. 4B, but it should be understood that the mobile handset 410 may include more than one speaker and/or other audio device. In some examples, the mobile handset 410 may also include one or more microphones (not shown). In some examples, the audio output to the user by the mobile handset 410 through the one or more speakers 435B and/or other audio output devices may include or be based on audio recorded using one or more microphones.

Fig. 5 is a block diagram illustrating three consecutive blocks of a blockchain ledger 500 that may be used to track digital assets associated with locations in a geographic area in accordance with an aspect of the present disclosure. Three blocks of blockchain ledger 500 are shown in FIG. 5, including block A505, block B535, and block C565.

Each chunk includes a list of chunk headers 510/540/570 and one or more payloads 530/560/590. In some examples, the block header 510/540/570 includes a hash 515/545/575 of the previous block and/or a hash 510/540/570 of the block header of the previous block. For example, header 570 of block C565 includes a hash 575 of header 540 of block B535. The header 540 of block B535 also includes a hash 545 of the header 510 of block a 505. Header 510 of block a 505 also includes hash 515 of a header (not shown) of a previous block (not shown) preceding block a 505 in blockchain ledger 500. The hashing of the header that includes the previous block protects blockchain ledger 500 by preventing modification of any block of blockchain ledger 500 after a block has been entered into blockchain ledger 500 because any change to a particular block will result in the hashing 515/545/575 of the blockheader in the next block being incorrect. Furthermore, modifications to the hash of the block header in the next block will make the hash 515/545/575 of the header of the next block in the blocks following the next block incorrect, and so on. The verification device may verify that a block has not been modified by calculating a hash of the block and/or a hash of the block header and then comparing the calculated hash with the stored hashes 515/545/575 stored in the next block. In some distributed ledgers, tile headers 510/540/570 may include hashes of a plurality of previous tiles and/or hashes of tile headers of a plurality of previous tiles, as in Distributed Acyclic Graph (DAG) ledger 700 of fig. 7.

The block header 510/540/570 of each block may include a merck root 520/550/580. The merck root 520/550/580 may be generated based on a hash of each of the token, transaction, smart contract, and/or other elements identified in the payload 530/560/590 for that chunk. Any attempt to modify the payload after a chunk has been entered will change the merck root. The verification device may verify that the payload 530/560/590 has not been modified by computing the merck root and then comparing the computed merck root to the stored merck root 520/550/580 stored in the chunk header 510/540/570. Changes to the payload 530/560/590 and/or to the merck root 520/550/580 will also change the hash for the chunk and/or for the chunk header for which the value is stored in the next chunk as hash 515/545/575. Each payload of each chunk may include one or more tokens, one or more transactions, one or more smart contracts, other content, or a combination thereof.

The blockheader 510/540/570 of each block may also include various elements of metadata, such as a version number for the blockchain ledger platform, a version number for the block itself, a timestamp for validating each payload, a timestamp for generating the block, a timestamp for entering the block into the blockchain ledger 500, a timestamp for requesting the block to be generated, a difficulty target value (e.g., adjusting difficulty of mining), one or more randomized random values, a counter that identifies how many random numbers have been tried, a title of the blockchain ledger 500, an identifier of what is being tracked by the blockchain ledger 500 (e.g., a history of digital assets 605 associated with device locations in a geographic area), or a combination thereof. Each individual element added may also be used as information that can be verified by a verification device to identify whether the chunk and its payload are accurate and authorized. One or more randomized random values can be used to further complicate hashing, thereby improving security.

Each block 505/535/565 of blockchain ledger 500 also includes a payload 530/560/590. The payload 530/560/590 for each block 505/535/565 may include one or more tokens, one or more transactions, one or more smart contracts, one or more other elements, metadata related to any previously listed elements, or a combination thereof. The token may be, for example, an irreplaceable token. Token 600 may be an example of a token stored in payload 530/560/590 for block 505/535/565. As discussed with respect to token 600, certain portions of token 600 are stored within payloads 530/560/590 of blockchain ledger 500, and thus are stored "on-chain," as discussed with respect to token 600, certain portions of token 600 include on-chain pointers to data external to blockchain ledger 500, where such data is stored "off-chain. The payloads 530/560/590 of the blockchain ledger 500 may store hashes of out-of-chain data such that the verification device may calculate hashes of out-of-chain data and compare the calculated hashes to stored hashes stored on the chain to verify that the out-of-chain data is accurate. In some examples, payloads 530/560/590 include one or more smart contracts. The blockmay include code for the smart contract stored within the payload 530/560/590 of the blockchain ledger 500, thereby storing the code on the chain. If the payload 530/560/590 includes a smart contract, the chunk may include a hash of the code of the smart contract and/or a pointer to an off-chain data structure storing the code of the smart contract, thereby storing the code off-chain. In some examples, some of the code of the smart contract may be stored on the chain and some of the code of the smart contract may be stored off the chain. In some examples, the smart contract may be used to create, modify, transfer, or otherwise manage tokens. In some examples, payloads 530/560/590 include transactions. In some examples, the transaction may include a transfer of the token from one account to another account. In some examples, the transaction may include a change to certain properties of the token or associated digital asset, such as a change to ownership, properties, authorship, use license, lease, or a combination thereof.

Although fig. 5 only shows three blocks 505/535/565 of blockchain ledger 500, it should be understood that any of the blockchain ledgers or distributed ledgers discussed herein may be longer or shorter and may have more than three blocks or less than three blocks.

In one illustrative example, a first computing device may store a blockchain ledger including a plurality of blocks. Each of the plurality of computing devices (e.g., in a distributed architecture) also stores a copy of the blockchain ledger. The first computing device may receive a message identifying an expected payload element (e.g., a token and/or a transaction and/or a smart contract). For example, the expected payload element may be a token related to a digital asset (e.g., media data 250) associated with a location as described herein. The first computing device may verify that the expected payload element is valid. In some blockchain ledger 500 implementations, the first computing device may verify that sufficient funds are allocated to pay for execution of the intended payload element, e.g., in the form of a gas on an ethernet blockchain ledger. For transactions such as token transfer, the first computing device may verify whether the transferor has a sufficient number of assets (e.g., whether the transferor possesses tokens to be transferred) to conduct the transaction. For a smart contract, a first computing device may verify that the smart contract refers to a valid account that includes a sufficient number of assets (e.g., tokens) to execute the smart contract (e.g., transfer tokens), that code to verify the smart contract may be executed (e.g., not include grammatical errors or other errors), that all parties involved in the smart contract have submitted an agreement to terms of the smart contract, or a combination thereof. For a token, the first computing device may verify that the token refers to a valid digital asset, such as a valid type of digital asset having a URI or other pointer that effectively points to the digital asset.

The first computing device may generate a hash of the nearest block or block header of blockchain ledger 500. The first computing device may generate a new block header for the new block. The new blockheader may include at least a hash of the nearest blockor blockheader of blockchain ledger 500. The first computing device may generate a new chunk including a new chunk header and a payload having one or more payload elements. The one or more payload elements include at least the expected payload elements discussed above (e.g., tokens, smart contracts, transactions). The first computing device may generate a merck root based on the payload element and include the merck root in the new chunk header. The first computing device may generate metadata and random values based on the payload elements and include the metadata and random values in a new chunk header. The first computing device may append the new chunk to a plurality of chunks of blockchain ledger 500 in response to validating the expected payload element. The first computing device may send the new chunk to a plurality of computing devices that each store blockchain ledger 500 in response to verifying the expected payload element. Each of the plurality of computing devices also appends a new block to its corresponding copy of blockchain ledger 500.

In another illustrative example, a first computing device may store blockchain ledger 500 that includes a plurality of blocks. Each of the plurality of computing devices (e.g., in a distributed architecture) also stores a copy of blockchain ledger 500. The first computing device may receive UI input identifying an expected payload element (e.g., a transaction and/or a smart contract). The first computing device may generate a message identifying an expected payload element. The first computing device may retrieve a private key associated with an account corresponding to the first computing device. The first computing device may modify the message by encrypting at least a portion of the message with the private key. The first computing device may send the message to a plurality of computing devices other than the first computing device. A second computing device of the plurality of computing devices verifies that the expected payload element is valid, e.g., as described in the previous paragraph. The first computing device receives the new block from the second computing device. The new chunk identifies and/or includes (e.g., in its payload) the expected payload element. The first computing device appends the new block to a plurality of blocks of blockchain ledger 500 at the first computing device.

Fig. 6 is a block diagram illustrating an example token 600, which example token 600 may be non-replaceable and may represent digital assets 605 associated with locations in a geographic area as tracked in a distributed ledger. In some examples, token 600 is a non-replaceable token (NFT). In some examples, token 600 is an ERC721 token, an ERC1155 token, an ERC-20 token, or a combination thereof. In some examples, token 600 is tracked in blockchain ledger 500. In some examples, token 600 is tracked in ethernet-based blockchain ledger 500. In some examples, token 600 is tracked in Directed Acyclic Graph (DAG) ledger 700.

The digital asset 605 represented by the token 600 may be an example of the media data 250 from the media device 205 of the digital asset tracking system 200 of fig. 2. As discussed with respect to the digital asset tracking system 200 of fig. 2, the media data 250, and thus the digital asset 605, may include one or more images, videos, audio clips, 3D point clouds, 3D models, sensor data 230, gesture data 225, metadata associated with the sensor data 230, metadata associated with the gesture data 225, virtual content generated by the virtual content generator 240, images or videos with virtual content incorporated via the image synthesizer 245, maps generated by the map generator 247, or a combination thereof. The 3D model may include, for example, a 3D reconstruction based on a 3D point cloud, such as a 3D reconstruction of a portion of a forest, a portion of a celebrity's home, a historic location, a national park, and the like.

One or more token intelligence contracts 645 may be associated with token 600. For example, one or more token intelligence contracts 645 manage creation (or "casting") of tokens 600. One or more token intelligence contracts 645 may pay a mineworker device that creates ("casts") tokens 600 or batches of tokens to calculate the time and resources for casting tokens 600. The one or more token intelligence contracts 645 may include conditions that must be met before the token 600 can be successfully created (cast). For example, one such condition may require that verification in a geographic area must be successfully performed by one or more verification devices (e.g., at least a threshold number of verification devices, such as the quorum in fig. 15A-15B) with respect to the time of capture of sensor data 230 (e.g., block 290 of fig. 2) corresponding to media data 250 of digital asset 605 and/or during capture of sensor data 230 in order to allow creation (casting) of token 600. One or more token intelligence contracts 645 may control how ownership of token 600 is decided and/or transferred. For example, one or more token intelligence contracts 645 may indicate an initial owner of token 600 and/or may identify conditions for automatic transfer of ownership, such as an offer that meets or exceeds an owner variable threshold amount. One or more token intelligence contracts 645 may indicate conditions under which token 600 may rent or license for temporary use or possession by a licensed user, such as an offer that meets or exceeds an owner variable threshold amount. One or more token intelligence contracts 645 may control conditions under which token 600 may be burned (e.g., irreversibly destroyed and/or not listed). Elements identified as part of token 600 in fig. 6 (including token identifier 610, token number 615, token ownership 620, on-chain immutable metadata 625, on-chain variable metadata 630, on-chain pointers to off-chain media 635, on-chain pointers to off-chain metadata 640) may be stored as part of token 600, may be part of token intelligence contract 645, or both. In some examples, the code of token intelligence contract 645 is stored at least in part on the chain. In some examples, the code of token intelligence contract 645 is stored at least partially off-chain at an off-chain location, such as data structure 650, where the off-chain location is identified by an on-chain pointer to the off-chain location.

Token 600 includes a token identifier 610, and token identifier 610 may be referred to as a token ID. Token identifier 610 may be a unique identifier for token 600 and/or for digital asset 605. Token identifier 610 may be used to distinguish a particular instance of digital asset 605 to which token 600 corresponds from any other instance of digital asset 605. In some examples, token identifiers may be created by a computing system that creates (or "casts") tokens 600 by sequentially incrementing compared to token identifiers of previously created tokens to ensure that each token identifier is unique.

Token 600 may include a token number 615. The token quantity 615 may identify the quantity of tokens 600 that have been cast or set to be cast. In some examples, the number of tokens 615 is 1, in which case there is a single token 600 for a given digital asset 605. In some examples, the number of tokens 615 is greater than 1. For example, if the number of tokens 615 is 5, there are actually 5 copies of the token 600, the token 600 represents the unique digital asset 605 that may be owned and/or transferred alone. In some examples, those 5 copies may each correspond to a separate token. In some examples, all 5 copies may be represented by a single token. In some examples, those 5 copies may be replaceable with each other or indistinguishable from each other. However, those 5 copies are still irreplaceable, unique, distinct, and/or distinguishable relative to any other instance or version or variant of the digital asset 605. In some examples, those 5 copies are still distinguishable from each other, e.g., where the corresponding token 600 for each copy includes an identifier (on-chain or off-chain) indicating which of the 5 copies is (e.g., 1 st, 2 nd, 3 rd, 4 th, or 5 th). The token number 615 may control how rare the token 600 is and by extending the digital asset 605. If the token number 615 is 1, the token 600 and corresponding digital asset 605 are unique. If the number of tokens 615 is greater than one but less than the rareness threshold, then the token 600 and corresponding digital asset 605 are rare. If the number of tokens 615 is greater than once but greater than the rareness threshold, then the token 600 and corresponding digital asset 605 are common. In some examples, there may be any number of rareness ranges, such as, for example, biographical, very rare, slightly rare, unusual, and other kinds of rareness, in addition to or instead of unique, rare, and common. In some cases, the token quantity 615 may be determined as part of the casting process and/or identified in one of the token intelligence contracts 645 that manages the casting process.

Token 600 may identify token ownership 620, token ownership 620 may identify who owns token 600, and by extension, the corresponding digital asset 605. In some examples, token ownership 620 may be initially assigned to an account associated with the creator of digital asset 605, such as a user associated with media device 205 capturing, obtaining, or generating media data 250 of digital asset 605. The user associated with the media device 205 may be a user in possession of the media device 205. The user associated with the media device 205 may be a user using the media device 205 when the media device 205 captures sensor data 230 and/or gesture data 225 associated with the digital asset 605, when the media device 205 captures, obtains, or generates media data 250 of the digital asset 605, or a combination thereof. In some examples, token ownership 620 may be initially assigned to an account associated with a person depicted or represented in media data 250 of digital asset 605, as shown in user Bob 945 of fig. 9A-9B. Token intelligence contract 645 may control rules for transferring token ownership 620. Token ownership 620 may be transferred as a transaction recorded as payload elements in the payload of a blockchain ledger or other block of a distributed ledger.

Token 600 may include on-chain immutable metadata 625. The on-chain immutable metadata 625 may include, for example, a description of the token 600, a description of the digital asset 605 represented by the token 600, some immutable attribute or characteristic of the digital asset 605 and/or the token 600, or some combination thereof. The on-chain immutable metadata 625 may use the attributes of the distributed ledger and/or token intelligence contract 645 to ensure that the on-chain immutable metadata 625 remains unchanged. In some examples, the on-chain immutable metadata 625 may identify the media device 205 that captured, obtained, or generated the media data 250 of the digital asset 605. In some examples, the on-chain immutable metadata 625 can identify categories of media (e.g., images, videos, audio clips, 3D point clouds, 3D models, maps, etc.) that the digital asset 605 includes. In some examples, the on-chain immutable metadata 625 may identify a location or pose of the media device 205 at the same time and/or during capturing of the sensor data 230 associated with the digital asset 605. In some examples, the on-chain immutable metadata 625 can identify a geographic region.

Token 600 may include on-chain variable metadata 630. The on-chain variable metadata 630 may include, for example, a description of the token 600, a description of the digital asset 605 represented by the token 600, some non-variable attribute or characteristic of the digital asset 605 and/or the token 600, or some combination thereof. The on-chain variable metadata 630 may be variable (changeable) or changeable (changeable). In some examples, changes to the on-chain variable metadata 630 may be recorded as transactions recorded as payload elements in payloads of chunks of a blockchain ledger or other distributed ledger. In some examples, the on-chain immutable metadata 625 may identify how many times the digital asset 605 has been viewed, played, accessed, or used in a specified manner.

Token 600 may include an on-chain pointer to off-chain media 635. The out-of-chain media may include digital asset 605 and/or one or more representations of digital asset 605. For example, the out-of-chain media may include one or more images, 3D point clouds, 3D models, video clips, audio clips, maps, or combinations thereof. These types of media may require a large amount of storage space to store and thus may be expensive to store on the chain in terms of execution costs (such as gas on an ethernet blockchain ledger). Thus, it may be more efficient to store the off-chain media in one or more off-chain locations (such as data structure 650). The on-chain pointer may include a Uniform Resource Identifier (URI), such as a Uniform Resource Locator (URL), that points to one or more network locations in one or more off-chain locations. In some examples, hashes of the off-chain media may be stored such that the verification device may calculate hashes of the off-chain media and compare the calculated hashes to stored hashes stored on the chain to verify that the off-chain media is accurate. In some examples, the out-of-chain media may be immutable. In some examples, the out-of-chain media may be variable. In some examples, the pointer may be immutable. In some examples, the pointer may be variable.

Token 600 may include an on-chain pointer to out-of-chain metadata 640. The out-of-chain metadata 630 may include, for example, a description of the token 600, a description of the digital asset 605 represented by the token 600, some immutable attribute or characteristic of the digital asset 605 and/or the token 600, or some combination thereof. Some digital assets 605 and/or tokens 600 may require a large amount of metadata, which may require a large amount of storage space to store, and thus may be expensive to store on-chain in terms of execution costs (such as gas on an ethernet blockchain ledger). Thus, it may be more efficient to store the out-of-chain metadata in one or more out-of-chain locations (such as data structure 650). The on-chain pointer may include a Uniform Resource Identifier (URI), such as a Uniform Resource Locator (URL), that points to one or more network locations in one or more off-chain locations. In some examples, hashes of out-of-chain metadata may be stored such that the verification device may calculate hashes of out-of-chain metadata and compare the calculated hashes to stored hashes stored on the chain to verify that the out-of-chain metadata is accurate. In some examples, the out-of-chain metadata may be immutable. In some examples, the out-of-chain metadata may be variable. In some examples, the pointer may be immutable. In some examples, the pointer may be variable.

Fig. 7 is a block diagram illustrating a Directed Acyclic Graph (DAG) ledger 700 configured to track digital assets associated with locations in a geographic area according to an aspect of the disclosure. Although FIG. 5 discusses the use of blockchain ledger 500, it should be understood that a non-linear ledger structure, such as the Directed Acyclic Graph (DAG) ledger structure of FIG. 7, may be used instead of or in addition to blockchain ledger 500 discussed herein. The term "distributed ledger" as used herein should be understood to refer to at least one of blockchain ledger 500 (as in fig. 5), DAG ledger 700 (as in fig. 7), or a combination thereof. In the DAG ledger, each chunk header includes hashes of chunks, of a predetermined number of other "parent" chunks in the DAG ledger that are selected randomly or in some other non-linear manner, rather than hashes of a single previous chunk in the blockchain. Where each chunk header includes multiple hashes corresponding to different parent chunks or their headers, these hashes may be combined together (e.g., using merck root).

For example, in the DAG ledger of fig. 7, the predetermined number is two at least after the first two blocks are generated. In the network DAG ledger of fig. 7, the parent block is indicated using an arrow. Block 710 includes hashes of the block headers of parent blocks 720 and 750. Block 720 includes hashes of the block headers of parent blocks 740 and 760. Block 730 includes a hash of the block header of parent blocks 720 and 760. Block 740 includes a hash of the block header of parent blocks 710 and 730. Block 750 includes a hash of the block headers of parent blocks 710 and 720. Block 760 includes a hash of the block header of parent blocks 710 and 750. The resulting structure is a Directed Acyclic Graph (DAG) of blocks, where each vertex block includes a hash of its parent vertex block, rather than a linear stream of blocks in the blockchain. DAG ledgers may sometimes be referred to as "networks", "entanglement", or "hash maps".

In some examples, the number of parent blocks for a given block in the DAG ledger is not predetermined, but there may be a predetermined minimum number of parent blocks, such as a two parent block minimum or a parent block minimum, meaning that each block has at least a predetermined minimum number of parent blocks. In some cases, each chunk in the DAG ledger may identify only a single payload element (e.g., token 600) instead of multiple payload elements, and thus may discard the merck root 520/350/380 of the payload element and/or replace it with a hash of the single payload element. In other implementations, each chunk may identify a plurality of payload elements associated with a predetermined period of time, and/or may include the merck root 520/350/380 of the payload elements. In some examples, DAG ledger 700 may provide benefits over blockchain ledger 500 by providing parallelized verification, which may provide higher throughput.

Fig. 8A is a perspective view 800 showing a user 805 capturing a digital asset 840 (image) of a portrait in a museum using a media device 810. The media device 810 captures the digital asset 840 using the image sensor 815 of the media device 810, while a portrait (Mona Lisa) in a museum (Lu vre) museum) is in the field of view (FOV) 825 of the image sensor 815 of the media device 810. Media device 810 may be an example of media device 205. The image sensor 815 of the media device 810 may be an example of the media sensor 220 of the media device 205. Media device 810 may generate positioning data using its positioning sensor 820 at the same time and/or during the capture of an image corresponding to digital asset 840 by image sensor 815. The positioning sensor 820 may be an example of the gesture sensor 215. The positioning data may be an example of gesture data 225. The media device 810 may communicate with a local device 830 in or near a geographic area (e.g., in a museum). Media device 810 may send to local device 830 and/or receive one or more communications 835 from local device 830. Local device 830 may be an example of local device 270. Communication 835 may be an example of communication 272. In some examples, local device 830 may be a beacon.

Although the media device 810 of fig. 8A is shown as a mobile handset 410, in some examples, the media device 810 may be a media device 810 having a geographic area and/or geographically locked to a geographic area. For example, media device 810 may be a kiosk device that is geographically locked to a rufiguy museum that user 805 may access and capture digital asset 840 to use. In this case, such a media device 810 may self-verify that it is located in a geographic area, for example, because the media device 810 is geographically locked to the geographic area.

Fig. 8B is a conceptual diagram 850 illustrating information 855 about a token 860 associated with the digital asset 840 of fig. 8A. Token 860 may be an example of token 600. The information 855 may be partially identified within the token 860 itself (e.g., as token identifier 610, on-chain immutable metadata 625, on-chain changeable metadata 630, off-chain media 635, off-chain metadata 640, rules of one or more smart contracts 645, or a combination thereof). Information 855 about token 860 includes a message indicated as "see Mona Lisa-! Title 865 of "in the specification. Information 855 about token 860 includes a copy of digital asset 840 (e.g., retrieved from token 860 using an on-chain pointer to off-chain media 635). Information 855 about token 860 identifies digital asset type 870 of digital asset 840 as an image. Information 855 about token 860 includes metadata 875 associated with the capture of digital asset 840, metadata 875 being a paperclip icon (indicating that metadata 875 is viewable when the gyrator icon is clicked).

Information 855 about token 860 includes history 880. In some examples, each element of history 880 is identified as a payload element in a block of the distributed ledger storing token 860. History 880 indicates that at 2021, 5 months, 24 days, 2:03:36 afternoon, digital asset 840 was captured by user 805 using media device 810, and that location sensor 920 of media device 810 indicated that the pose of media device 810 was north-facing in a luffland museum, while media device 810 and local device 830 at the luffland museum were within communication range (based on communication 835). History 880 indicates that at day 26 of 5 months 2021, 6:40:01 am, server 885 casts token 860 based on digital asset 840 having ownership of user 805 settings when verifying that media device 810 is in a rufiguy museum during capture (e.g., via object identification and/or by verifying that positioning sensor 820 data matches a known geographic area of the rufiguy museum and/or by verifying communication in communication 835). A server 885 may be an example of a network device 280. History 880 indicates that at 28 days 5 of 2021, at 1:22:54 pm, ownership of token 860 is transferred from user 805 to user 890 after user 890 purchased token 860 from user 805.

In some examples, a venue may allow venue attendees to capture a limited number of digital assets for which a network device 280 associated with the venue may cast token 600. For example, a venue attendee may purchase a token "pass" from the venue indicating that the network device 280 associated with the venue will generate one or more tokens for a certain number of images (or other digital assets) captured by the user within the venue (e.g., tokens to be generated by 5 of the images of the user in the venue). Generating tokens for such images may use the reputation of the token caster (venue and network device 280 associated with the venue) to help prove that the user is indeed at the venue at a given date and time, e.g., to allow the user to prove that they are at a particular concert, sporting event, movie show, etc. Generating tokens for such images may use the reputation of the token caster (venue and network device 280 associated with the venue) to help prove that the user is at a particular portion of the venue (e.g., a particular seat). In some cases, verification of the media device 205 in a geographic area (e.g., in a venue) while and/or during capturing of the sensor data 230 associated with the media data 250 of the digital asset may include cross-referencing the identity of the user with tickets to the venue and/or to a particular portion of the venue (e.g., a particular seat or seat portion). In some examples, tokens for images (or other media) captured from certain seats or locations within a venue (e.g., a front seat) may be more valuable than tokens for images (or other media) captured from other seats or locations within the venue (e.g., a remote seat or a "nose bleed" seat). In some examples, the geographic area may be a particular portion of a venue, such as a particular seat or seat portion.

Fig. 9A is a perspective view 900 showing a user 905 using a media device 910 to capture digital assets 940 (images) of a number of people including an individual identified as Bob 945. The media device 910 captures the digital asset 940 using the image sensor 915 of the media device 910, while a person including Bob 945 is in the field of view (FOV) 925 of the image sensor 915 of the media device 910. Media device 910 may be an example of media device 205. The image sensor 915 of the media device 910 can be an example of the media sensor 220 of the media device 205. The media device 910 may generate positioning data using its positioning sensor 920 at the same time and/or during the capturing of an image corresponding to the digital asset 940 by the image sensor 915. The positioning sensor 920 may be an example of the gesture sensor 215. The positioning data may be an example of gesture data 225. The media device 910 may communicate with a local device 930 that is in or near a geographic area. The local device 930 may be, for example, a Bob device. In the context of fig. 9A-9B, the geographic area may be a vicinity of a person depicted in digital asset 940 (including Bob 945). Verification of the media device 910 in a geographic area may help verify that the person depicted in the digital asset 940 is actually Bob 845 and other depicted persons. The media device 910 can send to the local device 930 and/or receive from the local device 930 one or more communications 935. Local device 930 may be an example of local device 270. Communication 935 may be an example of communication 272.

Fig. 9B is a conceptual diagram 950 illustrating information 955 about a token 960 associated with the digital asset 940 of fig. 9A. Token 960 may be an example of token 600. Information 955 may be partially identified within the token 960 itself (e.g., as token identifier 610, on-chain immutable metadata 625, on-chain changeable metadata 630, off-chain media 635, off-chain metadata 640, rules of one or more smart contracts 645, or a combination thereof). Information 955 about token 960 includes a title 965, indicated as "partner here-! ". Information 955 about the token 960 includes a copy of the digital asset 940 (e.g., retrieved from the token 960 using an on-chain pointer to the off-chain media 635). Information 955 about token 960 identifies digital asset type 970 of digital asset 940 as an image. Information 955 about token 960 includes metadata 975 associated with the capture of digital asset 940. Metadata 975 is shown as a paperclip icon (indicating that metadata 975 is viewable when the paperclip icon is clicked).

Information 955 about token 960 includes history 980. In some examples, each element of history 980 is identified as a payload element in a block of the distributed ledger storing token 960. History 980 indicates that at 24 months 5 of 2021, at 2:03:36 pm, digital asset 940 was captured by user 905 using media device 910, and location sensor 920 of media device 910 indicates that the pose of media device 910 is in proximity to Bob's device 930, and that media device 910 and Bob's device 930 are within communication range (communication 935). History 980 indicates that at day 26 of 5 months 2021, 6:40:01 a.m., server 985 casts token 960 based on digital asset 940 having ownership set to Bob 945 when verifying Bob 945 is depicted in digital asset 940 (e.g., via facial recognition and/or verifying location sensor 920 data in the vicinity of Bob's device 930, and/or by verifying communication 935). A server 985 may be an example of network device 280. History 980 indicates that at 28 months 5 of 2021, at 1:22:54 pm, after user 990 purchased token 960 from Bob 945, ownership of token 960 was transferred from Bob 945 to user 990.

In some examples, one or more tokens 960 may be cast by a server 985 corresponding to a digital asset 940. For example, the server 985 may cast one or more tokens 960 such that the user 905 capturing the digital asset 940 may possess one of the tokens 960 and such that everyone identified in the digital asset 940 (including Bob 945 as identified in information 955) may possess one of the tokens 960.

Fig. 10A is a perspective view 1000 illustrating a user 1005 using a media device 1010 to generate a digital asset 1040 (image) comprising a virtual object 1045 composited into a real scene. The media device 1010 captures the digital asset 1040 using the image sensor 1015 of the media device 1010 while a virtual object 1045 (virtual dog) in a geographic area (park) is in the field of view (FOV) 1025 of the image sensor 1015 of the media device 1010. In some examples, the virtual object 1045 may be associated with a geographic area, such as part of a video game, in which different virtual objects appear in different geographic areas, such that the user 1005 may walk to different geographic areas to "capture", encounter, or otherwise encounter different virtual objects 1045 (e.g., different virtual pets). Media device 1010 may be an example of media device 205. The image sensor 1015 of the media device 1010 may be an example of the media sensor 220 of the media device 205. The media device 1010 may use the positioning sensor 1020 to generate positioning data at the same time and/or during the capturing of an image of the park corresponding to the digital asset 1040 by the image sensor 1015. Virtual object 1045 may be generated (e.g., via virtual content generator 240) added to an image of the park (e.g., via image compositor 245). The positioning sensor 1020 may be an example of the gesture sensor 215. The positioning data may be an example of gesture data 225. The media device 1010 may communicate with the local device 1030 in or near a geographic area (e.g., in a museum). The media device 1010 may send and/or receive one or more communications 1035 from the local device 1030. Local device 1030 may be an example of local device 270. Communication 1035 may be an example of communication 272.

Fig. 10B is a conceptual diagram 1050 illustrating information 1055 about a token 1060 associated with the digital asset 1040 of fig. 10A. Token 1060 may be an example of token 600. The information 1055 may be partially identified within the token 1060 itself (e.g., as token identifier 610, on-chain immutable metadata 625, on-chain changeable metadata 630, off-chain media 635, off-chain metadata 640, rules of one or more smart contracts 645, or a combination thereof). Information 1055 about token 1060 includes a title 1065, title 1065 being indicated as "just encountered My virtual pets, spark-! ". Information 1055 about the token 1060 includes a copy of the digital asset 1040 (e.g., retrieved using an on-chain pointer to the off-chain media 635 of the token 1060). Information 1055 about the token 1060 identifies the digital asset type 1070 of the digital asset 1040 as an image. The information 1055 about the token 1060 includes metadata 1075 associated with the capture of the digital asset 1040, the metadata 1075 being a paperclip icon (indicating that the metadata 1075 is viewable when the paperclip icon is clicked).

Information 1055 about token 1060 includes history 1080. In some examples, each element of history 1080 is identified as a payload element in a tile of the distributed ledger of storage token 1060. History 1080 indicates that at 24 months 5 of 2021, at 2:03:36 pm, digital asset 1040 was captured and/or generated by user 1005 using media device 1010 while location sensor 1020 of media device 1010 indicated that the pose of media device 1010 was in the park facing north, and while media device 1010 and local device 1030 at the park were in communication range (communication 1035). As shown, the park includes real objects 1047 (e.g., trees and/or other objects). History 1080 indicates that, at day 26 of 5 months 2021, 6:40:01 a.m., server 1085 casts token 1060 based on digital asset 1040 when verifying that media device 1010 is in a geographic region where virtual object 1045 appears during capture (e.g., by verifying that positioning sensor 1020 data matches the geographic region and/or by verifying communication 1035), wherein ownership is set to user 1005. Server 1085 may be an example of network device 280. History 1080 indicates that at 28 months 5 of 2021, at 1:22:54 pm, ownership of token 1060 is transferred from user 1005 to user 1090 after user 1090 purchased token 1060 from user 1005.

In some examples, the generation of the virtual object 1045 and/or the token 1060 associated therewith may be part of a video game and may be driven by a scarcity function that accounts for factors such as the amount of users (number of users of the video game), the location of the users (geographic distribution of users of the video game), the market transaction history (recent transfers of the virtual object 1045 and/or the token 1060 associated therewith (indicating interest in the basis of the user)), the user engagement (hours of each user in the video game), or a combination thereof.

FIG. 11A is a perspective view 1100 illustrating a user 1105 using a media device 1110 to generate a digital asset 1140 (map) of a hiking path. Media device 1110 captures sensor data using its location sensor 1120. The sensor data may be examples of gesture data 225 and/or sensor data 230. The positioning sensor 1120 may be an example of the gesture sensor 215 and/or the media sensor 220. The media device 1110 can generate digital assets 1140 (maps) of the hiking path using the map generator 247. At least some of the sensor data may be captured by the location sensor 1120 while the media device 1110 is in a geographic area (e.g., a park where hiking is located).

The media device 1110 may communicate with the local device 1130 in or near a geographic area (e.g., in a museum). Media device 1110 can send and/or receive one or more communications 1135 to and/or from local device 1130. The local device 1130 may be an example of the local device 270. Communication 1135 may be an example of communication 272.

Fig. 11B is a conceptual diagram 1150 illustrating information 1155 about a token 1160 associated with the digital asset 1140 of fig. 11A. Token 1160 may be an example of token 600. Information 1155 may be partially identified within the token 1160 itself (e.g., as token identifier 610, on-chain immutable metadata 625, on-chain changeable metadata 630, off-chain media 635, off-chain metadata 640, rules of one or more smart contracts 645, or a combination thereof). Information 1155 about token 1160 includes a title 1165, title 1165 being indicated as "see Mona Lisa-! ". Information 1155 about token 1160 includes a copy of digital asset 1140 (e.g., retrieved using an on-chain pointer to out-of-chain media 635 of token 1160). Information 1155 regarding token 1160 identifies digital asset type 1170 of digital asset 1140 as an image. Information 1155 about token 1160 includes metadata 1175 associated with the capture of digital asset 1140, metadata 1175 being a paperclip icon (indicating that metadata 1175 is viewable when paperclip icon is clicked).

Information 1155 about token 1160 includes history 1180. In some examples, each element of history 1180 is identified as a payload element in a block of the distributed ledger of storage token 1160. History 1180 indicates that, at 24 months 5 of 2021, at 2:03:36 pm, digital asset 1140 was captured/generated by user 1105 using media device 1110 while location sensor 920 of media device 1110 indicated that the pose of media device 1110 was in the park facing west, and while media device 1110 and local device 1130 (e.g., beacons) at the park were in communication range (communication 1135). History 1180 indicates that, at 26 months 5 of 2021, 6:40:01 a.m., server 1185 casts token 1160 based on digital asset 1140 when verifying that media device 1110 is at a park during capture (e.g., by verifying that location sensor 1120 data matches the park and/or by verifying communication 1135), wherein ownership is set to 1105. The server 1185 may be an example of the network device 280. History 1180 indicates that at 28 days 5 of 2021, at 1:22:54 pm, ownership of token 1160 has been transferred from user 1105 to user 1190 after user 1190 purchased token 1160 from user 1105.

In some examples, additional information may need to be validated (e.g., by one or more smart contracts 645) before the network device 280 can cast a token corresponding to a particular digital asset (e.g., by the network device 280). For example, in addition to verifying that the media device is in a geographic location, additional information that may need to be verified may include fitness or activity achievements (number of steps, calories burned, first runner on new trail, etc.), difficulty level of achievements (number of steps on steep hills relative to number of steps on flat surfaces, personal records, local records, world records, or combinations thereof. The information may be based on gesture data 225, positioning data, fitness application data, health application data, fitness tracker data, wearable device data, and the like.

Fig. 12A is a perspective view 1200 showing a user 1205 using an ownership device 1210 to purchase a digital asset 1240 (image) of a portrait in a museum. Ownership device 1210 displays a purchase user interface with "purchase" button 1245. Pressing purchase button 1245 allows ownership device 1210 to purchase an existing token 1260 for digital asset 1240 or to request creation (casting) of a new token 1260 for digital asset 1240. Digital asset 1240 may be captured by one or more sensors of the media device (e.g., as in media device 205). In some examples, ownership device 1210 may be a media device that captures digital asset 1240. In some examples, ownership device 1210 may be different from the media device capturing digital asset 1240. For example, the media device capturing digital asset 1240 may be media device 810 of fig. 8A. Ownership device 1210 may include a location sensor 1220. Ownership device 1210 may use its location sensor 1220 to generate location data. The positioning sensor 1220 may be an example of the gesture sensor 215. The positioning data may be an example of gesture data 225. The ownership device 1210 may communicate with a local device 1230 in or near a geographic area (e.g., in a museum). The ownership device 1210 may send one or more communications 1235 to the local device 1230 and/or receive one or more communications 1235 from the local device 1230. Local device 1230 may be an example of local device 270. Communication 1235 may be an example of communication 272. In some examples, if the ownership device 1210 is verified as being in a geographic region (e.g., in a rufiguy museum), the ownership device 1210 may only be provided with ownership (and/or creation/casting) of the purchase token 1260. In some examples, if the ownership device 1210 is verified as being in a geographic region (e.g., in a rufiguy museum), the ownership device 1210 may only be able to become the owner of the token 1260 (and/or cause creation/casting).

Fig. 12B is a conceptual diagram 1250 illustrating information 1255 about a token 1260 associated with digital asset 1240 of fig. 12A. Token 1260 may be an example of token 600. Information 1255 may be partially identified within the token 1260 itself (e.g., as token identifier 610, on-chain immutable metadata 625, on-chain changeable metadata 630, off-chain media 635, off-chain metadata 640, rules of one or more intelligent contracts 645, or a combination thereof). Information 1255 about token 1260 includes a title 1265 indicated as "rufiguy official number mona lisa". Information 1255 about token 1260 includes a copy of digital asset 1240 (e.g., retrieved using an on-chain pointer to off-chain media 635 of token 1260). Information 1255 about token 1260 identifies digital asset type 1270 of digital asset 1240 as an image. Information 1255 about token 1260 includes metadata 1275 associated with the capture of digital asset 1240. Metadata 1275 is shown as a paperclip icon (indicating that metadata 1275 is viewable when the paperclip icon is clicked).

Information 1255 about token 1260 includes history 1280. In some examples, each element of history 1280 is identified as a payload element in a block of the distributed ledger of storage token 1260. History 1280 indicates that at 24 months 5 of 2021, at 2:03:36 pm, digital asset 1240 was captured by the media device while the position sensor of the media device indicated that the pose of the media device was north-facing in the luffa museum and while the media device and local device 1230 at the luffa museum were in communication range. History 1280 indicates that, at 26 months 5 of 2021, 6:40:01 am, server 1285 casts token 1260 based on digital asset 1240 when verifying that ownership device 1210 is in the luffpalace during request of digital asset 1240 (e.g., by verifying that positioning sensor 1220 data matches the luffpalace museum and/or when verifying communication 1235) and/or when verifying that the media device is in the luffpalace museum during capture of digital asset 1240, wherein ownership is set to user 1205. A server 1285 may be an example of a network device 280. History 1280 indicates that at 28, 5, 2021, at 1:22:54 pm, ownership of token 1260 was transferred from user 1205 to user 1290 after user 1290 purchased token 1260 from user 1205.

In some examples, the user interface (with purchase button 1245) for ownership device 1210 may filter which digital assets 1240 and/or tokens 1260 associated therewith are available to be the same, e.g., based on factors such as: authentication (using a particular application to find particular content based on context information, or to specify NFT content for selection by a user for viewing or purchase), user selection, user filtering, crowd-sourced feedback (number of times of viewing, liking, commenting, requesting, etc.), and/or learned user behavior (e.g., behavior learning using machine learning algorithms).

In some examples, the tracking history of tokens (such as histories 880, 980, 1080, 1180, and 1280) may track a chain of custody of tokens corresponding to digital assets (such as token 860 corresponding to digital asset 840, token 960 corresponding to digital asset 940, token 1060 corresponding to digital asset 1040, token 1160 corresponding to digital asset 1140, or token 1260 corresponding to digital asset 1240). In some examples, the user may view the history and/or chain of custody of certain tokens. For example, a visitor to a museum (e.g., a rufiguy museum) may be interested in viewing a history and/or chain of custody of official tokens for a digital copy of a particular work of art in the museum (e.g., an official digital copy of Mona Lisa portrait produced by a museum staff).

Fig. 13 is a conceptual diagram 1300 illustrating anchor element 1350 associated with token 1360 and detection of anchor element 1350 by media device 1310 to trigger display of digital asset 1340 corresponding to the token on media device 1310. The anchor element 1350 may be an example of the anchor element 299 of fig. 2. The anchor element 1350 is shown as an optical glyph, specifically a QR code. In some examples, the optical glyphs of the anchor element 1350 may include QR codes, bar codes, aztec codes, point codes, data matrices, lens codes, or combinations thereof. Other real objects 1347 (e.g., trees) are also shown. In some examples, the optical glyph may optically encode information identifying token 1360, information about token 1360, information indicating token 1360, or a combination thereof. The media device 1310 uses the image sensor 1315 of the media device 1310 to detect the optical glyphs of the anchor element 1350. In some examples, the media device 1310 uses the image sensor 1315 of the media device 1310 to scan the optical glyphs of the anchor element 1350 to decode the optically encoded information in the optical glyphs of the anchor element 1350. Based on the information, media device 1310 determines that anchor element 1350 is associated with token 1360 (e.g., token 600) stored in distributed ledger 1365 (e.g., blockchain ledger 500 and/or DAG ledger 700).

Media device 1310 determines that token 1360 is associated with digital asset 1340 based on information that media device 1310 has decoded from anchor element 1350 about token 1360 and/or based on information that media device 1310 has read about token 1360 in distributed ledger 1365. In the example shown in fig. 13, digital asset 1340 is a virtual object 1345, shown as a virtual dog, similar to virtual object 1045 of fig. 10A. Media device 1310 displays digital asset 1340 (e.g., virtual object 1345) on a display of media device 1310. Media device 1310 may also display information 1355 about token 1360 associated with digital asset 1340. For example, information 1355 may include ownership of token 1360 (e.g., the name of the owner of token 1360 or some other identifier of the owner), an identifier and/or type of distributed ledger 1365 on which token 1360 was cast (e.g.,distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledger 1365, distributed ledger 1415, etc.), information about the smart contracts associated with tokens 1360 (e.g., third party security audits of contracts, when tokens 1360 are cast, when smart contracts are started, when smart contracts are updated, when conditions of smart contracts are met), when tokens 1360 are generated and/or cast, token identifier 610, token unit number 615 (e.g., how many instances of tokens 1360 exist, which instance is the particular token 1360), token ownership 620, any on-chain immutable metadata 625, on-chain changeable metadata 630, off-chain media 635, on-chain media, off-chain metadata 640, token smart contracts 645, any information about any other parameters of tokens 1360, or a combination thereof. In some examples, information 1355 may be included to Interface elements (e.g., buttons, links, URLs, pointers) of the transfer platform may allow token 1360 to be transferred (e.g., purchased, sold, rented, licensed, or some combination thereof). If user 1305 is the current owner of token 1360, the interface element may instruct media device 1310 to sell token 1360 using the transfer platform. If user 1305 is not the current owner of token 1360, the interface element may instruct media device 1310 to purchase token 1360 using the transfer platform.

Media device 1310 may also communicate with data store 1370 to obtain information regarding token 1360, digital asset 1340, and/or any modifications, customizations, and/or personalizations. Data store 1370 may be an example of data store 298 and/or data structure 650. In some examples, some of the information 1355 may be obtained by the media device 1310 from the data store 1370. In some examples, data store 1370 may store modifications, customizations, and/or personalizations to digital asset 1340 (e.g., to virtual object 1345). For example, in fig. 13, one such customization 1357 stored in data store 1370 is shown as a hat (e.g., a party hat) for virtual object 1345 (e.g., a virtual dog). In some examples, modifications, customizations, and/or personalizations for digital asset 1340 may be added by the owner of token 1360. In some examples, modifications, customizations, and/or personalizations for digital asset 1340 may be added by a previous owner of token 1360. In some examples, modifications, customizations, and/or personalizations for digital asset 1340 may be added by a viewer of digital asset 1340 corresponding to token 1360. Different users and/or owners of token 1360 may set different settings that identify who may add modifications, customizations, and/or personalizations to digital asset 1340, and who may not.

In some examples, certain modifications, customizations, and/or personalizations for digital asset 1340 may be automatically applied to digital asset 1340 to help user 1305 know certain information about digital asset 1340 and/or associated token 1360. For example, if user 1305 owns token 1360, a first effect (e.g., one or more of modifying, customizing, and/or personalizing) may be applied to digital asset 1340 as displayed by media device 1310. If a person known to user 1305 (e.g., a friend, family member, colleague, contact, or acquaintance of another relationship type) owns token 1360, a second effect (e.g., one or more of modifying, customizing, and/or personalizing) may be applied to digital asset 1340 as displayed by media device 1310. If a named person (e.g., celebrity) owns token 1360, a third effect (e.g., one or more of modifying, customizing, and/or personalizing) may be applied to digital asset 1340 as displayed by media device 1310. In some examples, different relationship types (e.g., friends versus family versus colleagues) may be associated with different effects (e.g., one or more modifications, customizations, and/or personalizations). In some examples, different types of celebrities (e.g., politicians, sports stars, musicians, movie stars, television stars, famous scientists, etc.) may be associated with different effects (e.g., one or more modifications, customizations, and/or personalizations).

While the media device 1310 is shown first showing a depiction of the anchor element 1350 on its display, it should be understood that this is intended to illustrate that the image sensor 1315 of the media device 1310 has captured an image of the anchor element 1350. In some examples, the anchor element 1350 itself is displayed by the media device 1310, e.g., in an image preview window corresponding to the image sensor 1315. In some examples, the anchor element 1350 itself is never displayed by the media device 1310, and the media device 1310 instead displays the virtual object 1345 in its place (e.g., with the information 1355 and/or the customization 1357).

In some examples, anchor element 1350 may be a different type of anchor element than the optical glyph. For example, in some examples, anchor element 1350 may be an object, where a reference image of the object is stored in data store 1370 and/or in distributed ledger 1365 (e.g., using an on-chain pointer to an off-chain reference image). The media device 1310 may detect and identify an object in an image captured using the image sensor 1315 by comparing the image captured using the image sensor 1315 to a reference image of the object. Data store 1370 may identify token 1360 with a reference image of an object, allowing media device 1310 to determine token 1360 when detecting and/or identifying an object, after which media device 1310 proceeds as described above, outputting digital asset 1340 (e.g., with information 1355 and/or customization 1357).

In some examples, anchor element 1350 may include a designated area identified in data store 1370 and/or in distributed ledger 1365 associated with token 1360. Detection by media device 1310 that media device 1310 is located in a designated area using positioning sensor 1320 and/or image sensor 1315 (e.g., by identifying an image of the environment in the designated area) may cause media device 1310 to output digital asset 1340 (e.g., with information 1355 and/or customization 1357) corresponding to token 1360 corresponding to anchor element 1350. In some examples, anchor element 1350 may include a designated place identified in data store 1370 and/or in distributed ledger 1365 associated with token 1360. Detection by media device 1310 that media device 1310 is within a threshold range of a specified location using positioning sensor 1320 and/or image sensor 1315 (e.g., by identifying an image of an environment in a specified area) may cause media device 1310 to output digital asset 1340 (e.g., with information 1355 and/or customization 1357) corresponding to token 1360 corresponding to anchor element 1350.

Fig. 14 is a conceptual diagram illustrating token device 1405 associated with token 1420 in distributed ledger 1415 and transferring token device 1405 from first user 1410 to second user 1430. Token device 1405 may be an example of a local device 270, a network device 280, a media device 205, one of the additional devices 297, a data store 298, an anchor element 299, an anchor element 1350, a computing system 1900, or a combination thereof. Token device 1405 is associated with token 1420, token 1420 may be associated with digital asset 1425. Digital asset 1425 is shown in fig. 14 as including an image of dogs and trees. Token device 1405 may include an output device such as a display and/or a speaker. The token device 1405 may output the digital asset 1425 associated with the token 1420, for example, by using a display of the token device to output visual content (e.g., images, video) of the digital asset 1425 and/or by using a speaker of the token device to play audio content (e.g., sound, music) of the digital asset 1425. In fig. 14, token device 1405 is shown to include a display showing an image of a dog's tree that is part of digital asset 1425. In some examples, the digital asset 1425 may include video or animated images, and the token device 1405 may, for example, loop play the video or animated images. In some examples, token device 1405 may be a physical representation of token 1420 with which token device 1405 is associated.

As indicated by top scenario 1400A of fig. 14, distributed ledgers 1415 (e.g., blockchain ledgers 500 and/or DAG ledgers 700) associated with tokens 1420 indicate that tokens 1420 are owned by first user 1410. In the middle scenario 1400B and the bottom scenario 1400C of fig. 14, a first user 1410 is shown transferring a token device 1405 to a second user 1430. In intermediate scenario 1400B, distributed ledger 1415 is not updated, resulting in a split ownership scenario in which first user 1410 still owns token 1420 from distributed ledger 1415, but second user 1430 owns token device 1405. This scenario may lead to confusion, as the token device 1405 may be considered to be a physical representation of the token 1420. For example, the first user 1410 may propose to sell the token 1420 to the second user 1430, but instead sell the token device 1405 only to the second user 1430. This may lead to negative results if the second user 1430 is unaware of the token 1420 and the token device 1405, wherein the second user 1430 believes that they have purchased the token 1420 and the token device 1405, but in fact only purchased the token device 1405 and no token 1420.

In the bottom scenario 1400C, the transfer system (e.g., token device 1405, media device 205, network device 280, local device 270, additional device 297, computing system 1900) detects that token device 1405 has been relocated to an area associated with the second user 1430 (e.g., from another area associated with the first user 1410). The transfer system may detect that the token device 1405 is in an area associated with the second user 1430 based on the token device 1405 entering a communication range with one or more devices associated with the second user 1430, such as a local device 1435, a Wireless Local Area Network (WLAN), other token devices owned by the second user 1430 and associated with tokens owned by the second user 1430, or a combination thereof. The transfer system may detect that the token device 1405 is in an area associated with the second user 1430 based on the location sensor of the token device 1405 indicating that the token device 1405 is in a geographic area that has been previously designated (e.g., in the distributed ledger 1415 and/or in the data store 298) as being associated with the second user 1430. The transfer system may detect that the token device 1405 is in an area associated with the second user 1430 based on the location sensor of the token device 1405 indicating that the token device 1405 is within a threshold range of the location of the second user 1430 (e.g., the location of the media device 205 of the second user 1430).

In some examples, distributed ledger 1415 may store intelligent contracts associated with token 1420. The smart contract may be previously agreed upon by the first user 1410. If the token device 1405 is relocated to an area associated with another user (e.g., second user 1430), the smart contract may indicate that the token 1420 is to be transferred to the other user (e.g., second user 1430). In some examples, upon detecting that token device 1405 is relocated to an area associated with second user 1430, the transfer system may query media device 205 associated with first user 1410 to agree to transfer token 1420 to second user 1430, and upon receiving confirmation of approval from media device 205 associated with first user 1410, may proceed to initiate transfer of token 1420 from first user 1410 to second user 1430 (e.g., by causing transfer of token 1420 from first user 1410 to second user 1430 to be recorded in distributed ledger 1415, such as by generating and/or adding a new block with a payload to record the transfer). In some examples, upon detecting that token device 1405 is relocated to an area associated with second user 1430, the transfer system may query media device 205 associated with second user 1430 to agree to transfer token 1420 to second user 1430, and upon receiving confirmation of approval from media device 205 associated with second user 1430, may proceed to initiate transfer of token 1420 from first user 1410 to second user 1430 (e.g., by causing transfer of token 1420 from first user 1410 to second user 1430 to be recorded in distributed ledger 1415, e.g., by generating and/or adding a new block with a payload to record the transfer).

Fig. 15A is a conceptual diagram 1500 illustrating generating and entering a smart contract into a distributed ledger according to an aspect of the disclosure. The distributed computing architecture includes multiple computing systems (referred to herein as computers), which may be computing system 1900 that stores and modifies distributed ledgers. The first computer submits a request 1505 for requesting that an intelligent contract with a particular rule be entered into the distributed ledger. The second computer submits a response 1510 indicating that the second computer has generated a new block to input into the distributed ledger with the requested intelligent contract. Third, fourth, and fifth computer submittal validations 1520A-1520C that indicate that they have validated that the block implemented the smart contract correctly, that the code of the smart contract can be executed (e.g., without including syntax errors or other errors), that all parties involved in the smart contract have submitted consent to the terms of the smart contract, that the on-chain pointer correctly points to the valid off-chain smart contract code, and/or that sufficient funds have been allocated to pay for the execution of the intended payload element. In response to the quorum device verification, the second computer submits an input confirmation indicating that the new block was successfully input into the distributed ledger with the requested smart contract.

A process similar to that shown in fig. 15A may be used to enter tokens, where corresponding validations 1520A-1520C validate that, for example, the token refers to a valid type of digital asset, that the on-chain pointer correctly points to valid off-chain media or metadata, and/or that sufficient funds have been allocated to pay for execution of the intended payload element. A process similar to that shown in fig. 15A may be used to enter a transaction in which corresponding validations 1520A-1520C validate, for example, whether the transferor has a sufficient number of assets (e.g., whether the transferor has tokens to transfer) to conduct the transaction and/or whether sufficient funds are allocated to pay for the execution of the intended payload element.

Fig. 15B is a conceptual diagram 1550 illustrating execution of a smart contract according to an aspect of the present disclosure. The first computer submits an identification 1555 that the first computer has executed the smart contract code, identifying that conditions in the smart contract have been met, and identifying an action to take. The second, third, and fourth computers submit validations 1510A-1510C that identify that the second, third, and fourth computers have executed the smart contract code, that conditions in the smart contract have been met, and that actions are to be taken. The fifth computer indicates an error without verification 1515. The third computer indicates an action 1520 indicating that the third computer has executed the smart contract code and performed the action in response to a quorum of device authentications (e.g., authentication 1510A-1510C).

FIG. 16A is a flow chart illustrating an example of a process 1600 for context token generation according to some examples. Process 1600 may be performed by a digital asset management system. In some examples, the digital asset management system may include the digital asset tracking system 200 of fig. 2 or a portion thereof. In some examples, the imaging system may include, for example, one or more of image capture and processing system 100, image capture device 105A, image processing device 105B, image processor 150, ISP 154, host processor 152, digital asset tracking system 200, media device 205, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD 310, mobile handheld device 410, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, media device 1310, distributed ledger 1365, data store 1370, token device 1405, one or more of the computing systems of fig. 15A, the digital asset tracking system of fig. 15B, the digital asset management system of performing process 1650, the digital asset management system of performing process 1900, the digital asset management system of performing process 1800, computing system 1700, processor 1910, or a combination thereof.

At operation 1605, the digital asset management system is configured and may: media content based on sensor data captured by at least one sensor of a media device is received. Examples of media devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, media device 205, HMD 310, mobile handheld device 410, media device 810, media device 910, media device 1010, media device 1110, ownership device 1210, media device 1310, distributed ledger 1365, data store 1370, token device 1405, computing system of fig. 15A-15B, computing system 1900, or a combination thereof. Examples of at least one sensor include image sensor 130, one or more sensors 210, one or more gesture sensors 215, one or more media sensors 220, first camera 330A, second camera 330B, first camera 430A, second camera 430B, third camera 430C, fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, image sensor 1315, positioning sensor 820, positioning sensor 920, positioning sensor 1020, positioning sensor 1120, positioning sensor 1220, positioning sensor 1320, or a combination thereof. Examples of sensor data may include sensor data 230, pose data 225, images captured by image sensor 130, images processed by ISP 154, images processed by host processor 152, images processed by image processor 152, stored communications of block 278, or a combination thereof. Examples of media data may include media data 250, sensor data 230, gesture data 225, images captured by image sensor 130, images processed by ISP 154, images processed by host processor 152, images processed by image processor 152, stored communications of block 278, digital asset 605, digital asset 840, digital asset 940, digital asset 1040, digital asset 1140, digital asset 1240, digital asset 1340, virtual object 1345, digital asset 1425, or a combination thereof.

In some examples, the digital asset tracking system includes one or more sensor connectors coupled to one or more sensors. One or more sensor connectors may be used to receive media data. One or more sensor connectors may be used to receive sensor data captured by one or more sensors. The one or more sensor connectors may include one or more of a port, a socket, a wire, an input/output (IO) pin, a conductive trace on a Printed Circuit Board (PCB), any other type of connector discussed herein, or some combination thereof. In some examples, the digital asset tracking system includes one or more sensors.

In some examples, the media content includes at least a portion of the sensor data. For example, the media device 205 may obtain the media data 250 by receiving the sensor data 230 and/or the gesture data 225. Digital asset 840 is an example of media data that may be sensor data captured by image sensor 815 of media device 810. Digital asset 940 is an example of media data that may be sensor data captured by image sensor 915 of media device 910.

In some examples, the media content includes a modified variant of at least a portion of the sensor data. Modifying the sensor data may include processing the sensor data, for example, as discussed with respect to image processing device 105B and/or media processor 235. In some aspects, the media device generates the media data at least in part by modifying the sensor data to add virtual content to the sensor data. The virtual content may be generated by the virtual content generator 240. The virtual content may be added to (e.g., combined with) the sensor data using the image synthesizer 245. Examples of virtual content include virtual object 1045 (a virtual dog) that appears in digital asset 1040 (an example of media data) while not appearing in sensor data captured by image sensor 1015, virtual object 1345 (a virtual dog) that appears in digital asset 1340 (an example of media data) while not appearing in sensor data captured by image sensor 1315, or a combination thereof. Digital asset 1140 may also be an example of media content that includes a modified variant of at least a portion of the sensor data, where a map of digital asset 1140 is processed and/or modified form of location data (e.g., collected using location sensor 1120 and/or based on communication between media device 1110 and local device 1130).

At operation 1610, the digital asset management system is configured and may: a location of the media device is determined. In some examples, the digital asset management system may determine the location of the media device based on the sensor data. Examples of locations of media devices include gesture data 225, sensor data 230, location information determined (e.g., by media device 205 and/or locator device 270 and/or digital asset tracking system) based on one or more communications 272, stored communications of block 277, stored communications of block 278, location information determined (e.g., by media device 810 and/or local device 830 and/or digital asset tracking system) based on one or more communications 1035, location information determined (e.g., by image sensor 915 and/or location sensor 915 and/or digital asset tracking system) based on one or more communications, location information determined (e.g., by media device 810 and/or local device 930 and/or digital asset tracking system) based on one or more communications 935, location information determined (e.g., by media device 1010 and/or local device 1030 and/or digital asset tracking system) based on one or more communications 1035, location information determined (e.g., by media device 1235 and/or local device 1230 and/or digital asset tracking system) based on one or digital asset tracking system based on one or more communications 935, location information determined (e.g., by media device 810 and/local device 930 and/or digital asset tracking system) based on one or digital asset tracking system based on one or more communications 935, location information determined using image sensor 1315 and/or location sensor 1320, the location of token device 1405, or a combination thereof.

In some examples, the sensor data includes positioning data based on receipt of at least one wireless signal by at least one sensor. Determining the location of the media device may be based at least in part on the positioning data. In some examples, the at least one wireless signal includes a Global Navigation Satellite System (GNSS) signal (e.g., a GPS signal) received from a GNSS satellite (e.g., a GPS satellite), for example, using a positioning receiver. In some examples, the at least one wireless signal includes a short range wireless signal (e.g., wi-Fi, cellular, WLAN) from a local device that is within a transmission range of the media device at least during receipt of the at least one wireless signal by the at least one sensor. Examples of local devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, local device 1435, the computing system of fig. 15A-15B, computing system 1900, or a combination thereof. Examples of positioning receivers may include one or more short-range wireless transceivers 275, positioning sensors 820, positioning sensors 920, positioning sensors 1020, positioning sensors 1120, positioning sensors 1220, positioning sensors 1320, or combinations thereof. Examples of the at least one wireless signal may include a signal carrying communication 272 between media device 205 and local device 270, a signal carrying communication 835 between mobile device 810 and local device 830, a signal carrying communication 935 between mobile device 910 and local device 930, a signal carrying communication 1035 between mobile device 1010 and local device 1030, a signal carrying communication 1135 between mobile device 1110 and local device 1130, a signal carrying communication 1235 between mobile device 1210 and local device 1230, or a combination thereof.

At operation 1615, the digital asset management system is configured and may: the location of the media device is determined to be within the geographic area. In some examples, the digital asset management system may determine that the location of the media device is within the geographic region based on the sensor data. Examples of geographic areas include a museum (e.g., as in fig. 8A-8B and 12A-12B), an office (e.g., as in fig. 9A-9B), a park (e.g., as in fig. 10A-10B and 13), a trail (e.g., as in fig. 11A-11B), an area associated with the first user 1410, an area associated with the second user 1430, an indoor area, an outdoor area, a stadium, a concert venue, a movie theater, a shopping mall, a transmission range of one or more short-range wireless transceivers 275 of one or more local devices 270, a reception range of one or more short-range wireless transceivers 275 of one or more local devices 270 (for receiving signals transmitted using one or more short-range wireless transceivers 260 of media devices), or a combination thereof. Examples of determining that the location of the media device is within the geographic region include block 290 of the digital asset tracking system 200 of fig. 2, which may be performed by the network device 280, the media device 205, the local device 270, or a combination thereof.

In some examples, the sensor data includes at least one image captured by at least one image sensor of at least one sensor of the media device. The media content may be based on at least one image. Examples of image sensors may include image sensor 130, media sensor 220, one or more media sensors 220, an image sensor of first camera 330A, an image sensor of second camera 330B, an image sensor of first camera 430A, an image sensor of second camera 430B, an image sensor of third camera 430C, an image sensor of fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, or a combination thereof. That is, examples of media data that includes or is based on one or more images include digital asset 840, digital asset 940, digital asset 1040, digital asset 1240, digital asset 1340, digital asset 1425, or a combination thereof.

In some examples, determining the location of the media device includes: detecting at least a portion of an environment in the at least one image; and determining the location of the media device based at least in part on the detection of at least the portion of the environment in the at least one image. In some examples, determining that the location of the media device is within the geographic area includes: at least a portion of an environment in the at least one image is detected, and it is determined that at least the portion of the environment is located within the geographic area. For example, in the context of fig. 8A, the digital asset tracking system may verify that the digital asset 840 is depicted in an object (monlita) in a geographic area (rufiguy museum), and thus may verify that the media device 810 is in a geographic area (rufiguy museum). In the context of fig. 9A, the digital asset tracking system may verify that the digital asset 940 depicts an object (Bob 945) in a geographic area (park), and thus may verify that the media device 910 is in the geographic area (park). In the context of fig. 10A, the digital asset tracking system may verify that digital asset 1040 depicts objects (virtual object 1045 and real object 1047) in a geographic area (park), and thus may verify that media device 1010 is in the geographic area (park). In the context of fig. 11A, the digital asset tracking system may verify that the digital asset 1140 depicts an object (hiking) in a geographic area (yostreamite), and thus may verify that the media device 1110 is in a geographic area (yostreamite). In the context of fig. 13, the digital asset tracking system may verify that digital asset 1340 depicts objects (virtual object 1345 and real object 1347) in a geographic area (park), and thus may verify that media device 1310 is in a geographic area (park).

In some examples, the digital asset management system is configured and may: at least a portion of the individual in the at least one image is detected, the identity of the individual is determined, and parameters of the token (e.g., token ownership 620, token intelligence contract 645) are set to indicate that the token is associated with the identity. In the context of fig. 9A, the digital asset tracking system may identify that the image captured by the image sensor 915 (and corresponding to the digital asset 940) includes a depiction of an individual (Bob 945) having an identified identity. In some aspects, the digital asset tracking system is configured and may: ownership of the token is set to an account associated with the individual having the identified identity. In the context of fig. 9A-9B, the digital asset tracking system may set ownership of the token 960 to Bob 945.

In some examples, the media content includes a map of a geographic area, such as in digital asset 1140.

In some examples, determining that the location of the media device is within the geographic area is based on at least one communication (e.g., communication 272, communication 835, communication 935, communication 1035, communication 1135, communication 1235, etc.) between the media device and a local device associated with the geographic area. Examples of local devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, local device 1435, the computing system of fig. 15A-15B, computing system 1900, or a combination thereof.

At operation 1620, responsive to determining that the location of the media device is within the geographic area at operation 1615, the digital asset management system is configured and operable to: a token corresponding to the media content is generated. The payload of at least one tile of the distributed ledger identifies a token. Examples of tokens may include token 600, token 860, token 960, token 1060, token 1160, token 1260, token 1360, token 1420, or a combination thereof. Examples of distributed ledgers include distributed ledgers 295, blockchain ledgers 500, DAG ledgers 700, distributed ledgers 1365, distributed ledgers 1415, distributed ledgers corresponding to the intelligent contracts of fig. 15A-15B, or combinations thereof. Examples of blocks include block a 505, block B535, block C565, block 710, block 720, block 730, block 740, block 750, block 760, or a combination thereof. Examples of payloads include a block a payload 530, a block B payload 560, and a block C payload 590. The token may be an irreplaceable token (NFT).

In some examples, the digital asset management system is configured and may: at least one tile is generated in response to determining that the location of the media device is within the geographic area and causing the at least one tile to be appended to the distributed ledger. In some examples, at least one chunk includes a hash of at least a portion of a previous chunk of the distributed ledger (e.g., hash 515/545/575, merck root 520/550/580). In some examples, the digital asset management system is configured and may: a distributed ledger is generated in response to determining that the location of the media device is within the geographic area.

In some examples, the digital asset management system is configured and may: the method includes sending a request to the computing device to generate at least one tile, receiving the at least one tile, and attaching the at least one tile to the distributed ledger in response to determining that the location of the media device is within the geographic area.

In some examples, the digital asset management system is configured and may: parameters of the token (e.g., token ownership 620, token intelligence contract 645) are set to indicate that the token is associated with the user. The media device may be associated with a user. For example, in the context of fig. 8A-8B, the digital asset tracking system may set parameters of token 860 to indicate 805. In the context of fig. 9A-9B, the digital asset tracking system may set parameters of the token 960 to indicate that the token is associated with the user 905. In the context of fig. 10A-10B, the digital asset tracking system may set parameters of the token 1060 to indicate that the token is associated with the user 1005. In the context of fig. 11A-11B, the digital asset tracking system may set parameters of the token 1160 to indicate that the token is associated with the user 1105. In the context of fig. 12A-12B, the digital asset tracking system may set parameters of token 1260 to indicate that the token is associated with user 1205. In the context of fig. 13, the digital asset tracking system may set parameters of token 1360 to indicate that the token is associated with user 1305. In the context of fig. 14, the digital asset tracking system may set parameters of the token 1420 to indicate that the token is associated with the first user 1410 and/or the second user 1430. In some examples, parameters of the token may be stored on the chain, such as in token ownership 620, on-chain immutable metadata 625, and/or on-chain mutable metadata 630. In some examples, the parameters of the token may be stored off-chain, such as in off-chain metadata 640.

In some examples, the digital asset management system is configured and may: determining the geographic area includes at least a threshold number of people. Generating tokens corresponding to media content may be performed in response to determining that the geographic region includes at least a threshold amount of people.

In some examples, the digital asset management system performing process 1600 may include a media device, a local device, or a combination thereof. In some examples, the digital asset management system performing process 1600 is located in a geographic region.

In some examples, the digital asset management system performing process 1600 may include at least one of a Head Mounted Display (HMD) (e.g., HMD 310), a mobile handheld device (e.g., mobile handheld device 410), a wireless communication device, or a combination thereof.

In some examples, a digital asset management system includes: means for receiving media content based on sensor data captured by at least one sensor of a media device; means for determining a location of the media device; means for determining that a location of the media device is within a geographic area; and means for generating a token corresponding to the media content in response to determining that the location of the media device is within the geographic area, wherein a payload of at least one tile of the distributed ledger identifies the token.

In some examples, the means for receiving media content includes one or more of image capture and processing system 100, image sensor 130, digital asset tracking system 200, one or more of sensor 210, one or more of gesture sensor 215, one or more of media sensor 220, first camera 330A, second camera 330B, first camera 430A, second camera 430B, third camera 430C, fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, image sensor 1315, location sensor 820, location sensor 920, location sensor 1020, location sensor 1120, location sensor 1220, location sensor 1320, media device 205, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD, mobile handheld device 410, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1130, ownership device 1210, local device 1110, local device 1230, distributed device 1370, computing device 15, or a combination thereof.

In some examples, the means for determining the location of the media device and/or determining the location of the media device within the geographic area includes a system of image capture and processing 100, image sensor 130, digital asset tracking system 200, one or more sensors 210, one or more gesture sensors 215, one or more media sensors 220, first camera 330A, second camera 330B, first camera 430A, second camera 430B, third camera 430C, fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, image sensor 1315, location sensor 820, location sensor 920, location sensor 1020, location sensor 1120, location sensor 1220, location sensor 1320, media device 205, network device 280, local device 270, additional device 297, data storage 298, anchor element 299, HMD 310, mobile device 410, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, 1110, media device 1210, local device 1130, local device 810, local device 1230, computing system of a, computing system 15, computing system of any one or more of the other devices 15, or a combination of the systems.

In some examples, the means for generating the token includes digital asset tracking system 200, media device 205, network device 280, local device 270, distributed ledger 295, additional device 297, data store 298, anchor element 299, HMD 310, mobile handheld device 410, blockchain ledger 500, token 600, data structure 650, DAG ledger 700, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, one or more of media device 1310, anchor element 1350, distributed ledger 1365, data store 1370, token device 1405, one or more of the computing systems of fig. 15A, computing system 1900, output device 1935, communication interface 1940, or a combination thereof.

FIG. 16B is a flow chart illustrating an example of a process 1650 for tracking digital assets associated with a location according to some examples. Process 1650 may be performed by a digital asset tracking system. In some examples, the digital asset tracking system may include the digital asset tracking system 200 of fig. 2 or a portion thereof. In some examples, the imaging system may include, for example, image capture and processing system 100, image capture device 105A, image processing device 105B, image processor 150, ISP 154, host processor 152, digital asset tracking system 200, media device 205, network device 280, local device 270, additional device 297, HMD 310, mobile handheld device 410, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, one or more of the computing systems of fig. 15A, one or more of the computing systems of fig. 15B, computing system 1900, processor 1910, or a combination thereof.

At operation 1655, the digital asset tracking system is configured and operable to: media data based on sensor data captured by one or more sensors of the media device is received from the media device. Examples of media devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, media device 205, HMD 310, mobile handheld device 410, media device 810, media device 910, media device 1010, media device 1110, ownership device 1210, media device 1310, distributed ledger 1365, data store 1370, token device 1405, computing system 1900 of fig. 15A-15B, or a combination thereof. Examples of the one or more sensors include image sensor 130, one or more sensors 210, one or more gesture sensors 215, one or more media sensors 220, first camera 330A, second camera 330B, first camera 430A, second camera 430B, third camera 430C, fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, image sensor 1315, positioning sensor 820, positioning sensor 920, positioning sensor 1020, positioning sensor 1120, positioning sensor 1220, positioning sensor 1320, or a combination thereof. Examples of sensor data may include sensor data 230, pose data 225, images captured by image sensor 130, images processed by ISP 154, images processed by host processor 152, images processed by image processor 152, stored communications of block 278, or a combination thereof. Examples of media data may include media data 250, sensor data 230, gesture data 225, images captured by image sensor 130, images processed by ISP 154, images processed by host processor 152, images processed by image processor 152, stored communications of block 278, digital asset 605, digital asset 840, digital asset 940, digital asset 1040, digital asset 1140, digital asset 1240, digital asset 1340, virtual object 1345, digital asset 1425, or a combination thereof.

The media data may be sensor data. The media data may include sensor data. For example, the media device 205 may obtain the media data 250 by receiving the sensor data 230 and/or the gesture data 225. Digital asset 840 is an example of media data that may be sensor data captured by image sensor 815 of media device 810. Digital asset 940 is an example of media data that may be sensor data captured by image sensor 915 of media device 910.

The media device generates media data at least in part by modifying the sensor data. Modifying the sensor data may include processing the sensor data, for example, as discussed with respect to image processing device 105B and/or media processor 235. In some aspects, the media device generates the media data at least in part by modifying the sensor data to add virtual content to the sensor data. The virtual content may be generated by the virtual content generator 240. The virtual content may be added to (e.g., combined with) the sensor data using the image synthesizer 245. Examples of virtual content include virtual objects 1045 (virtual dogs) that appear in digital assets 1040 (examples of media data) although not in sensor data captured by image sensors 1015.

The sensor data may include one or more images captured by one or more image sensors of one or more sensors of the media device. The media data may be based on at least one of the one or more images. Examples of image sensors may include image sensor 130, media sensor 220, one or more media sensors 220, an image sensor of first camera 330A, an image sensor of second camera 330B, an image sensor of first camera 430A, an image sensor of second camera 430B, an image sensor of third camera 430C, an image sensor of fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, or a combination thereof. That is, examples of media data that includes or is based on one or more images include digital asset 840, digital asset 940, digital asset 1040, digital asset 1240, digital asset 1340, digital asset 1425, or a combination thereof.

At operation 1660, the digital asset tracking system is configured and may: positioning data is received, the positioning data indicating a location of the media device while sensor data is captured by one or more sensors of the media device. Examples of positioning data may include gesture data 225, sensor data 230, positioning information determined (e.g., by media device 205 and/or local device 270 and/or digital asset tracking system) based on one or more communications 272, stored communications of block 277, stored communications of block 278, positioning information determined (e.g., by media device 810 and/or local device 830 and/or digital asset tracking system) based on one or more communications 835, positioning information determined (e.g., by media device 910 and/or local device 930 and/or digital asset tracking system) based on one or more communications 935, positioning information determined (e.g., by media device 1030 and/or local device 1030 and/or digital asset tracking system) based on one or more communications 1035, positioning information determined (e.g., by media device 1030 and/or local device 1030 and/or digital asset tracking system) based on one or digital asset tracking system based on one or more communications 1110, positioning information determined (e.g., by media device 1135 and/or digital asset tracking system) based on one or more communications 935 Location information determined using image sensor 1315 and/or location sensor 1320, the location of token device 1405, or a combination thereof.

The sensor data may include positioning data that is determined based on receipt of one or more positioning signals by a positioning receiver in one or more sensors of the media device. For example, at least some of the positioning data may include gesture data 225 from one or more gesture sensors 215 and/or positioning information determined by the media device 205 based on the communication 272. The media data may include a map generated by the media device based on the positioning data. The media device may generate the media data at least in part by generating a map based on the positioning data and/or the sensor data. Examples of such maps include maps generated by media device 1110 in digital asset 1140 based on location sensor data from location sensor 1120.

The sensor data may include auxiliary positioning data determined based on receipt of one or more positioning signals by a positioning receiver of one or more sensors of the media device. Examples of the one or more positioning signals may include GNSS signals, such as GPS signals. Examples of positioning receivers may include GNSS receivers, such as GPS receivers. Examples of the one or more positioning signals may include a signal carrying communication 272 between media device 205 and local device 270, a signal carrying communication 835 between mobile device 810 and local device 830, a signal carrying communication 935 between mobile device 910 and local device 930, a signal carrying communication 1035 between mobile device 1010 and local device 1030, a signal carrying communication 1135 between mobile device 1110 and local device 1130, a signal carrying communication 1235 between mobile device 1210 and local device 1230, or a combination thereof. The media data may include a map generated by the media device based on the positioning data. The media device may generate the media data at least in part by generating a map based on the positioning data and/or the sensor data. Examples of such maps include maps generated by media device 1110 in digital asset 1140 based on location sensor data from location sensor 1120. Examples of positioning receivers may include short-range wireless transceiver 260, short-range wireless transceiver 275, or a combination thereof.

To receive the positioning data, the digital asset tracking system may receive the positioning data from the media device. The positioning data may be based on one or more positioning signals received by a positioning receiver of one or more sensors of the media device. For example, at least some of the positioning data may include gesture data 225 from one or more gesture sensors 215 and/or positioning information determined by the media device 205 based on the communication 272. Examples of positioning receivers may include GNSS receivers, such as GPS receivers. Examples of the one or more positioning signals may include GNSS signals, such as GPS signals. Examples of positioning receivers may include positioning sensor 820, positioning sensor 920, positioning sensor 1020, positioning sensor 1120, positioning sensor 1220, or a combination thereof. Examples of positioning receivers may include one or more short-range wireless transceivers 260, positioning sensors 820, positioning sensors 920, positioning sensors 1020, positioning sensors 1120, positioning sensors 1220, positioning sensors 1320, or combinations thereof. Examples of the one or more positioning signals may include a signal carrying communication 272 between media device 205 and local device 270, a signal carrying communication 835 between mobile device 810 and local device 830, a signal carrying communication 935 between mobile device 910 and local device 930, a signal carrying communication 1035 between mobile device 1010 and local device 1030, a signal carrying communication 1135 between mobile device 1110 and local device 1130, a signal carrying communication 1235 between mobile device 1210 and local device 1230, or a combination thereof.

To receive the positioning data, the digital asset tracking system may receive the positioning data from a local device that is different from the media device. The positioning data may be based on one or more positioning signals received by a positioning receiver of the local device. Examples of local devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, local device 1435, the computing system of fig. 15A-15B, computing system 1900, or a combination thereof. Examples of positioning receivers may include one or more short-range wireless transceivers 275. Examples of the one or more positioning signals may include a signal carrying communication 272 between media device 205 and local device 270, a signal carrying communication 835 between mobile device 810 and local device 830, a signal carrying communication 935 between mobile device 910 and local device 930, a signal carrying communication 1035 between mobile device 1010 and local device 1030, a signal carrying communication 1135 between mobile device 1110 and local device 1130, a signal carrying communication 1235 between mobile device 1210 and local device 1230, or a combination thereof.

The positioning receiver may be a short-range wireless communication receiver configured to receive one or more short-range wireless communication signals. Examples of short-range wireless communication receivers include one or more short-range wireless transceivers 260. One or more short-range wireless communication signals may be transmitted by local devices in a geographic area. Examples of local devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, the computing system of fig. 15A-15B, computing system 1900, or a combination thereof. Examples of the one or more short-range wireless communication signals may include a signal carrying communication 272 between media device 205 and local device 270, a signal carrying communication 835 between mobile device 810 and local device 830, a signal carrying communication 935 between mobile device 910 and local device 930, a signal carrying communication 1035 between mobile device 1010 and local device 1030, a signal carrying communication 1135 between mobile device 1110 and local device 1130, a signal carrying communication 1235 between mobile device 1210 and local device 1230, or a combination thereof. The geographic area may correspond to a transmission range of one or more short-range wireless communication signals of the local device. In some examples, the positioning receiver may be a Global Navigation Satellite System (GNSS) receiver configured to receive one or more GNSS signals from one or more satellites.

In some aspects, a digital asset tracking system includes a local device. In some aspects, a digital asset tracking system includes a media device.

At operation 1665, the digital asset tracking system is configured and may: the location of the media device within the geographic area while capturing the sensor data is verified based on the positioning data. Examples of verifying that the location of the media device is within the geographic area while capturing the sensor data include block 290 of the digital asset tracking system 200 of fig. 2, which may be performed by the network device 280, the media device 205, the local device 270, or a combination thereof. Examples of geographic areas include a museum, a sports venue, a concert venue, a movie theater, a shopping mall, a transmission range of one or more short-range wireless transceivers 275 of one or more local devices 270, a reception range of one or more short-range wireless transceivers 275 of one or more local devices 270 (for receiving signals transmitted using one or more short-range wireless transceivers 260 of a media device), or a combination thereof.

To verify that the location of the media device is within the geographic area while the sensor data is captured, the digital asset tracking system may verify the content of one or more communications between the media device and a local device associated with the geographic area. To verify that the location of the media device is within the geographic area while the sensor data is captured, the digital asset tracking system may verify the timing of the transmission and/or reception of one or more communications between the media device and a local device associated with the geographic area. To verify that the location of the media device is within the geographic area while the sensor data is captured, the digital asset tracking system may verify the transmit frequency and/or the receive frequency of one or more communications between the media device and a local device associated with the geographic area. Examples of local devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, the computing system of fig. 15A-15B, computing system 1900, or a combination thereof. One or more communication attributes, such as content, timing of transmission, timing of reception, frequency of transmission, and/or frequency of reception, may be stored in the stored communication at block 277 at the local device and/or in the stored communication at block 278 at the media device 205. Examples of the one or more communications may include a signal carrying communication 272 between media device 205 and local device 270, a signal carrying communication 835 between mobile device 810 and local device 830, a signal carrying communication 935 between mobile device 910 and local device 930, a signal carrying communication 1035 between mobile device 1010 and local device 1030, a signal carrying communication 1135 between mobile device 1110 and local device 1130, a signal carrying communication 1235 between mobile device 1210 and local device 1230, or a combination thereof.

To verify that the location of the media device is within the geographic area while the sensor data is captured, the digital asset tracking system may verify that the sensor data (and/or the media data) depicts objects visible within the geographic area. For example, in the context of fig. 8A, the digital asset tracking system may verify that the digital asset 840 is depicted in an object (monlita) in a geographic area (rufiguy museum), and thus may verify that the media device 810 is in a geographic area (rufiguy museum). In the context of fig. 9A, the digital asset tracking system may verify that the digital asset 940 depicts an object (Bob 945) in a geographic area (park), and thus may verify that the media device 910 is in the geographic area (park). In the context of fig. 10A, the digital asset tracking system may verify that digital asset 1040 depicts objects (virtual object 1045 and real object 1047) in a geographic area (park), and thus may verify that media device 1010 is in the geographic area (park). In the context of fig. 11A, the digital asset tracking system may verify that the digital asset 1140 depicts an object (hiking route) in a geographic area (yostreamite), and thus may verify that the media device 1110 is in a geographic area (yostreamite). In the context of fig. 13, the digital asset tracking system may verify that digital asset 1340 depicts objects (virtual object 1345 and real object 1347) in a geographic area (park), and thus may verify that media device 1310 is in a geographic area (park).

At operation 1670, the digital asset tracking system is configured and operable to: a token corresponding to the media data is automatically generated in response to verifying that the location of the media device is within the geographic region, the token being identified in a payload of a tile of the distributed ledger. Examples of tokens may include token 600, token 860, token 960, token 1060, token 1160, token 1260, token 1360, token 1420, or a combination thereof. Examples of distributed ledgers include distributed ledgers 295, blockchain ledgers 500, DAG ledgers 700, distributed ledgers 1365, distributed ledgers 1415, distributed ledgers corresponding to the intelligent contracts of fig. 15A-15B, or combinations thereof. Examples of blocks include block a 505, block B535, block C565, block 710, block 720, block 730, block 740, block 750, block 760, or a combination thereof. Examples of payloads include a block a payload 530, a block B payload 560, and a block C payload 590. The token may be an irreplaceable token (NFT).

In some aspects, the digital asset tracking system is configured and may: a block for the distributed ledger is automatically generated in response to verifying that the location of the media device is within the geographic area. In some aspects, the digital asset tracking system is configured and may: blocks are appended to multiple blocks of the distributed ledger. In some aspects, the digital asset tracking system is configured and may: the tile is sent to the plurality of computing devices such that the plurality of computing devices may append the tile to respective copies of their distributed ledgers. Examples of the plurality of computing devices may include additional devices 297, the computing systems of fig. 15A-15B, computing system 1900, or a combination thereof.

In some aspects, the digital asset tracking system is configured and may: a request for generating a tile for the distributed ledger is automatically sent to the tile generation computing device in response to verifying that the location of the media device is within the geographic area. In some aspects, the digital asset tracking system is configured and may: a block is received from a block generating computing device. In some aspects, the digital asset tracking system is configured and may: blocks are appended to multiple blocks of the distributed ledger. Examples of block-generating computing devices may include one of the additional devices 297, one of the computing systems of fig. 15A-15B, computing system 1900, or a combination thereof.

The block may include a hash of at least a portion of a previous block of the distributed ledger. Examples of hashes include hash 515, hash 545, and hash 575. A chunk may include the merck root of multiple elements of the payload of the chunk. Examples of merck roots include merck root 520, merck root 550, and merck root 580. The token may correspond to at least one element of the plurality of elements of the payload of the chunk. In some aspects, the digital asset tracking system is configured and may: a distributed ledger is automatically generated in response to verifying that the location of the media device is within the geographic area.

In some aspects, the digital asset tracking system is configured and may: ownership of the token is set to an account associated with a user associated with the media device. For example, in the context of fig. 8A-8B, the digital asset tracking system may set ownership of token 860 to user 805. In the context of fig. 9A-9B, the digital asset tracking system may set ownership of the token 960 to the user 905. In the context of fig. 10A-10B, the digital asset tracking system may set ownership of the token 1060 to the user 1005. In the context of fig. 11A-11B, the digital asset tracking system may set ownership of the token 1160 to the user 1105. In the context of fig. 12A-12B, the digital asset tracking system may set ownership of token 1260 to user 1205. In the context of fig. 13, the digital asset tracking system may set ownership of token 1360 to user 1305. In the context of fig. 13, the digital asset tracking system may set ownership of token 1420 to first user 1410 and/or second user 1430. In some examples, ownership of the token may be stored on the chain, such as in token ownership 620, on-chain immutable metadata 625, and/or on-chain mutable metadata 630. In some examples, ownership of the token may be stored off-chain, such as in off-chain metadata 640.

In some aspects, the digital asset tracking system is configured and may: the identification sensor data includes a representation of an individual having an identified identity. In the context of fig. 9A, the digital asset tracking system may identify that the image captured by the image sensor 915 (and corresponding to the digital asset 940) includes a depiction of an individual (Bob 945) having an identified identity. In some aspects, the digital asset tracking system is configured and may: ownership of the token is set to an account associated with the individual having the identified identity. In the context of fig. 9A-9B, the digital asset tracking system may set ownership of the token 960 to Bob 945.

In some aspects, the media device includes a head mounted display, such as HMD 310. In some aspects, the media devices include mobile handsets such as mobile handset 410, media device 810, media device 910, media device 1010, media device 1110, ownership device 1210, or a combination thereof. In some aspects, the media device comprises a wearable device. In some aspects, the media device is in a geographic region.

In some aspects, the digital asset tracking system includes a head mounted display, such as HMD 310. In some aspects, the digital asset tracking system comprises a mobile handset, such as mobile handset 410, media device 810, media device 910, media device 1010, media device 1110, ownership device 1210, or a combination thereof. In some aspects, the digital asset tracking system includes a wearable device. In some aspects, the digital asset tracking system includes a server. In some aspects, the digital asset tracking system is in a geographic region.

In some aspects, a digital asset tracking system may include: the apparatus includes means for receiving media data based on sensor data captured by one or more sensors of a media device. In some aspects, a digital asset tracking system may include: the apparatus includes means for receiving positioning data indicative of a location of a media device while capturing sensor data with one or more sensors of the media device. In some aspects, a digital asset tracking system may include: the apparatus includes means for verifying that a location of the media device is within a geographic region while capturing sensor data based on the positioning data. In some aspects, a digital asset tracking system may include: the apparatus includes means for automatically generating a token corresponding to the media data in response to verifying that the location of the media device is within the geographic region, the token being identified in a payload of a tile of the distributed ledger.

In some examples, the means for receiving media data includes the network device 280. In some examples, the means for receiving media data includes the media device 205, the media device 810, the media device 910, the media device 1010, the media device 1110, the ownership device 1210, or a combination thereof. In some examples, the means for receiving media data includes local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, or a combination thereof. In some examples, the means for receiving media data includes HMD 310. In some examples, the means for receiving media data includes the media processor 235. In some examples, the means for receiving media data includes the mobile handset 410. In some examples, the means for receiving media data includes the image sensor 130. In some examples, the means for receiving media data includes the image capture device 105A, the image processing device 105B, the image capture and processing system 100, or a combination thereof. In some examples, the means for receiving media data includes receiving media data from a network transceiver (such as network transceiver 265) of the media device 205 at the network transceiver (such as network transceiver 285) via the communication 282. In some examples, the means for receiving media data includes capturing sensor data (such as gesture data 225 and/or sensor data 230) by one or more sensors 210 of the media device 205. In some examples, the means for receiving media data includes generating and/or obtaining media data 250 at the media device 205. In some examples, the means for receiving media data includes capturing sensor data (such as gesture data 225 and/or sensor data 230) by one or more sensors 210 of the media device 205. In some examples, the means for receiving media data includes generating and/or obtaining media data 250 at the media device 205. In some examples, the means for receiving media data includes digital asset 605. In some examples, the means for receiving media data includes digital asset 840, digital asset 940, digital asset 1040, digital asset 1140, digital asset 1240, or a combination thereof. In some examples, the means for receiving media data includes an image sensor 815, an image sensor 915, an image sensor 1015, or a combination thereof. In some examples, the means for receiving media data includes a digital asset tracking system that performs process 0016. In some examples, the means for receiving media data includes the first camera 330A and/or the second camera 330B. In some examples, the means for receiving media data includes the first camera 430A, the second camera 430B, the third camera 430C, the fourth camera 430D, or a combination thereof.

In some examples, the means for receiving positioning data includes the network device 280. In some examples, the means for receiving positioning data includes the media device 205, the media device 810, the media device 910, the media device 1010, the media device 1110, the ownership device 1210, or a combination thereof. In some examples, the means for receiving positioning data includes local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, or a combination thereof. In some examples, the means for receiving positioning data includes HMD 310. In some examples, the means for receiving positioning data comprises the mobile handset 410. In some examples, the means for receiving positioning data includes receiving, at a network transceiver (such as network transceiver 285), gesture data from a network transceiver (such as network transceiver 265) of the media device 205 via the communication 282 (e.g., as gesture data 225 and/or as part of the media data 250 and/or as part of the information about the communication 272). In some examples, the means for receiving positioning data includes capture of gesture data 225 and/or sensor data 230 by one or more sensors 210 of the media device 205. In some examples, the means for receiving positioning data includes receiving a stored copy of the communication 272 (e.g., a stored communication of block 277 and/or a stored communication of block 278). In some examples, the means for receiving positioning data includes generating and/or obtaining media data 250 at the media device 205 (e.g., where the media data is based at least in part on the gesture data 225 and/or includes the gesture data 225). In some examples, the means for receiving media data includes receiving media data at a network transceiver (such as network transceiver 285) from a network transceiver (such as network transceiver 265) of the media device 205 via the communication 282. In some examples, the means for receiving positioning data includes positioning sensor 820, positioning sensor 920, positioning sensor 1020, positioning sensor 1120, positioning sensor 1220, or a combination thereof. In some examples, the means for receiving positioning data includes a digital asset tracking system that performs process 1650. In some examples, the means for receiving positioning data includes receiving data about communication 272 from media device 205 and/or from local device 270, receiving data about communication 835 from media device 810 and/or from local device 830, receiving data about communication 935 from media device 910 and/or from local device 930, receiving data about communication 1035 from media device 1010 and/or from local device 1030, receiving data about communication 1135 from media device 1110 and/or from local device 1130, receiving data about communication 1235 from ownership device 1210 and/or from local device 1230, or a combination thereof. In some examples, the means for receiving positioning data includes the first camera 330A and/or the second camera 330B. In some examples, the means for receiving positioning data includes a first camera 430A, a second camera 430B, a third camera 430C, a fourth camera 430D, or a combination thereof.

In some examples, the means for verifying the location of the media device includes the network device(s) 280. In some examples, the means for verifying the location of the media device comprises the media device 205, the media device 810, the media device 910, the media device 1010, the media device 1110, the ownership device 1210, or a combination thereof. In some examples, the means for verifying the location of the media device comprises local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, or a combination thereof. In some examples, the means for verifying the location of the media device includes the HMD 310. In some examples, the means for verifying the location of the media device comprises the mobile handset 410. In some examples, the means for verifying the location of the media device includes the media device 205. In some examples, the means for verifying the location of the media device includes the local device 270. In some examples, the means for verifying the location of the media device includes verifying that the pose of the media device 205 is in a geographic region associated with the local device 270 (block 290). In some examples, the means for verifying the location of the media device includes receiving, at a network transceiver (e.g., network transceiver 285) from a network transceiver (e.g., network transceiver 265) of the media device 205 via communication 282, and comparing the location data to a geographic area. In some examples, the means for verifying the location of the media device includes token intelligence contract 645. In some examples, the means for verifying the location of the media device includes the smart contract of fig. 15A-15B. In some examples, the means for verifying the location of the media device includes a digital asset tracking system that performs process 1650.

In some examples, the means for generating a token corresponding to media data includes the network device(s) 280. In some examples, the means for generating tokens corresponding to media data includes media device 205, media device 810, media device 910, media device 1010, media device 1110, ownership device 1210, or a combination thereof. In some examples, the means for generating a token corresponding to the media data includes the local device 270, the local device 830, the local device 930, the local device 1030, the local device 1130, the local device 1230, or a combination thereof. In some examples, the means for generating tokens corresponding to media data includes HMD 310. In some examples, the means for generating a token corresponding to the media data includes the mobile handset 410. In some examples, the means for generating tokens corresponding to media data includes distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledgers corresponding to the smart contracts of fig. 15A-15B, or a combination thereof. In some examples, the means for generating a token corresponding to the media data includes token 600. In some examples, the means for generating tokens corresponding to media data includes token 860, token 960, token 1060, token 1160, token 1260, or a combination thereof. In some examples, the means for generating a token corresponding to the media data includes the token intelligence contract 645. In some examples, the means for generating tokens corresponding to media data includes the smart contracts of fig. 15A-15B. In some examples, the means for generating tokens corresponding to media data includes the computing system of fig. 15A-15B. In some examples, the means for generating a token corresponding to media data includes a computing system of 1900. In some examples, the means for generating a token corresponding to the media data includes a digital asset tracking system that performs process 1650.

FIG. 17 is a flow chart illustrating a process 1700 for context token associated media output. Process 1700 may be performed by a digital asset management system. In some examples, the digital asset management system may include the digital asset tracking system 200 of fig. 2 or a portion thereof. In some examples, the imaging system may include, for example, one or more of image capture and processing system 100, image capture device 105A, image processing device 105B, image processor 150, ISP 154, host processor 152, digital asset tracking system 200, media device 205, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD 310, mobile handheld device 410, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, media device 1310, distributed ledger 1365, data store 1370, token device 1405, one or more 165of the computing systems of fig. 15A, the digital asset management system of fig. 15B, the digital asset tracking system of executing process 1600, the digital asset tracking system of executing process 1800, the computing system of executing process 1800, processor 1910, or a combination thereof.

At operation 1705, the digital asset management system is configured and may: sensor data captured by at least one sensor of a media device is received. Examples of media devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, media device 205, HMD 310, mobile handheld device 410, media device 810, media device 910, media device 1010, media device 1110, ownership device 1210, media device 1310, distributed ledger 1365, data store 1370, token device 1405, computing system of fig. 15A-15B, computing system 1900, or a combination thereof. Examples of at least one sensor include image sensor 130, one or more sensors 210, one or more gesture sensors 215, one or more media sensors 220, first camera 330A, second camera 330B, first camera 430A, second camera 430B, third camera 430C, fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, image sensor 1315, positioning sensor 820, positioning sensor 920, positioning sensor 1020, positioning sensor 1120, positioning sensor 1220, positioning sensor 1320, or a combination thereof. Examples of sensor data may include sensor data 230, pose data 225, images captured by image sensor 130, images processed by ISP 154, images processed by host processor 152, images processed by image processor 152, stored communications of block 278, or a combination thereof.

At operation 1710, the digital asset management system is configured and may: a relationship between the media device and an anchor element associated with the token is identified based on the sensor data. In some examples, the relationship between the media device and the anchor element may include interactions between the media device and the anchor element. Examples of anchor elements include anchor element 299, anchor element 1350, an optical glyph, a specified region, a specified location, a specified sound, and the like.

In some examples, the sensor data includes image data captured by at least one image sensor of at least one sensor of the media device. The anchor element may include an object. Identifying the relationship between the media device and the anchor element may include identifying that the image data depicts the object. For example, in some examples, the object includes an optical glyph, and the information indicative of the token is optically encoded based on the optical glyph, as shown in anchor element 1350. Examples of optical glyphs include Quick Response (QR) codes, bar codes, aztec codes, dot codes, data matrices, lens codes, or combinations thereof. In some examples, reference image data depicting the object is stored in a data store (e.g., data store 298, data structure 650, data store 1370), and identifying the image data depicting the object includes comparing the image data to the reference image data.

In some examples, the sensor data includes location data indicating a location of the media device. Examples of location data may include gesture data 225, sensor data 230, location information determined (e.g., by media device 205 and/or locator device 270 and/or digital asset tracking system) based on one or more communications 272, stored communications of block 277, stored communications of block 278, location information determined (e.g., by media device 810 and/or local device 830 and/or digital asset tracking system) based on one or more communications 835, location information determined (e.g., by media device 910 and/or local device 930 and/or digital asset tracking system) based on one or more communications 935, location information determined (e.g., by media device 1030 and/or digital asset tracking system) based on one or more communications 1035, location information determined (e.g., by media device 1030 and/or local device 1030 and/or digital asset tracking system) based on one or more communications 1220, location information determined (e.g., by media device 1220, local device and/or local device 1220, etc., based on one or digital asset tracking system based on one or more communications 1220 Location information determined using image sensor 1315 and/or location sensor 1320, the location of token device 1405, or a combination thereof.

In some examples, the anchor element includes a region, and identifying the relationship between the media device and the anchor element includes identifying that the location of the media device is within the region. In some examples, the anchor element includes a place, and identifying the relationship between the media device and the anchor element includes identifying that the location of the media device is within a threshold range of the place. In some examples, the threshold range of the area and/or location includes an area within a communication range of the local device. Examples of local devices may include image capture and processing system 100, image capture device 105A, image processing device 105B, local device 270, local device 830, local device 930, local device 1030, local device 1130, local device 1230, local device 1435, the computing system of fig. 15A-15B, computing system 1900, or a combination thereof.

In some examples, the sensor data includes audio data captured by at least one microphone (e.g., sensor 210) of at least one sensor of the media device. In some examples, the anchor element comprises a sound, and identifying the relationship between the media device and the anchor element comprises identifying that the audio data comprises a sound. For example, if a particular song or other sound is playing in an area, the relationship between the media device and the anchor element may be identified by detecting the sound recorded from the microphone of the media device.

At operation 1715, the digital asset management system is configured and may: a token is identified in a payload of at least one tile of the distributed ledger, wherein the token corresponds to media content according to the distributed ledger. For example, in the context of fig. 13, in response to identifying a relationship between media device 1310 and anchor element 1350 (e.g., media device 1310 has scanned a QR code of anchor element 1350), digital asset management system may identify token 1360 in distributed ledger 1365, and token 1360 may correspond to digital asset 1340 (e.g., media content).

Examples of tokens may include token 600, token 860, token 960, token 1060, token 1160, token 1260, token 1360, token 1420, or a combination thereof. Examples of distributed ledgers include distributed ledgers 295, blockchain ledgers 500, DAG ledgers 700, distributed ledgers 1365, distributed ledgers 1415, distributed ledgers corresponding to the intelligent contracts of fig. 15A-15B, or combinations thereof. Examples of blocks include block a 505, block B535, block C565, block 710, block 720, block 730, block 740, block 750, block 760, or a combination thereof. Examples of payloads include a block a payload 530, a block B payload 560, and a block C payload 590. The token may be an irreplaceable token (NFT).

At operation 1720, the digital asset management system is configured and may: a representation of the media content corresponding to the token is generated. At operation 1725, in response to identifying the relationship between the media device and the anchor element at operation 1720, the digital asset management system is configured and may: a representation of the media content is output. For example, in the context of fig. 13, a representation of media content corresponding to a token may include digital asset 1340, virtual object 1345, information 1355 about token 1360 associated with digital asset 1340, one or more customizations 1357, or a combination thereof.

In some examples, outputting the representation of the media content includes causing a display (e.g., output device 1935) to display at least a portion of the media content. In some examples, outputting the representation of the media content includes sending the representation of the media content to the recipient device (e.g., using communication interface 1940). Examples of recipient devices may include any of the examples of media devices listed herein.

In some examples, the digital asset management system is configured and may: a media device pose of the media device is identified based on the sensor data. The digital asset management system may determine a media content pose for the media content based on a media device pose of the media device. In some examples, outputting the representation of the media content includes outputting a representation of the media content that is gestured according to the media content pose. Examples of media content gestures include customization 1357 and/or any other modification, customization, and/or personalization of digital asset 1340.

In some examples, the digital asset management system is configured and may: parameters (e.g., token ownership 620, token intelligence contract 645) that identify the token based on the distributed ledger indicate that the token is associated with the first user. The digital asset management system may determine a visual effect of the media content based on a parameter of the token associated with the first user indicative of the token. The digital asset management system may apply visual effects to the media content. In some examples, outputting the representation of the media content includes outputting the representation of the media content with the applied visual effect. Examples of visual effects include customization 1357 and/or any other modification, customization, and/or personalization of digital asset 1340.

In some examples, the digital asset management system is configured and may: it is determined, based on the data store, that the first user and the second user are associated according to a relationship type. The media device is associated with a second user. The visual effect of the media content may correspond to a relationship type. For example, the visual effect may indicate that the first user and the second user are family, friends, spouse, important others, colleagues, contacts, acquaintances, employers/employees, contractors/invitees, instructors/operators, girlfriend/men friends, buddies, or another relationship type.

In some examples, the digital asset management system is configured and may: a media device is determined to be associated with a first user. The visual effect of the media content corresponds to the first user. For example, the visual effect may indicate to the first user that the media content is the first user's own media content and/or is associated with the first user's own token.

In some examples, the digital asset management system is configured and may: a determination is made that the first user is a celebrity based on the data store. The visual effect of the media content corresponds to the first user being a celebrity. In some examples, different classes of celebrities may have different visual effects, for example to distinguish politicians, sports stars, musicians, movie stars, television stars, famous scientists, and the like.

In some examples, the digital asset management system is configured and may: a rating associated with the media content is determined based on the data store. The visual effect of the media content may correspond to a rating. The rating may be a selected number relative to the maximum possible number. For example, the rating may be 9 of 3, or 10, out of 5, or some other rating. Different ratings may have different visual effects. In some examples, the maximum rating (e.g., 5 of 5, 10 of 10, etc.) may have a specified visual effect.

In some examples, the digital asset management system is configured and may: it is determined that the token is identified in the data store. The visual effect of the media content corresponds to the data store. For example, the data store may include records for tokens and/or media content. The record may identify and/or store the visual effect. Examples of data stores include data store 298, data structure 650, and/or data store 1370.

In some examples, the digital asset management system is configured and may: information about the token is retrieved from the distributed ledger and output. Examples of information about tokens include information 1355 about token 1360. In some examples, outputting the information about the token includes causing a display to display at least a portion of the information, for example, as shown in fig. 13, wherein information 1355 is displayed on media device 1310 using digital asset 1340. In some examples, the information identifies a distributed ledger. In some examples, the digital asset management system is configured and may: parameters (e.g., token ownership 620, token intelligence contract 645) that identify the token based on the distributed ledger indicate that the token is associated with the first user. The information may identify the first user.

For example, in the context of fig. 8A-8B, the digital asset tracking system may set parameters of token 860 to indicate 805. In the context of fig. 9A-9B, the digital asset tracking system may set parameters of the token 960 to indicate that the token is associated with the user 905. In the context of fig. 10A-10B, the digital asset tracking system may set parameters of the token 1060 to indicate that the token is associated with the user 1005. In the context of fig. 11A-11B, the digital asset tracking system may set parameters of the token 1160 to indicate that the token is associated with the user 1105. In the context of fig. 12A-12B, the digital asset tracking system may set parameters of token 1260 to indicate that the token is associated with user 1205. In the context of fig. 13, the digital asset tracking system may set parameters of token 1360 to indicate that the token is associated with user 1305. In the context of fig. 14, the digital asset tracking system may set parameters of the token 1420 to indicate that the token is associated with the first user 1410 and/or the second user 1430. In some examples, parameters of the token may be stored on the chain, such as in token ownership 620, on-chain immutable metadata 625, and/or on-chain mutable metadata 630. In some examples, the parameters of the token may be stored off-chain, such as in off-chain metadata 640.

In some examples, the digital asset management system is configured and may: parameters that identify tokens based on the distributed ledgers (e.g., token smart contracts 645) indicate that the tokens are associated with the smart contracts. The information may identify a smart contract. In some examples, the digital asset management system is configured and may: a parameter (e.g., token number 615) that identifies the token based on the distributed ledger indicates the amount of instances of the token, wherein the information identifies the amount of instances of the token.

In some examples, the digital asset management system is configured and may: a transfer platform configured for token transfer (e.g., configured for tokens to be purchased, sold, leased, licensed, or some combination thereof) is identified. The digital asset management system may output an interface element (e.g., a button, menu, or another user interface element) corresponding to the media content. The interface element may be configured to initiate transfer of the token (e.g., sales token, purchase token, lease token, and/or license token) using the transfer platform upon interaction with the interface element (e.g., by a user of the digital asset management system through input device 1945).

In some examples, the digital asset management system performing process 1700 may include at least one of a Head Mounted Display (HMD) (e.g., HMD 310), a mobile handheld device (e.g., mobile handheld device 410), a wireless communication device, or a combination thereof.

In some examples, a digital asset management system includes: means for receiving sensor data captured by at least one sensor of a media device; means for identifying a relationship between the media device and an anchor element associated with the token based on the sensor data; identifying a token in a payload of at least one tile of the distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and means for outputting a representation of the media content in response to identifying the relationship between the media device and the anchor element.

In some examples, the means for receiving sensor data includes one or more of image capture and processing system 100, image sensor 130, digital asset tracking system 200, one or more of sensor 210, one or more of gesture sensor 215, one or more of media sensor 220, first camera 330A, second camera 330B, first camera 430A, second camera 430B, third camera 430C, fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, image sensor 1315, location sensor 820, location sensor 920, location sensor 1020, location sensor 1120, location sensor 1220, location sensor 1320, media device 205, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD 310, mobile handset 410, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1310, local device 1130, ownership device 1210, local device 1230, distributed device 1365, distributed device 1370, computing system 15, or a combination thereof.

In some examples, the means for identifying relationships and/or identifying tokens includes digital asset tracking system 200, media device 205, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD 310, mobile handheld device 410, blockchain ledger 500, token 600, data structure 650, DAG ledger 700, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, media device 1310, anchor element 1350, distributed ledger 1365, data store 1370, token device 1405, distributed ledger 1415, token 1420, local device 1435, one or more of the computing systems of fig. 15A, one or more of the computing systems of fig. 15B, computing system 1900, or a combination thereof.

In some examples, means for generating and/or outputting a representation of media content includes digital asset tracking system 200, media device 205, media processor 235, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD 310, display 340, mobile handheld device 410, display 440, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, media device 1310, anchor element 1350, distributed ledger 1365, data store 1370, token device 1405, one or more of the computing systems of fig. 15A, one or more of the computing systems of fig. 15B, computing system 1900, output device 1935, communication interface 1940, or a combination thereof.

Fig. 18 is a flow chart illustrating a process 1800 for token device transfer management. Process 1800 may be performed by a digital asset management system. In some examples, the digital asset management system may include the digital asset tracking system 200 of fig. 2 or a portion thereof. In some examples, the imaging system may include, for example, one or more of image capture and processing system 100, image capture device 105A, image processing device 105B, image processor 150, ISP 154, host processor 152, digital asset tracking system 200, media device 205, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD 310, mobile handheld device 410, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, media device 1310, distributed ledger 1365, data store 1370, token device 1405, one or more of the computing systems of fig. 15A, digital asset management system 165of fig. 15B, digital asset tracking system of executing process 1600, digital asset tracking system of executing process 1900, digital asset management system of executing process 1700, computing system of processor 1910, or a combination thereof.

At operation 1805, the digital asset management system is configured and may: tokens corresponding to media content are identified in a payload of at least one tile of the distributed ledger. Parameters of the tokens in the distributed ledger indicate that the tokens are associated with the first user. Examples of tokens may include token 600, token 860, token 960, token 1060, token 1160, token 1260, token 1360, token 1420, or a combination thereof. Examples of distributed ledgers include distributed ledgers 295, blockchain ledgers 500, DAG ledgers 700, distributed ledgers 1365, distributed ledgers 1415, distributed ledgers corresponding to the intelligent contracts of fig. 15A-15B, or combinations thereof. Examples of blocks include block a 505, block B535, block C565, block 710, block 720, block 730, block 740, block 750, block 760, or a combination thereof. Examples of payloads include a block a payload 530, a block B payload 560, and a block C payload 590. The token may be an irreplaceable token (NFT).

At operation 1810, the digital asset management system is configured and may: devices associated with the token and the media content are identified. The device is associated with a first user. Examples of devices include image capture and processing system 100, image capture device 105A, image processing device 105B, media device 205, HMD 310, mobile handheld device 410, media device 810, media device 910, media device 1010, media device 1110, ownership device 1210, media device 1310, distributed ledger 1365, data store 1370, token device 1405, computing system of fig. 15A-15B, computing system 1900, or a combination thereof. Examples of first users include user 320, user 805, user 905, user 1005, user 1105, user 1205, user 1305, first user 1410, and/or second user 1430.

In some examples, a device is configured to present media content. For example, the device may be configured to display media content, such as digital asset 1425 corresponding to token 1420, as shown with respect to token device 1405.

In some examples, the identifier of the device is stored in a distributed ledger (e.g., distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledger 1365, distributed ledger 1415, distributed ledgers corresponding to the intelligent contracts of fig. 15A-15B, or a combination thereof) and/or a data store (e.g., data store 298, data structure 650, and/or data store 1370), and the identification device is based on the identifier. For example, the number of the cells to be processed,

in some examples, the device includes an interactive element indicating a token, and the identifying token in operation 1805 is based on interactions with the interactive element. In some examples, the interaction includes an optical glyph, and the identifier of the token is optically encoded based on the optical glyph. In some examples, the optical glyph includes one or more QR codes, bar codes, aztec codes, dot codes, data matrices, lens codes, or combinations thereof. Interaction with interactive elements including optical glyphs may include scanning the optical glyphs to optically encode information therein (e.g., uniform Resource Locators (URLs) and/or unification A resource identifier (URI)). The interactive elements may include short-range wireless communication transceivers, such as those used for Near Field Communication (NFC), radio Frequency Identification (RFID),A transceiver of a WLAN, PAN, or some combination thereof. Interaction with the interactive element comprising the short-range wireless communication transceiver may include communicating with the short-range wireless communication transceiver (e.g., transmitting and/or receiving one or more wireless signals to/from the short-range wireless communication transceiver).

In some examples, the digital asset management system is configured and may: image data is received, and the detection device is represented in the image data. In some examples, the digital asset management system may identify the token in operation 1805 based on detecting that the device is represented in the image data. For example, in some examples, the digital asset management system may detect and/or identify devices in the image data based on a comparison to reference image data depicting the devices and/or media content. In some examples, the digital asset management system may detect and/or identify elements on the device, such as an optical glyph, by scanning the optical glyph to decode information (e.g., a Uniform Resource Locator (URL) and/or a Uniform Resource Identifier (URI)) optically encoded therein.

At operation 1815, the digital asset management system is configured and may: the identification device has been relocated to an area associated with the second user. Examples of second users include user 320, user 805, user 905, user 1005, user 1105, user 1205, user 1305, first user 1410, and/or second user 1430. In the illustrative example, the first user of operation 1810 is first user 1410 of fig. 14 and the second user of operation 1815 is second user 1430 of fig. 14. In another illustrative example, the first user of operation 1810 is the second user 1430 of fig. 14 and the second user of operation 1815 is the first user 1410 of fig. 14.

In some examples, identifying that the device has been relocated to an area associated with the second user includes identifying that one or more additional devices located in the area are associated with the second user. For example, other devices (e.g., other token devices, media devices, and/or computing systems) in the area associated with the second user may include information indicating that these devices belong to and/or are associated with the second user. Devices may communicate with these one or more additional devices to obtain this information, and the digital asset management system may identify a relocation based on these communications.

In some examples, identifying that the device has been relocated to an area associated with the second user includes identifying that a Wireless Local Area Network (WLAN) in the area is associated with the second user. For example, the device may include a wireless network transceiver that may search for and/or connect to a WLAN network and may be capable of locating in an area associated with the second user and/or connecting to a WLAN associated with the second user, and the digital asset management system may identify the relocation based on the device detecting and/or connecting to the WLAN.

In some examples, identifying that the device has been relocated to an area associated with the second user includes determining that the location data from at least one location sensor of the device indicates that the device is located in the area, and wherein the area is a geographic area.

In some examples, identifying that the device has been relocated to an area associated with the second user includes determining that the location data from the at least one location sensor of the device indicates that the device is located within a range of the location of the second user, wherein the area associated with the second user is within a range of the location of the second user. For example, the device may include a position sensor (e.g., position sensor 820, position sensor 920, position sensor 1020, position sensor 1120, position sensor 1220, position sensor 1320, or a combination thereof), such as a GNSS positioning receiver. The location sensor of the device may identify a location of the device and the digital asset management system may identify the relocation based on whether the location of the device is within a predetermined geographic area associated with the second user.

In some examples, identifying that the device has been relocated to an area associated with the second user includes identifying that the device has been relocated from a first area associated with the first user. For example, when token device 1405 is repositioned to an area associated with second user 1430, token device 1405 is also repositioned from an area associated with first user 1410. The detection device having been relocated from a first area associated with a first user may be based on any of the types of detection listed above with respect to the detection device having been relocated to an area associated with a second user. For example, the digital asset management system may identify a relocation from the first area based on the device no longer being able to detect and/or connect to a WLAN associated with the first user and/or being in the first area, based on the location sensor of the user indicating a location no longer within a predetermined geographic area associated with the first user, or a combination thereof.

At operation 1820, in response to identifying that the device has been relocated to an area at operation 1815, the digital asset management system is configured and may: such that parameters of the tokens in the distributed ledger (e.g., token ownership 620, token intelligence contract 645) are modified from indicating that the token is associated with a first user to indicating that the token is associated with a second user. For example, the digital asset management system may modify the parameter from an indication token associated with the first user 1410 to an indication token associated with the second user 1430.

In some examples, causing parameters of tokens in the distributed ledger to be modified includes causing a new block to be appended to the distributed ledger. Parameters of tokens in the distributed ledger may be modified based on the payload of the new block. In some examples, causing the new tile to be appended to the distributed ledger includes generating the new tile.

In some examples, the digital asset management system is configured and may: a request is sent to a first user device associated with the first user to modify parameters of a token in the distributed ledger from indicating that the token is associated with the first user to indicating that the token is authorized associated with the second user. The digital asset management system may receive authorization from the first user device. In some examples, the digital asset management system causes the parameter to change in operation 1820 in response to receiving the authorization from the first user device.

In some examples, the digital asset management system is configured and may: a request is sent to a second user device associated with the second user to modify parameters of the tokens in the distributed ledger from indicating that the tokens are associated with the first user to indicating that the tokens are authorized with the second user. The digital asset management system may receive authorization from the second user device. In some examples, the digital asset management system causes the parameter to change in operation 1820 in response to receiving the authorization from the second user device.

In some examples, the digital asset management system is configured and may: intelligent contracts associated with tokens are identified in a distributed ledger. The smart contract indicates that parameters of the token are to be modified in response to the condition. Such that the parameters of the tokens in the distributed ledger will be modified as in operation 1820 may include executing the smart contract in response to the identification condition. The identification condition is based on the identification device having been relocated to an area associated with the second user. Examples of smart contracts include token smart contract 645, the smart contracts of fig. 15A-15B, or a combination thereof. The intelligent contract may be indicated in a distributed ledger. Examples of the conditions include the conditions of fig. 15B.

In some examples, the digital asset management system performing process 1800 may include at least one of a Head Mounted Display (HMD) (e.g., HMD 310), a mobile handheld device (e.g., mobile handheld device 410), a wireless communication device, or a combination thereof.

In some examples, a digital asset management system includes: a unit for: identifying a token corresponding to the media content in a payload of at least one tile of the distributed ledger, wherein a parameter of the token in the distributed ledger indicates that the token is associated with the first user; identifying a device associated with the token and the media content, wherein the device is associated with the first user; identifying that the device has been relocated to an area associated with the second user; a unit for: in response to identifying that the device has been relocated to the area, the parameters of the tokens in the distributed ledger are modified from indicating that the tokens are associated with the first user to indicating that the tokens are associated with the second user.

In some examples, means for identifying the token and/or for causing parameters of the token to be modified include one or more of digital asset tracking system 200, media device 205, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD 310, mobile handset 410, blockchain ledger 500, token 600, data structure 650, DAG ledger 700, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, media device 1310, anchor element 1350, distributed ledger 1365, data store 1370, token device 1405, distributed ledger 1415, token 1420, local device 1435, computing system of fig. 15A, computing system 1900, or a combination thereof.

In some examples, the means for identifying the device and/or for identifying that the device has been relocated to an area associated with the second user includes one or more of digital asset tracking system 200, media device 205, network device 280, local device 270, additional device 297, data store 298, anchor element 299, HMD 310, mobile handheld device 410, blockchain ledger 500, token 600, data structure 650, DAG ledger 700, media device 810, local device 830, media device 910, local device 930, media device 1010, local device 1030, media device 1110, local device 1130, ownership device 1210, local device 1230, media device 1310, anchor element 1350, distributed ledger 1365, data store 1370, token device 1405, distributed ledger 1415, token 1420, local device 1435, computing system of fig. 15A, one or more of the computing systems of fig. 15B 1900, or a combination thereof.

In some examples, the processes described herein (e.g., process 1650 and/or other processes described herein) may be performed by a computing device or apparatus. In some examples, process 1650 may be performed by digital asset tracking system 200 of fig. 2. In some examples, process 1650 may be performed by media device 205, network device 280, local device 270, or a combination thereof. In another example, process 1650 may be performed by a computing device having computing system 1900 shown in fig. 19.

The computing device may include any suitable device, such as a mobile device (e.g., a mobile phone), a desktop computing device, a tablet computing device, a wearable device (e.g., a VR headset, AR glasses, a networked watch or smart watch, or other wearable device), a server computer, an autonomous vehicle or a computing device of an autonomous vehicle, a robotic device, a television, and/or any other computing device having resource capabilities to perform the processes described herein (including process 1600). In some cases, the computing device or apparatus may include various components, such as one or more input devices, one or more output devices, one or more processors, one or more microprocessors, one or more microcomputers, one or more cameras, one or more sensors, and/or other components configured to perform the steps of the processes described herein. In some examples, a computing device may include a display, a network interface configured to transmit and/or receive data, any combination thereof, and/or other components. The network interface may be configured to transmit and/or receive Internet Protocol (IP) based data or other types of data.

Components of the computing device may be implemented in a circuit. For example, a component may include and/or be implemented using electronic circuitry or other electronic hardware, which may include one or more programmable electronic circuits (e.g., microprocessors, graphics Processing Units (GPUs), digital Signal Processors (DSPs), central Processing Units (CPUs), and/or other suitable electronic circuits), and/or may include and/or be implemented using computer software, firmware, or any combination thereof to perform the various operations described herein.

Process 1650 is illustrated as a logic flow diagram whose operations represent a sequence of operations that may be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform particular functions or implement particular data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations may be combined in any order and/or in parallel to implement a process.

Additionally, the process 1650 and/or other processes described herein may be performed under control of one or more computer systems configured with executable instructions, and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) that is commonly executed on one or more processors, may be implemented by hardware, or a combination thereof. As noted above, the code may be stored on a computer-readable or machine-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non-transitory.

Fig. 19 is a diagram illustrating an example of a system for implementing certain aspects of the present technique. In particular, FIG. 19 illustrates an example of a computing system 1900, which computing system 1900 may be any computing device that constitutes, for example, an internal computing system, a remote computing system, a camera, or any component thereof, where the components of the system communicate with each other using a connection 1905. Connection 1905 may be a physical connection using a bus or a direct connection in processor 1910, such as in a chipset architecture. Connection 1905 may also be a virtual connection, a network connection, or a logical connection.

In some embodiments, computing system 1900 is a distributed system where the functionality described in this disclosure may be distributed within a data center, multiple data centers, a peer-to-peer network, or the like. In some embodiments, one or more of the described system components represent many such components, each of which performs some or all of the functions described for the component. In some embodiments, the component may be a physical or virtual device.

The example system 1900 includes at least one processing unit (CPU or processor) 1910 and connections 1905 that couple various system components including a system memory 1915, such as Read Only Memory (ROM) 1920 and Random Access Memory (RAM) 1925, to the processor 1910. The computing system 1900 may include a cache memory 1912, the cache memory 1912 being directly connected to the processor 1910, immediately adjacent to the processor 1910, or integrated as part of the processor 1910.

The processor 1910 may include any general purpose processor and hardware services or software services, such as services 1932, 1934, and 1936 stored in a storage device 1930, configured to control the processor 1910 as well as special purpose processors, wherein software instructions are incorporated into an actual processor design. Processor 1910 may be a substantially fully self-contained computing system containing multiple cores or processors, buses, memory controllers, caches, and the like. The multicore processor may be symmetrical or asymmetrical.

To enable user interaction, computing system 1900 includes an input device 1945 that may represent any number of input mechanisms, such as a microphone for voice, a touch-sensitive screen for gesture or graphical input, a keyboard, a mouse, motion input, voice, and so forth. The computing system 1900 may also include an output device 1935, which may be one or more of several output mechanisms. In some examples, the multi-mode system may enable a user to provide multiple types of input/output to communicate with the computing system 1900. Computing system 1900 may include a communication interface 1940, which communication interface 1940 may generally control and manage user inputs and system outputs. The communication interface may use wired and/or wireless transceivers to perform or facilitate the reception and/or transmission of wired or wireless communications, including transceivers that utilize: audio jack/plug, microphone jack/plug, universal serial bus(USB) port/plug,Port/plug, ethernet port/plug, fiber optic port/plug, proprietary line port/plug, +.>Radio signal transmission, < >>Low power consumption (BLE) wireless signal transmission,Wireless signaling, radio Frequency Identification (RFID) wireless signaling, near Field Communication (NFC) wireless signaling, dedicated Short Range Communication (DSRC) wireless signaling, 802.11Wi-Fi wireless signaling, wireless Local Area Network (WLAN) signaling, visible Light Communication (VLC), worldwide interoperability for microwave access (Wi MAX), infrared (IR) communication wireless signaling, public Switched Telephone Network (PSTN) signaling, integrated Services Digital Network (ISDN) signaling, 3G/4G/5G/LTE cellular data network wireless signaling, ad hoc network signaling, radio wave signaling, microwave signaling, infrared signaling, visible light signaling, ultraviolet light signaling, wireless signaling along the electromagnetic spectrum, or some combination thereof. The communication interface 1940 may also include one or more Global Navigation Satellite System (GNSS) receivers or transceivers to determine a location of the computing system 1900 based on receiving one or more signals from one or more satellites associated with the one or more GNSS systems. GNSS systems include, but are not limited to, the united states based Global Positioning System (GPS), the russian based global navigation satellite system (GLONASS), the chinese based beidou navigation satellite system (BDS), and the european based galileo GNSS. There is no limitation on the operation on any particular hardware arrangement, and thus the basic features herein may be readily replaced with improved hardware or firmware arrangements as they are developed.

The storage device 1930 may be a nonvolatile and/or non-transitory and/or computer-readable memory device, and may be a hard disk or other type of computer-readable media that can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, magnetic cassettes, floppy disks, flexible disks, hard disks, magnetic tapes, magnetic stripe/stripe, any other magnetic storage medium, flash memory, memristor memory, any other solid state memory, compact disk read-only memory (CD-ROM) optical disks, compact disk rewriteable Compact Disks (CD) optical disks, digital Video Disk (DVD) optical disks, blu-ray disk (BDD) optical disks, holographic optical disks, another optical medium, secure Digital (SD) cards, micro-all-digital (micro SD) cards, memory stick cards, smart card chips, EMV chips, subscriber Identity Module (SIM) cards, mini/micro/nano/pico cards, another Integrated Circuit (IC) chip/card, random Access Memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable memory (programmable ROM), erasable programmable memory (ROM), programmable ROM (ROM), erasable programmable ROM (62), electrically Erasable Programmable ROM (EEPROM) flash ROM 2 read-only memory (ROM) flash ROM 2, flash ROM 2 read-ROM 2 (ROM) flash ROM 2 read-ROM 2 (RAM) Spin transfer torque RAM (STT-RAM), another memory chip or cartridge, and/or combinations thereof.

Storage device 1930 may include software services, servers, services, etc., the code defining such software, when executed by processor 1910, causes the system to perform functions. In some embodiments, a hardware service performing a particular function may include software components stored in a computer-readable medium in connection with the necessary hardware components (e.g., processor 1910, connection 1905, output device 1935, etc.) to perform the function.

As used herein, the term "computer-readable medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instruction(s) and/or data. Computer-readable media may include non-transitory media in which data may be stored and which do not include carrier waves and/or transitory electronic signals propagating wirelessly or through a wired connection. Examples of non-transitory media may include, but are not limited to, magnetic disks or tapes, optical storage media such as Compact Discs (CDs) or Digital Versatile Discs (DVDs), flash memory, or memory devices. The computer-readable medium may have code and/or machine-executable instructions stored thereon, which may represent procedures, functions, subroutines, programs, routines, subroutines, modules, software packages, classes, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.

In some embodiments, the computer readable storage devices, media, and memory may comprise a cable or wireless signal comprising a bit stream or the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals themselves.

In the above description, specific details are provided to provide a thorough understanding of the embodiments and examples provided herein. However, it will be understood by those of ordinary skill in the art that the embodiments may be practiced without these specific details. For clarity of explanation, in some cases, the present technology may be presented as including individual functional blocks, including functional blocks that include steps or routines in a device, device component, method, embodied in software or a combination of hardware and software. Additional components other than those shown in the figures and/or described herein may be used. For example, circuits, systems, networks, processes, and other components may be shown in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

Various embodiments may be described above as a process or method, which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. Further, the order of operations may be rearranged. The process terminates when its operation is completed, but may have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function or the main function.

The processes and methods according to the examples above may be implemented using computer-executable instructions that may be stored or otherwise available from a computer-readable medium. Such instructions may include, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or processing device to perform a certain function or group of functions. Portions of the computer resources used may be accessible over a network. The computer-executable instructions may be, for example, binary files, intermediate format instructions, such as assembly language, firmware, source code, and the like. Examples of computer readable media that may be used to store instructions, information used, and/or information created during a method according to the described examples include magnetic or optical disks, flash memory, USB devices equipped with non-volatile memory, networked storage devices, and the like.

Devices implementing processes and methods according to these disclosures may include hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof, and may take any of a variety of form factors. When implemented in software, firmware, middleware or microcode, the program code or code segments (e.g., a computer program product) to perform the necessary tasks may be stored in a computer-readable or machine-readable medium. The processor may perform the necessary tasks. Typical examples of form factors include laptop computers, smart phones, mobile phones, tablet devices, or other small form factor personal computers, personal digital assistants, rack-mounted devices, stand alone devices, and the like. The functionality described herein may also be embodied in a peripheral device or add-in card. As a further example, such functionality may also be implemented on circuit boards between different chips or different processes executing in a single device.

The instructions, the medium for transmitting such instructions, the computing resources for executing these instructions, and other structures for supporting such computing resources are example units for providing the functionality described in this disclosure.

In the foregoing description, aspects of the present application have been described with reference to specific embodiments thereof, but those skilled in the art will recognize that the present application is not so limited. Thus, although illustrative embodiments of the present application have been described in detail herein, it should be understood that the inventive concepts may be otherwise variously embodied and employed, and the appended claims are intended to be construed to include such variations, except as limited by the prior art. The various features and aspects of the above-described applications may be used singly or in combination. Furthermore, embodiments may be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. For purposes of illustration, the methods are described in a particular order. It should be understood that in alternative embodiments, the methods may be performed in an order different than that described.

Those of ordinary skill in the art will understand that less ("<") and greater (">) symbols or terms used herein may be replaced with less than or equal to (" +") and greater than or equal to (" +") symbols, respectively, without departing from the scope of the present description.

Where a component is described as "configured to" perform a certain operation, such configuration may be implemented, for example, by designing electronic circuitry or other hardware to perform the operation, by programming programmable electronic circuitry (e.g., a microprocessor or other suitable electronic circuitry) to perform the operation, or any combination thereof.

The phrase "coupled to" refers to any component that is physically connected, directly or indirectly, to another component, and/or that is in communication, directly or indirectly, with another component (e.g., connected to another component through a wired or wireless connection and/or other suitable communication interface).

Claim language reciting "at least one of a collection" and/or "one or more of a collection" or other language indicates that a member of a collection or members of a collection (in any combination) satisfy the claims. For example, claim language reciting "at least one of a and B" means A, B or a and B. In another example, claim language reciting "at least one of A, B and C" means A, B, C or a and B, or a and C, or B and C, or a and B and C. The language "at least one of a collection" and/or "one or more of a collection" does not limit the collection to items listed in the collection. For example, claim language stating "at least one of a and B" may mean A, B or a and B, and may additionally include items not listed in the set of a and B.

The various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, firmware, or combinations thereof. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The techniques described herein may also be implemented in electronic hardware, computer software, firmware, or any combination thereof. Such techniques may be implemented in any of various devices such as a general purpose computer, a wireless communication device handset, or an integrated circuit device having multiple uses including applications in wireless communication device handsets and other devices. Any features described as modules or components may be implemented together in an integrated logic device or separately as discrete but interoperable logic devices. If implemented in software, the techniques may be realized at least in part by a computer-readable data storage medium comprising program code including instructions that, when executed, perform one or more of the methods described above. The computer readable data storage medium may form part of a computer program product, which may include packaging material. The computer-readable medium may include memory or data storage media such as Random Access Memory (RAM), such as Synchronous Dynamic Random Access Memory (SDRAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic or optical data storage media, and the like. Additionally or alternatively, the techniques may be realized at least in part by a computer-readable communication medium that carries or communicates program code in the form of instructions or data structures and that can be accessed, read, and/or executed by a computer, such as a propagated signal or wave.

The program code may be executed by a processor, which may include one or more processors, such as one or more Digital Signal Processors (DSPs), general purpose microprocessors, application Specific Integrated Circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Such a processor may be configured to perform any of the techniques described in this disclosure. A general purpose processor may be a microprocessor; but, in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Thus, the term "processor" as used herein may refer to any one of the foregoing structures, any combination of the foregoing structures, or any other structure or device suitable for implementation of the techniques described herein. Additionally, in some aspects, the functionality described herein may be provided within dedicated software modules or hardware modules configured for encoding and decoding, or incorporated in a combined video encoder-decoder (CODEC).

Illustrative aspects of the present disclosure include:

aspect 1A. An apparatus for token generation, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor configured to: receiving media content based on sensor data captured by at least one sensor of a media device; determining a location of the media device; determining that the location of the media device is within a geographic region; and in response to determining that the location of the media device is within the geographic region, generating a token corresponding to the media content, wherein a payload of at least one tile of a distributed ledger identifies the token.

Aspect 2A. The apparatus of aspect 1A, wherein the media content comprises at least a portion of the sensor data.

Aspect 3A. The apparatus of any of aspects 1A-2A, wherein the media content comprises a modified variant of at least a portion of the sensor data.

Aspect 4A. The apparatus of any of claims 1A-3A, wherein the sensor data comprises at least one image captured by at least one image sensor of the at least one sensor of the media device, and wherein the media content is based on at least one of the at least one image.

Aspect 5A. The apparatus of any of aspects 1A-4A, wherein to determine the location of the media device, the at least one processor is configured to: at least a portion of an environment in the at least one image is detected, and the location of the media device is determined based at least in part on the detection of at least the portion of the environment in the at least one image.

Aspect 6A. The apparatus of any of aspects 1A-5A, wherein to determine that the location of the media device is within the geographic area, the at least one processor is configured to: at least a portion of an environment in the at least one image is detected and it is determined that at least the portion of the environment is located within the geographic area.

Aspect 7A. The apparatus of any one of aspects 1A-6A, wherein the at least one processor is configured to: detecting at least a portion of an individual in the at least one image; determining the identity of the individual; and setting a parameter of the token to indicate that the token is associated with the identity.

Aspect 8A. The apparatus of any of aspects 1A-7A, wherein the sensor data comprises positioning data based on receipt of at least one wireless signal by the at least one sensor, wherein to determine the location of the media device, the at least one processor is configured to: the location of the media device is determined based at least in part on the positioning data.

Aspect 9A. The apparatus of any one of aspects 1A-8A, wherein the at least one wireless signal comprises a short range wireless signal from a local device that is within a transmission range of the media device at least during reception of the at least one wireless signal by the at least one sensor.

Aspect 10A. The apparatus of any one of aspects 1A-9A, wherein the at least one wireless signal comprises a Global Navigation Satellite System (GNSS) signal from a GNSS satellite.

Aspect 11A. The apparatus of any of aspects 1A-10A, wherein the media content comprises a map of the geographic area.

Aspect 12A. The apparatus of any of aspects 1A-11A, wherein to determine that the location of the media device is within the geographic area, the at least one processor is configured to: the location of the media device is determined to be within the geographic area based on at least one communication between the media device and a local device associated with the geographic area.

Aspect 13A. The apparatus of any one of aspects 1A-12A, wherein the apparatus comprises the local device.

Aspect 14A. The apparatus of any one of aspects 1A-13A, wherein the apparatus comprises the media device.

Aspect 15A. The apparatus of any one of aspects 1A-14A, wherein the apparatus is in the geographic region.

Aspect 16A. The apparatus of any one of aspects 1A-15A, wherein the at least one processor is configured to: generating the at least one tile in response to determining that the location of the media device is within the geographic area; and causing the at least one tile to be attached to the distributed ledger.

Aspect 17A. The apparatus of any of aspects 1A-16A, wherein the at least one tile comprises a hash of at least a portion of a previous tile of the distributed ledger.

Aspect 18A. The apparatus of any one of aspects 1A-17A, wherein the at least one processor is configured to: in response to determining that the location of the media device is within the geographic area, the distributed ledger is generated.

Aspect 19A. The apparatus of any one of aspects 1A-18A, wherein the at least one processor is configured to: in response to determining that the location of the media device is within the geographic region, sending a request to a computing device to generate the at least one tile; receiving the at least one block; and attaching the at least one tile to the distributed ledger.

Aspect 20A. The apparatus of any one of aspects 1A-19A, wherein the at least one processor is configured to: parameters of the token are set to indicate that the token is associated with a user with whom the media device is associated.

Aspect 21A. The apparatus of any one of aspects 1A-20A, wherein the at least one processor is configured to: based on the sensor data, determining that the geographic area includes at least a threshold number of people, wherein the at least one processor is configured to: in response to determining that the geographic area includes at least the threshold number of people, the token corresponding to the media content is generated.

Aspect 22A. The device of any of aspects 1A-21A, wherein the apparatus comprises at least one of a Head Mounted Display (HMD), a mobile handheld device, or a wireless communication device.

Aspect 23A. A method of token generation, the method comprising: receiving media content based on sensor data captured by at least one sensor of a media device; determining a location of the media device; determining that the location of the media device is within a geographic region; and in response to determining that the location of the media device is within the geographic region, generating a token corresponding to the media content, wherein a payload of at least one tile of a distributed ledger identifies the token.

Aspect 24A. The method of aspect 23A, wherein the media content comprises at least a portion of the sensor data.

Aspect 25A. The method of any of aspects 23A-24A, wherein the media content comprises a modified variant of at least a portion of the sensor data.

Aspect 26A. The method of any of claims 23A-25A, wherein the sensor data includes at least one image captured by at least one image sensor of the at least one sensor of the media device, and wherein the media content is based on at least one of the at least one image.

Aspect 27A. The method of any of claims 23A-26A, wherein determining the location of the media device comprises: detecting at least a portion of an environment in the at least one image; and determining the location of the media device based at least in part on the detection of at least the portion of the environment in the at least one image.

Aspect 28A. The method of any of claims 23A-27A, wherein determining that the location of the media device is within the geographic area comprises: at least a portion of an environment in the at least one image is detected, and it is determined that at least the portion of the environment is located within the geographic area.

Aspect 29A. The method of any one of aspects 23A to 28A, further comprising: detecting at least a portion of an individual in the at least one image; determining the identity of the individual; and setting a parameter of the token to indicate that the token is associated with the identity.

Aspect 30A. The method of any of claims 23A-29A, wherein the sensor data comprises positioning data based on receipt of at least one wireless signal by the at least one sensor, and wherein determining the location of the media device comprises determining the location of the media device based at least in part on the positioning data.

Aspect 31A. The method of any of claims 23A-30A, wherein the at least one wireless signal comprises a short range wireless signal from a local device that is within a transmission range of the media device at least during receipt of the at least one wireless signal by the at least one sensor.

Aspect 32A. The method of any one of aspects 23A-31A, wherein the at least one wireless signal comprises a Global Navigation Satellite System (GNSS) signal from a GNSS satellite.

Aspect 33A. The method of any of aspects 23A-32A, wherein the media content comprises a map of the geographic area.

Aspect 34A. The method of any of claims 23A-33A, wherein determining that the location of the media device is within the geographic area comprises: the location of the media device is determined to be within the geographic area based on at least one communication between the media device and a local device associated with the geographic area.

Aspect 35A. The method of any one of aspects 23A-34A, wherein the method is performed using an apparatus comprising the local device.

Aspect 36A. The method of any of claims 23A-35A, wherein the method is performed using an apparatus comprising the media device.

Aspect 37A. The method of any one of aspects 23A-36A, wherein the method is performed using a device in the geographic area.

Aspect 38A. The method of any one of aspects 23A to 37A, further comprising: generating the at least one tile in response to determining that the location of the media device is within the geographic area; and causing the at least one tile to be attached to the distributed ledger.

Aspect 39A. The method of any of aspects 23A-38A, wherein the at least one tile includes a hash of at least a portion of a previous tile of the distributed ledger.

Aspect 40A. The method of any one of aspects 23A-39A, further comprising: in response to determining that the location of the media device is within the geographic area, the distributed ledger is generated.

Aspect 41A. The method of any one of aspects 23A to 40A, further comprising: in response to determining that the location of the media device is within the geographic region, sending a request to a computing device to generate the at least one tile; receiving the at least one block; and attaching the at least one tile to the distributed ledger.

Aspect 42A. The method of any one of aspects 23A to 41A, further comprising: parameters of the token are set to indicate that the token is associated with a user with whom the media device is associated.

Aspect 43A. The method of any one of aspects 23A-42A, further comprising: determining that the geographic area includes at least a threshold amount of people, wherein generating the token corresponding to the media content is performed in response to determining that the geographic area includes at least the threshold amount of people.

Aspect 44A. The method of any of aspects 23A-43A, wherein the method is performed using an apparatus comprising at least one of a Head Mounted Display (HMD), a mobile handheld device, or a wireless communication device.

Aspect 45A. A non-transitory computer-readable medium having instructions stored thereon, which when executed by one or more processors, cause the one or more processors to: receiving media content based on sensor data captured by at least one sensor of a media device; determining a location of the media device; determining that the location of the media device is within a geographic region; and in response to determining that the location of the media device is within the geographic region, generating a token corresponding to the media content, wherein a payload of at least one tile of a distributed ledger identifies the token.

Aspect 46A. The non-transitory computer-readable medium of aspect 45A, further comprising: the operations of any one of aspects 2A to 22A and/or any one of aspects 24A to 44A.

Aspect 47A. An apparatus for token generation, the apparatus comprising: means for receiving media content based on sensor data captured by at least one sensor of a media device; means for determining a location of the media device; means for determining that the location of the media device is within a geographic region; and means for generating a token corresponding to the media content in response to determining that the location of the media device is within the geographic area, wherein a payload of at least one tile of a distributed ledger identifies the token.

Aspect 48A. The apparatus of aspect 47A, further comprising means for performing the operations of any one of aspects 2A to 22A and/or any one of aspects 24A to 44A.

Aspect 1B. An apparatus for context token associated media output, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor configured to: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

Aspect 2B. The apparatus of aspect 1B, wherein the sensor data comprises image data captured by at least one image sensor of the at least one sensor of the media device, wherein the anchor element comprises an object, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify the image data to depict the object.

Aspect 3B. The apparatus of any of aspects 1B-2B, wherein the object comprises an optical glyph, wherein information indicative of the token is optically encoded based on the optical glyph.

Aspect 4B. The apparatus of any of aspects 1B-3B, wherein reference image data depicting the object is stored in a data store, and wherein to identify the image data depicting the object, the at least one processor is configured to compare the image data with the reference image data.

Aspect 5B. The apparatus of any of aspects 1B-4B, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a region, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify that the location of the media device is within the region.

Aspect 6B. The apparatus of any of aspects 1B-5B, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a place, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify that the location of the media device is within a threshold range of the place.

Aspect 7B. The apparatus of any of aspects 1B-6B, the sensor data comprising audio data captured by at least one microphone of the at least one sensor of the media device, wherein the anchor element comprises sound, and wherein to identify a relationship between the media device and the anchor element, the at least one processor is configured to identify that the audio data comprises the sound.

Aspect 8B. The apparatus of any of aspects 1B-7B, wherein to output the representation of the media content, the at least one processor is configured to cause a display to display at least a portion of the media content.

Aspect 9B. The apparatus of any one of aspects 1B-8B, wherein the at least one processor is configured to: identifying a media device pose of the media device based on the sensor data; and determining a media content pose for the media content based on the media device pose of the media device, wherein to cause the display to display at least the portion of the media content, the at least one processor is configured to: the representation of the media content that is gestured according to the media content pose is output.

Aspect 10B. The apparatus of any one of aspects 1B-9, wherein the at least one processor is configured to: identifying, based on the distributed ledger, that a parameter of the token indicates that the token is associated with a first user; determining a visual effect for the media content based on a parameter of the token indicating that the token is associated with the first user; and applying the visual effect to the media content, wherein to output the representation of the media content, the at least one processor is configured to output the representation of the media content with the visual effect applied.

Aspect 11B. The apparatus of any one of aspects 1B-10B, wherein the at least one processor is configured to: determining that the first user and second user are associated according to a relationship type based on a data store, wherein the media device is associated with the second user, and wherein the visual effect for the media content corresponds to the relationship type.

Aspect 12B. The apparatus of any one of aspects 1B-11B, wherein the at least one processor is configured to: determining that the media device is associated with the first user, and wherein the visual effect for the media content corresponds to the first user.

Aspect 13B. The apparatus of any one of aspects 1B-12B, wherein the at least one processor is configured to: the method further includes determining that the first user is a celebrity based on a data store, and wherein the visual effect for the media content corresponds to the first user being the celebrity.

Aspect 14B. The apparatus of any one of aspects 1B-13B, wherein the at least one processor is configured to: a rating associated with the media content is determined based on a data store, and wherein the visual effect for the media content corresponds to the rating.

Aspect 15B. The apparatus of any one of aspects 1B-14B, wherein the at least one processor is configured to: determining that the token is identified in a data store, and wherein the visual effect for the media content corresponds to the data store.

Aspect 16B. The apparatus of any one of aspects 1B-15B, wherein the at least one processor is configured to: retrieving information about the token from the distributed ledger; and outputting the information about the token.

Aspect 17B. The apparatus of any of aspects 1B-16B, wherein to output the information about the token, the at least one processor is configured to cause a display to display at least a portion of the information.

Aspect 18B. The apparatus of any one of aspects 1B-17B, wherein the at least one processor is configured to: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a first user, wherein the information identifies the first user.

Aspect 19B. The apparatus of any of aspects 1B-18B, wherein the information identifies the distributed ledger.

Aspect 20B. The apparatus of any one of aspects 1B-19B, wherein the at least one processor is configured to: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a smart contract, wherein the information identifies the smart contract.

Aspect 21B. The apparatus of any one of aspects 1B-20B, wherein the at least one processor is configured to: a parameter identifying the token based on the distributed ledger indicates a number of instances of the token, wherein the information identifies the number of instances of the token.

Aspect 22B. The apparatus of any one of aspects 1B-21B, wherein the at least one processor is configured to: identifying a transfer platform configured for token transfer; and outputting an interface element corresponding to the media content, wherein the interface element is configured to initiate transfer of the token using the transfer platform upon interaction with the interface element.

Aspect 23B. The device of any of aspects 1B-22B, wherein the apparatus comprises at least one of a Head Mounted Display (HMD), a mobile handheld device, or a wireless communication device.

Aspect 24B. A method of context token associated media output, the method comprising: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

Aspect 25B. The method of claim 24B, wherein the sensor data comprises image data captured by at least one image sensor of the at least one sensor of the media device, wherein the anchor element comprises an object, and wherein identifying the relationship between the media device and the anchor element comprises: the image data is identified to depict the object.

Aspect 26B. The method of any of claims 24B-25B, wherein the object comprises an optical glyph, wherein the information indicative of the token is optically encoded based on the optical glyph.

Aspect 27B. The method of any of claims 24B-26B, wherein reference image data depicting the object is stored in a data store, and wherein identifying that the image data depicts the object comprises comparing the image data to the reference image data.

Aspect 28B. The method of any of claims 24B-27B, wherein the sensor data includes location data indicating a location of the media device, wherein the anchor element includes a region, and wherein identifying the relationship between the media device and the anchor element includes: the location of the media device is identified as being within the region.

Aspect 29B. The method of any of claims 24B-28B, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a place, and wherein identifying the relationship between the media device and the anchor element comprises identifying that the location of the media device is within a threshold range of the place.

Aspect 30B. The method of any of claims 24B-29B, the sensor data comprising audio data captured by at least one microphone of the at least one sensor of the media device, wherein the anchor element comprises sound, and wherein identifying the relationship between the media device and the anchor element comprises: identifying that the audio data includes the sound.

Aspect 31B. The method of any of claims 24B-30B, wherein outputting the representation of the media content includes causing a display to display at least a portion of the media content.

Aspect 32B. The method of any one of aspects 24B to 31B, further comprising: identifying a media device pose of the media device based on the sensor data; and determining a media content pose for the media content based on the media device pose of the media device, wherein outputting the representation of the media content comprises: outputting the representation of the media content that is gestured according to the media content pose.

Aspect 33B. The method of any one of aspects 24B-32B, further comprising: identifying, based on the distributed ledger, that a parameter of the token indicates that the token is associated with a first user; determining a visual effect for the media content based on a parameter of the token indicating that the token is associated with the first user; and applying the visual effect to the media content, wherein outputting the representation of the media content comprises: outputting the representation of the media content with the visual effect applied.

Aspect 34B. The method of any one of aspects 24B-33B, further comprising: determining that the first user and second user are associated according to a relationship type based on a data store, wherein the media device is associated with the second user, and wherein the visual effect for the media content corresponds to the relationship type.

Aspect 35B. The method of any one of aspects 24B-34B, further comprising: determining that the media device is associated with the first user, and wherein the visual effect for the media content corresponds to the first user.

Aspect 36B. The method of any one of aspects 24B-35B, further comprising: the method further includes determining that the first user is a celebrity based on a data store, and wherein the visual effect for the media content corresponds to the first user being the celebrity.

Aspect 37B. The method of any one of aspects 24B-36B, further comprising: a rating associated with the media content is determined based on a data store, and wherein the visual effect for the media content corresponds to the rating.

Aspect 38B. The method of any one of aspects 24B-37B, further comprising: determining that the token is identified in a data store, and wherein the visual effect for the media content corresponds to the data store.

Aspect 39B. The method of any one of aspects 24B-38B, further comprising: retrieving information about the token from the distributed ledger; and outputting the information about the token.

Aspect 40B. The method of any of aspects 24B-39B, wherein outputting the information about the token comprises causing a display to display at least a portion of the information.

Aspect 41B. The method of any one of aspects 24B to 40B, further comprising: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a first user, wherein the information identifies the first user.

Aspect 42B. The method of any of aspects 24B-41B, wherein the information identifies the distributed ledger.

Aspect 43B. The method of any one of aspects 24B-42B, further comprising: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a smart contract, wherein the information identifies the smart contract.

Aspect 44B. The method of any one of aspects 24B-43B, further comprising: a parameter identifying the token based on the distributed ledger indicates a number of instances of the token, wherein the information identifies the number of instances of the token.

Aspect 45B. The method of any one of aspects 24B-44B, further comprising: identifying a transfer platform configured for token transfer; and outputting an interface element corresponding to the media content, wherein the interface element is configured to initiate transfer of the token using the transfer platform upon interaction with the interface element.

Aspect 46B. The method of any of aspects 24B-45B, wherein the method is performed using an apparatus comprising at least one of a Head Mounted Display (HMD), a mobile handheld device, or a wireless communication device.

Aspect 47B. A non-transitory computer-readable medium having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

Aspect 48B. The non-transitory computer-readable medium of aspect 47B, further comprising the operations of any one of aspects 2B to 24B and/or any one of aspects 25B to 46A.

Aspect 49B. An apparatus for context token associated media output, the apparatus comprising: means for receiving sensor data captured by at least one sensor of a media device; means for identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; means for generating a representation of the media content corresponding to the token; and means for outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

Aspect 50B. The apparatus according to aspect 49B, further comprising means for performing the operations according to any one of aspects 2B to 24B and/or any one of aspects 25B to 46A.

Aspect 1C. An apparatus for context token associated media output, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory, the at least one processor configured to: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

Aspect 2C. The apparatus of aspect 1C, wherein the sensor data comprises image data captured by at least one image sensor of the at least one sensor of the media device, wherein the anchor element comprises an object, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify the image data to depict the object.

Aspect 3C. The apparatus of any of aspects 1C-2C, wherein the object comprises an optical glyph, wherein the information indicative of the token is optically encoded based on the optical glyph.

Aspect 4C. The apparatus of any of aspects 1C-3C, wherein reference image data depicting the object is stored in a data store, and wherein to identify the image data depicting the object, the at least one processor is configured to compare the image data with the reference image data.

Aspect 5C. The apparatus of any of aspects 1C-4C, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a region, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify that the location of the media device is within the region.

Aspect 6C. The apparatus of any of aspects 1C-5C, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a place, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify that the location of the media device is within a threshold range of the place.

Aspect 7C. The apparatus of any of aspects 1C-6C, the sensor data comprising audio data captured by at least one microphone of the at least one sensor of the media device, wherein the anchor element comprises sound, and wherein to identify a relationship between the media device and the anchor element, the at least one processor is configured to identify that the audio data comprises the sound.

Aspect 8C. The apparatus of any of aspects 1C-7C, wherein to output the representation of the media content, the at least one processor is configured to cause a display to display at least a portion of the media content.

Aspect 9C. The apparatus of any one of aspects 1C-8C, wherein the at least one processor is configured to: identifying a media device pose of the media device based on the sensor data; and determining a media content pose for the media content based on the media device pose of the media device, wherein to cause the display to display at least the portion of the media content, the at least one processor is configured to: outputting the representation of the media content that is gestured according to the media content pose.

Aspect 10C. The apparatus of any one of aspects 1C-9C, wherein the at least one processor is configured to: identifying, based on the distributed ledger, that a parameter of the token indicates that the token is associated with a first user; determining a visual effect for the media content based on a parameter of the token indicating that the token is associated with the first user; and applying the visual effect to the media content, wherein to output the representation of the media content, the at least one processor is configured to output the representation of the media content with the visual effect applied.

Aspect 11C. The apparatus of any one of aspects 1C-10C, wherein the at least one processor is configured to: determining that the first user and second user are associated according to a relationship type based on a data store, wherein the media device is associated with the second user, and wherein the visual effect for the media content corresponds to the relationship type.

Aspect 12C. The apparatus of any one of aspects 1C-11C, wherein the at least one processor is configured to: determining that the media device is associated with the first user, and wherein the visual effect for the media content corresponds to the first user.

Aspect 13C. The apparatus of any one of aspects 1C-12C, wherein the at least one processor is configured to: the method further includes determining that the first user is a celebrity based on a data store, and wherein the visual effect for the media content corresponds to the first user being the celebrity.

Aspect 14C. The apparatus of any one of aspects 1C-13C, wherein the at least one processor is configured to: a rating associated with the media content is determined based on a data store, and wherein the visual effect for the media content corresponds to the rating.

Aspect 15C. The apparatus of any one of aspects 1C-14C, wherein the at least one processor is configured to: determining that the token is identified in a data store, and wherein the visual effect for the media content corresponds to the data store.

Aspect 16C. The apparatus of any one of aspects 1C-15C, wherein the at least one processor is configured to: retrieving information about the token from the distributed ledger; and outputting the information about the token.

Aspect 17C. The apparatus of any of aspects 1C-16C, wherein to output the information about the token, the at least one processor is configured to cause a display to display at least a portion of the information.

Aspect 18C. The apparatus of any one of aspects 1C-17C, wherein the at least one processor is configured to: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a first user, wherein the information identifies the first user.

Aspect 19C. The apparatus of any of aspects 1C-18C, wherein the information identifies the distributed ledger.

Aspect 20C. The apparatus of any one of aspects 1C-19C, wherein the at least one processor is configured to: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a smart contract, wherein the information identifies the smart contract.

Aspect 21C. The apparatus of any one of aspects 1C-20C, wherein the at least one processor is configured to: a parameter identifying the token based on the distributed ledger indicates a number of instances of the token, wherein the information identifies the number of instances of the token.

Aspect 22C. The apparatus of any one of aspects 1C-21C, wherein the at least one processor is configured to: identifying a transfer platform configured for token transfer; and outputting an interface element corresponding to the media content, wherein the interface element is configured to initiate transfer of the token using the transfer platform upon interaction with the interface element.

Aspect 23C. The apparatus of any one of aspects 1C-22C, wherein the apparatus comprises at least one of a Head Mounted Display (HMD), a mobile handheld device, or a wireless communication device.

Aspect 24C. A method of context token associated media output, the method comprising: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

Aspect 25C. The method of claim 24C, wherein the sensor data comprises image data captured by at least one image sensor of the at least one sensor of the media device, wherein the anchor element comprises an object, and wherein identifying the relationship between the media device and the anchor element comprises: the image data is identified to depict the object.

Aspect 26C. The method of any of claims 24C-25C, wherein the object comprises an optical glyph, wherein the information indicative of the token is optically encoded based on the optical glyph.

Aspect 27C. The method of any of claims 24C-26C, wherein reference image data depicting the object is stored in a data store, and wherein identifying that the image data depicts the object comprises comparing the image data to the reference image data.

Aspect 28C. The method of any of claims 24C-27C, wherein the sensor data includes location data indicating a location of the media device, wherein the anchor element includes a region, and wherein identifying the relationship between the media device and the anchor element includes: the location of the media device is identified as being within the region.

Aspect 29C. The method of any of claims 24C-28C, wherein the sensor data includes location data indicating a location of the media device, wherein the anchor element includes a place, and wherein identifying the relationship between the media device and the anchor element includes: the location of the media device is identified as being within a threshold range of the location.

Aspect 30C. The method of any of claims 24C-29C, the sensor data comprising audio data captured by at least one microphone of the at least one sensor of the media device, wherein the anchor element comprises sound, and wherein identifying the relationship between the media device and the anchor element comprises: identifying that the audio data includes the sound.

Aspect 31C. The method of any of claims 24C-30C, wherein outputting the representation of the media content includes causing a display to display at least a portion of the media content.

Aspect 32C. The method of any one of aspects 24C-31C, further comprising: identifying a media device pose of the media device based on the sensor data; and determining a media content pose for the media content based on the media device pose of the media device, wherein outputting the representation of the media content comprises: outputting the representation of the media content that is gestured according to the media content pose.

Aspect 33C. The method of any one of aspects 24C-32C, further comprising: based on the distributed ledger, identifying that a parameter of the token indicates that the token is associated with a first user; determining a visual effect for the media content based on a parameter of the token indicating that the token is associated with the first user; and applying the visual effect to the media content, wherein outputting the representation of the media content comprises: outputting the representation of the media content with the visual effect applied.

Aspect 34C. The method of any one of aspects 24C-33C, further comprising: determining that the first user and second user are associated according to a relationship type based on a data store, wherein the media device is associated with the second user, and wherein the visual effect for the media content corresponds to the relationship type.

Aspect 35C. The method of any one of aspects 24C-34C, further comprising: determining that the media device is associated with the first user, and wherein the visual effect for the media content corresponds to the first user.

Aspect 36C. The method of any one of aspects 24C-35C, further comprising: the method further includes determining that the first user is a celebrity based on a data store, and wherein the visual effect for the media content corresponds to the first user being the celebrity.

Aspect 37C. The method of any one of aspects 24C-36C, further comprising: a rating associated with the media content is determined based on a data store, and wherein the visual effect for the media content corresponds to the rating.

Aspect 38C. The method of any one of aspects 24C-37C, further comprising: determining that the token is identified in a data store, and wherein the visual effect for the media content corresponds to the data store.

Aspect 39C. The method of any one of aspects 24C-38C, further comprising: retrieving information about the token from the distributed ledger; and outputting the information about the token.

Aspect 40C. The method of any of aspects 24C-39C, wherein outputting the information about the token comprises causing a display to display at least a portion of the information.

Aspect 41C. The method of any one of aspects 24C-40C, further comprising: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a first user, wherein the information identifies the first user.

Aspect 42C. The method of any of aspects 24C-41C, wherein the information identifies the distributed ledger.

Aspect 43C. The method of any one of aspects 24C-42C, further comprising: a parameter identifying the token based on the distributed ledger indicates that the token is associated with a smart contract, wherein the information identifies the smart contract.

Aspect 44C. The method of any one of aspects 24C-43C, further comprising: a parameter identifying the token based on the distributed ledger indicates a number of instances of the token, wherein the information identifies the number of instances of the token.

Aspect 45C. The method of any one of aspects 24C-44C, further comprising: identifying a transfer platform configured for token transfer; and outputting an interface element corresponding to the media content, wherein the interface element is configured to initiate transfer of the token using the transfer platform upon interaction with the interface element.

Aspect 46C. The method of any of aspects 24C-45C, wherein the method is performed using an apparatus comprising at least one of a Head Mounted Display (HMD), a mobile handheld device, or a wireless communication device.

Aspect 47C. A non-transitory computer-readable medium having instructions stored thereon, which when executed by one or more processors, cause the one or more processors to: receiving sensor data captured by at least one sensor of a media device; identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; generating a representation of the media content corresponding to the token; and outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

Aspect 48C. The non-transitory computer-readable medium of aspect 47C, further comprising the operations of any one of aspects 2C to 23C and/or any one of aspects 25C to 46C.

Aspect 49C. An apparatus for context token associated media output, the apparatus comprising: means for receiving sensor data captured by at least one sensor of a media device; means for identifying a relationship between the media device and an anchor element associated with a token based on the sensor data; identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger; means for generating a representation of the media content corresponding to the token; and means for outputting the representation of the media content in response to identifying the relationship between the media device and the anchor element.

Aspect 50C. The apparatus of aspect 49C, further comprising means for performing the operations of any one of aspects 2C-23C and/or any one of aspects 25C-46C.

Aspect 1D: an apparatus for processing image data, the apparatus comprising: a memory; and one or more processors coupled to the memory, the one or more processors configured to: receiving media data based on sensor data captured by one or more sensors of a media device; receiving positioning data indicative of a location of the media device while the sensor data is captured by the one or more sensors of the media device; based on the positioning data, verifying that the location of the media device is within a geographic area while capturing the sensor data; and in response to verifying that the location of the media device is within the geographic region, automatically generating a token corresponding to the media data, the token identified in a payload of a block of a distributed ledger.

Aspect 2D. The apparatus of aspect 1D, wherein the media data is the sensor data.

Aspect 3D. The apparatus of any of aspects 1D-2D, wherein the media device generates the media data at least in part by modifying the sensor data to add virtual content to the sensor data.

Aspect 4D. The apparatus of any of aspects 1D-3D, wherein the sensor data comprises one or more images captured by one or more image sensors of the one or more sensors of the media device, and wherein the media data is based on at least one of the one or more images.

Aspect 5D. The apparatus of any of aspects 1D-4D, wherein the sensor data comprises the positioning data determined based on receipt of one or more positioning signals by a positioning receiver in the one or more sensors of the media device, and wherein the media data comprises a map generated by the media device based on the positioning data.

Aspect 6D. The apparatus of any of aspects 1D-5D, wherein the sensor data comprises assisted location data determined based on receipt of one or more location signals by a location receiver in the one or more sensors of the media device, and wherein the media data is a map generated by the media device based on the assisted location data.

Aspect 7D. The apparatus of any one of aspects 1D-6D, wherein the one or more processors are configured to: automatically generating the block for the distributed ledger in response to verifying that the location of the media device is within the geographic area; and attaching the tile to a plurality of tiles of the distributed ledger.

Aspect 8D. The apparatus of any of aspects 1D-7D, wherein the chunk includes a hash of at least a portion of a previous chunk of the distributed ledger.

Aspect 9D. The apparatus of any of aspects 1D-8D, wherein the chunk includes a merck root of a plurality of elements of the payload of the chunk, and wherein the token corresponds to at least one element of the plurality of elements of the payload of the chunk.

Aspect 10D. The apparatus of any one of aspects 1D-9D, wherein the one or more processors are configured to: the distributed ledger is automatically generated in response to verifying that the location of the media device is within the geographic area.

Aspect 11D. The apparatus of any one of aspects 1D to 10D, the one or more processors configured to: in response to verifying that the location of the media device is within the geographic region, sending a request to a tile generation computing device to generate the tile for the distributed ledger; receiving the block from the block generation computing device; and attaching the tile to a plurality of tiles of the distributed ledger.

Aspect 12D. The apparatus of any of aspects 1D-11D, wherein to receive the positioning data, the one or more processors are configured to receive the positioning data from the media device, the positioning data based on one or more positioning signals received by a positioning receiver in the one or more sensors of the media device.

Aspect 13D. The apparatus of any one of aspects 1D-12D, wherein to receive the positioning data, the one or more processors are configured to receive the positioning data from a local device different from the media device, the positioning data based on one or more positioning signals received by a positioning receiver of the local device.

Aspect 14D. The apparatus of any of aspects 5D, 6D, 12D, or 13D, wherein the positioning receiver is a short-range wireless communication receiver configured to receive one or more short-range wireless communication signals.

Aspect 15D. The apparatus of aspect 14D, wherein the one or more short-range wireless communication signals are transmitted by a local device in the geographic area, and wherein the geographic area corresponds to a transmission range of the one or more short-range wireless communication signals of the local device.

Aspect 16D. The apparatus of any of aspects 5D, 6D, or 12D-15D, wherein the positioning receiver is a global navigation satellite system receiver configured to receive one or more GNSS signals from one or more satellites.

Aspect 17D. The apparatus of any one of aspects 1D to 16D, wherein the apparatus comprises the local device.

Aspect 18D. The apparatus of any of aspects 12D-17D, wherein to verify that the location of the media device is within the geographic area while the sensor data is captured, the one or more processors are configured to verify content of one or more communications between the media device and a local device associated with the geographic area.

Aspect 19D. The apparatus of any one of aspects 1D-18D, wherein the apparatus comprises the media device.

Aspect 20D. The apparatus of any of aspects 1D-19D, wherein to verify that the location of the media device is within the geographic area while the sensor data is captured, the one or more processors are configured to verify that the sensor data depicts an object visible within the geographic area.

Aspect 21D. The apparatus of any one of aspects 1D-20D, wherein the one or more processors are configured to: ownership of the token is set to an account associated with a user associated with the media device.

Aspect 22D. The apparatus of any one of aspects 1D-21D, wherein the one or more processors are configured to: identifying that the sensor data includes a representation of an individual having an identified identity; and setting ownership of the token to an account associated with the individual having the identified identity.

Aspect 23D. The apparatus of any of aspects 1D-22D, wherein the media device comprises a head mounted display.

Aspect 24D. The apparatus of any of aspects 1D to 23D, wherein the media device comprises a mobile handheld device.

Aspect 25D. The apparatus of any of aspects 1D-24D, wherein the media device comprises a wearable device.

Aspect 26D. The apparatus of any one of aspects 1D to 25D, wherein the apparatus comprises a head mounted display.

Aspect 27D. The apparatus of any one of aspects 1D to 26D, wherein the apparatus comprises a mobile handset.

Aspect 28D. The apparatus of any one of aspects 1D to 27D, wherein the apparatus comprises a wearable device.

Aspect 29D. The apparatus of any one of aspects 1D to 28D, wherein the apparatus comprises a server.

Aspect 30D. The apparatus of any one of aspects 1D-29D, wherein the apparatus is in the geographic region.

Aspect 31D. A method for processing image data, the method comprising: receiving media data based on sensor data captured by one or more sensors of a media device; receiving positioning data indicative of a location of the media device while the sensor data is captured by the one or more sensors of the media device; based on the positioning data, verifying that the location of the media device is within a geographic area while capturing the sensor data; and in response to verifying that the location of the media device is within the geographic region, automatically generating a token corresponding to the media data, the token identified in a payload of a block of a distributed ledger.

Aspect 32D. The method of aspect 31D, wherein the media data is the sensor data.

Aspect 33D. The method of any of aspects 31D-32D, wherein the media device generates the media data at least in part by modifying the sensor data to add virtual content to the sensor data.

Aspect 34D. The method of any of claims 31D-33D, wherein the sensor data includes one or more images captured by one or more image sensors of the one or more sensors of the media device, and wherein the media data is based on at least one of the one or more images.

Aspect 35D. The method of any of claims 31D-34D, wherein the sensor data includes the positioning data, the positioning data determined based on one or more positioning signals received by a positioning receiver in the one or more sensors of the media device, and wherein the media data includes a map generated by the media device based on the positioning data.

Aspect 36D. The method of any of aspects 31D-35D, 36D, 42D, or 43D, wherein the positioning receiver is a short-range wireless communication receiver configured to receive one or more short-range wireless communication signals.

Aspect 37D. The method of any of claims 31D-36D, wherein the one or more short-range wireless communication signals are transmitted by a local device in the geographic area, and wherein the geographic area corresponds to a transmission range of the one or more short-range wireless communication signals of the local device.

Aspect 38D. The method of any of aspects 31D-37D, 36D, or 42D-45D, wherein the positioning receiver is a global navigation satellite system receiver configured to receive one or more GNSS signals from one or more satellites.

Aspect 39D. The method of any of claims 31D-38D, wherein the sensor data includes auxiliary positioning data determined based on one or more positioning signals received by a positioning receiver in the one or more sensors of the media device, and wherein the media data is a map generated by the media device based on the auxiliary positioning data.

Aspect 40D. The method of any one of aspects 31D to 39D, further comprising: automatically generating the block for the distributed ledger in response to verifying that the location of the media device is within the geographic area; and attaching the tile to a plurality of tiles of the distributed ledger.

Aspect 41D. The method of any of aspects 31D-40D, wherein the chunk includes a hash of at least a portion of a previous chunk of the distributed ledger.

Aspect 42D. The method of any of aspects 31D-41D, wherein the chunk includes a merck root of a plurality of elements of the payload of the chunk, and wherein the token corresponds to at least one element of the plurality of elements of the payload of the chunk.

Aspect 43D. The method of any one of aspects 31D to 42D, further comprising: the distributed ledger is automatically generated in response to verifying that the location of the media device is within the geographic area.

Aspect 44D. The method of any one of aspects 35D, 36D, 42D, or 43D, further comprising: in response to verifying that the location of the media device is within the geographic region, sending a request to a tile generation computing device to generate the tile for the distributed ledger; receiving the block from the block generation computing device; and attaching the tile to a plurality of tiles of the distributed ledger.

Aspect 45D. The method of aspect 44D, wherein receiving the positioning data comprises receiving the positioning data from the media device, the positioning data based on one or more positioning signals received by a positioning receiver of the one or more sensors of the media device.

Aspect 46D. The method of any one of aspects 35D, 36D, or 42D-45D, wherein the method is performed by an apparatus comprising the local device.

Aspect 47D. The method of any of aspects 31D-46D, wherein receiving the positioning data includes receiving the positioning data from a local device different from the media device, the positioning data based on one or more positioning signals received by a positioning receiver of the local device.

Aspect 48D. The method of any of aspects 42D-47D, wherein verifying that the location of the media device is within the geographic area while capturing the sensor data includes verifying content of one or more communications between the media device and a local device associated with the geographic area.

Aspect 49D. The method of any of aspects 31D-48D, wherein the method is performed by an apparatus comprising the media device.

Aspect 50D. The method of any of aspects 31D-49D, wherein verifying that the location of the media device is within the geographic area while capturing the sensor data includes verifying that the sensor data depicts an object visible within the geographic area.

Aspect 51D. The method of any one of aspects 31D to 50D, further comprising: ownership of the token is set to an account associated with a user associated with the media device.

Aspect 52D. The method of any one of aspects 31D to 51D, further comprising: identifying that the sensor data includes a representation of an individual having an identified identity; and setting ownership of the token to an account associated with the individual having the identified identity.

Aspect 53D. The method of any of aspects 31D-52D, wherein the media device comprises a head mounted display.

Aspect 54D. The method of any of aspects 31D-53D, wherein the media device comprises a mobile handheld device.

Aspect 55D. The method of any of aspects 31D-54D, wherein the media device comprises a wearable device.

Aspect 56D. The method of any of aspects 31D-55D, wherein the method is performed by a device comprising a head mounted display.

Aspect 57D. The method of any one of aspects 31D-56D, wherein the method is performed by an apparatus comprising a mobile handset.

Aspect 58D. The method of any one of aspects 31D-57D, wherein the method is performed by an apparatus comprising a wearable device.

Aspect 59D. The method of any one of aspects 31D-58D, wherein the method is performed by an apparatus comprising a server.

Aspect 60D. The method of any one of aspects 31D-59D, wherein the method is performed by a device in the geographic area.

Aspect 61D. An apparatus for processing image data, the apparatus comprising: means for performing the method of any one of aspects 31D-60D.

Aspect 62D. A non-transitory computer readable storage medium having a program thereon, wherein the program is executable by a processor to perform a method of processing image data, the method comprising: any of the methods of aspects 31D-60D.

Claims

1. An apparatus for context token associated media output, the apparatus comprising:

at least one memory; and

at least one processor coupled to the at least one memory, the at least one processor configured to:

receiving sensor data captured by at least one sensor of a media device;

Identifying a relationship between the media device and an anchor element associated with a token based on the sensor data;

identifying the token in a payload of at least one tile of a distributed ledger, wherein the token corresponds to media content according to the distributed ledger;

generating a representation of the media content corresponding to the token; and

the representation of the media content is output in response to identifying the relationship between the media device and the anchor element.

2. The apparatus of claim 1, wherein the sensor data comprises image data captured by at least one image sensor of the at least one sensor of the media device, wherein the anchor element comprises an object, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify the image data to depict the object.

3. The apparatus of claim 2, wherein the object comprises an optical glyph, wherein the information indicative of the token is optically encoded based on the optical glyph.

4. The apparatus of claim 2, wherein reference image data depicting the object is stored in a data store, and wherein to identify that the image data depicts the object, the at least one processor is configured to compare the image data with the reference image data.

5. The apparatus of claim 1, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a region, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify that the location of the media device is within the region.

6. The apparatus of claim 1, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a place, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify that the location of the media device is within a threshold range of the place.

7. The apparatus of claim 1, wherein the sensor data comprises audio data captured by at least one microphone of the at least one sensor of the media device, wherein the anchor element comprises sound, and wherein to identify the relationship between the media device and the anchor element, the at least one processor is configured to identify that the audio data comprises the sound.

8. The apparatus of claim 1, wherein to output the representation of the media content, the at least one processor is configured to cause a display to display at least a portion of the media content.

9. The apparatus of claim 8, wherein the at least one processor is configured to:

identifying a media device pose of the media device based on the sensor data; and

a media content pose for the media content is determined based on the media device pose of the media device, wherein to cause the display to display the at least a portion of the media content, the at least one processor is configured to output the representation of the media content that is pose-adjusted according to the media content pose.

10. The apparatus of claim 1, wherein the at least one processor is configured to:

identifying, based on the distributed ledger, that a parameter of the token indicates that the token is associated with a first user;

determining a visual effect for the media content based on a parameter of the token indicating that the token is associated with the first user; and

The visual effect is applied to the media content, wherein to output the representation of the media content, the at least one processor is configured to output the representation of the media content with the visual effect applied.

11. The apparatus of claim 10, wherein the at least one processor is configured to:

determining that the first user and second user are associated according to a relationship type based on a data store, wherein the media device is associated with the second user, and wherein the visual effect for the media content corresponds to the relationship type.

12. The apparatus of claim 10, wherein the at least one processor is configured to:

determining that the media device is associated with the first user, and wherein the visual effect for the media content corresponds to the first user.

13. The apparatus of claim 10, wherein the at least one processor is configured to:

the method further includes determining that the first user is a celebrity based on a data store, and wherein the visual effect for the media content corresponds to the first user being the celebrity.

14. The apparatus of claim 10, wherein the at least one processor is configured to:

a rating associated with the media content is determined based on a data store, and wherein the visual effect for the media content corresponds to the rating.

15. The apparatus of claim 10, wherein the at least one processor is configured to:

determining that the token is identified in a data store, and wherein the visual effect for the media content corresponds to the data store.

16. The apparatus of claim 1, wherein the at least one processor is configured to:

retrieving information about the token from the distributed ledger; and

outputting said information about said token.

17. The apparatus of claim 16, wherein to output the information about the token, the at least one processor is configured to cause a display to display at least a portion of the information.

18. The apparatus of claim 16, wherein the at least one processor is configured to:

a parameter identifying the token based on the distributed ledger indicates that the token is associated with a first user, wherein the information identifies the first user.

19. The apparatus of claim 16, wherein the information identifies the distributed ledger.

20. The apparatus of claim 16, wherein the at least one processor is configured to:

a parameter identifying the token based on the distributed ledger indicates that the token is associated with a smart contract, wherein the information identifies the smart contract.

21. The apparatus of claim 16, wherein the at least one processor is configured to:

a parameter identifying the token based on the distributed ledger indicates a number of instances of the token, wherein the information identifies the number of instances of the token.

22. The apparatus of claim 1, wherein the at least one processor is configured to:

identifying a transfer platform configured for token transfer; and

an interface element corresponding to the media content is output, wherein the interface element is configured to initiate transfer of the token using the transfer platform upon interaction with the interface element.

23. The apparatus of claim 1, wherein the apparatus comprises at least one of a Head Mounted Display (HMD), a mobile handheld device, or a wireless communication device.

24. A method of context token associated media output, the method comprising:

receiving sensor data captured by at least one sensor of a media device;

25. The method of claim 24, wherein the sensor data comprises image data captured by at least one image sensor of the at least one sensor of the media device, wherein the anchor element comprises an object, and wherein identifying the relationship between the media device and the anchor element comprises: the image data is identified to depict the object.

26. The method of claim 24, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a region, and wherein identifying the relationship between the media device and the anchor element comprises: the location of the media device is identified as being within the region.

27. The method of claim 24, wherein the sensor data comprises location data indicative of a location of the media device, wherein the anchor element comprises a place, and wherein identifying the relationship between the media device and the anchor element comprises: the location of the media device is identified as being within a threshold range of the location.

28. The method of claim 24, wherein the sensor data comprises audio data captured by at least one microphone of the at least one sensor of the media device, wherein the anchor element comprises sound, and wherein identifying the relationship between the media device and the anchor element comprises: identifying that the audio data includes the sound.

29. The method of claim 24, further comprising:

applying the visual effect to the media content, wherein outputting the representation of the media content comprises: outputting the representation of the media content with the visual effect applied.

30. The method of claim 24, further comprising:

retrieving information about the token from the distributed ledger; and

outputting said information about said token.