Systems and methods for managing non-fungible tokens and corresponding digital assets

Abstract

Systems and techniques are described for token device transfer management. The system identifies a token corresponding to media content in a payload of at least one block of a distributed ledger. Parameters of the token in the distributed ledger indicate that the token is associated with a first user. The system identifies a device associated with the token and the media content. The device is also associated with the first user. The system determines that the device has moved to an area associated with a second user. In response to determining that the device has moved to the area, the system causes parameters of the token in the distributed ledger to be altered from indicating that the token is associated with the first user to indicating that the token is associated with the second user.

Description

[[Technical Field]]

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

[0002] People often find meaning in owning, using, or trading unique or rare physical items associated with respected celebrities, events, or locations. For example, people often get signatures on clothing or music albums from famous musicians at concert venues as a memento of attending the concert, and seek to make the signed clothing or music album a unique item. Similarly, people often seek to purchase costumes, props, animation stills, and other items used to produce movies or television programs.

[0003] Digital assets may include, for example, images, videos, audio clips, three-dimensional models, and the like. Generally, digital assets are fungible, meaning that any one copy of a given digital asset is interchangeable with any other copy of the same digital asset.

[0004] 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 handset, or other device. This environment is at least partially different from the real-world environment where the user is located. A user can generally interactively change the view of the environment, for example, by tilting or moving the HMD or other device (e.g., by moving the user's head). Virtual reality (VR), augmented reality (AR), and mixed reality (MR) are examples of XR. [[Summary of Invention]] [Means for solving the problem]

[0005] In some examples, systems and techniques are described for creating, modifying, tracking, authenticating, and / or transferring non-fungible digital assets associated with the location of a device. A media device may include sensors such as image sensors and / or positioning sensors. A media device may use its sensors to ingest sensor data. In some examples, a system receives media content based on sensor data ingested by at least one sensor of a media device. The system determines the location of the media device (for example, based on the sensor data). The system determines (for example, based on the sensor data) that the location of the media device is within a geographical area. In response to determining that the location of the media device is within a geographical area, the system generates a token corresponding to the media content. The payload of at least one block in a distributed ledger identifies the token.

[0006] In some examples, the system receives sensor data captured by at least one sensor of a media device. Based on the sensor data, the system identifies the interaction between the media device and an anchor element associated with a certain token. The system identifies that token in the payload of at least one block of a 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 interaction between the media device and the anchor element, the system outputs a representation of the media content.

[0007] In some examples, the system identifies a token corresponding to media content in the payload of at least one block in the distributed ledger. The token's parameters in the distributed ledger indicate that the token is associated with a first user. The system identifies a device associated with the token and the media content. The device is also associated with the first user. The system identifies that the device has moved to an area associated with a second user. In response to identifying that the device has moved to that area, the system modifies the token's parameters in the distributed ledger from indicating that the token is associated with a first user to indicating that the token is associated with a second user.

[0008] In several examples, systems and techniques for token generation are described. Systems, apparatus, methods, and computer-readable media for token generation are disclosed. According to at least one example, an apparatus for token generation is provided, comprising at least one memory and at least one processor coupled to the at least one memory. The at least one processor is configured to receive media content based on sensor data captured by at least one sensor of a media device, determine the location of the media device, determine that the location of the media device is within a geographic area, and in response to the determination that the location of the media device is within that geographic area, generate a token corresponding to the media content, the payload of at least one block of a distributed ledger identifies the token.

[0009] Another example provides a method for token generation. The method includes the steps of receiving media content based on sensor data captured by at least one sensor of a media device, determining the location of the media device, determining that the location of the media device is within a geographic area, and generating a token corresponding to the media content in response to the determination that the location of the media device is within that geographic area, wherein the payload of at least one block of a distributed ledger identifies the token.

[0010] In another example, a non-temporary computer-readable medium is provided on which instructions are stored, and when executed by one or more processors, these instructions cause one or more processors to receive media content based on sensor data captured by at least one sensor of a media device, to determine the location of the media device, to determine that the location of the media device is within a geographical area, and in response to the determination that the location of the media device is within that geographical area, to generate a token corresponding to the media content, and the payload of at least one block of a distributed ledger identifies the token.

[0011] In another example, a device for token generation is provided. The device includes means for receiving media content based on sensor data captured by at least one sensor of a media device; means for determining the location of the media device; means for determining that the location of the media device is within a geographical area; and means for generating a token corresponding to the media content in response to the determination that the location of the media device is within that geographical area, wherein the payload of at least one block of a distributed ledger identifies the token.

[0012] In another example, a device for context-dependent token-related media output is provided, comprising at least one memory and at least one processor coupled to at least one memory. The at least one processor is configured to receive sensor data captured by at least one sensor of a media device, to identify a relationship between the media device and an anchor element associated with a token based on the sensor data, to identify the token in the payload of at least one block of a distributed ledger, to generate a representation of the media content corresponding to the token, and to output the representation of the media content in response to having identified the relationship between the media device and the anchor element.

[0013] Another example provides a method for context-dependent token-related media output. The method includes the steps of: 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 a token in the payload of at least one block 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 having identified the relationship between the media device and the anchor element.

[0014] In another example, a non-temporary computer-readable medium is provided on which instructions are stored. When these instructions are executed by one or more processors, one or more processors are caused to receive sensor data captured by at least one sensor of a media device, to identify the relationship between the media device and an anchor element associated with a token based on the sensor data, to identify the token in the payload of at least one block of a distributed ledger, to generate a representation of the media content corresponding to the token according to the distributed ledger, and to output a representation of the media content in response to having identified the relationship between the media device and the anchor element.

[0015] In another example, a device for context-dependent token-related media output is provided. The device includes at least one memory and at least one processor coupled to the at least one memory, the at least one processor being configured to receive sensor data captured by at least one sensor of a media device, to identify the relationship between the media device and an anchor element associated with the token based on the sensor data, to identify the token in the payload of at least one block of a distributed ledger, to generate a representation of the media content corresponding to the token, and to output the representation of the media content in response to having identified the relationship between the media device and the anchor element.

[0016] In another example, a device for managing token device transfers is provided, comprising at least one memory and at least one processor coupled to at least one memory. The at least one processor is configured to identify a token corresponding to media content in the payload of at least one block of a distributed ledger, to identify a device associated with the token and media content, to identify that the device is associated with the first user, that the device has moved to an area associated with a second user, and in response to the identification of the device moving to that area, to modify the token's parameters 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.

[0017] Another example provides a method for managing token device transfers. The method includes the steps of: identifying a token corresponding to media content in the payload of at least one block of a distributed ledger, wherein the parameters of the token in the distributed ledger indicate that the token is associated with a first user; identifying a device associated with the token and media content, wherein the device is associated with a first user; identifying that the device has moved to an area associated with a second user; and, in response to identifying that the device has moved to that area, modifying the parameters of the token in the distributed ledger from indicating that the token is associated with a first user to indicating that the token is associated with a second user.

[0018] In another example, a non-temporary computer-readable medium is provided on which instructions are stored, and when executed by one or more processors, the instructions cause one or more processors to identify a token corresponding to media content in the payload of at least one block of a distributed ledger, to cause the parameters of the token in the distributed ledger to indicate that the token is associated with a first user, to identify a device associated with the token and the media content, to identify that the device is associated with a first user and that the device has moved to an area associated with a second user, and in response to the identification of the device having moved to that area, the parameters of the token in the distributed ledger to change from indicating that the token is associated with a first user to indicating that the token is associated with a second user.

[0019] In another example, a device for managing token device transfers is provided. The device includes means for identifying a token corresponding to media content in the payload of at least one block of a distributed ledger, wherein the parameters of the token in the distributed ledger indicate that the token is associated with a first user; means for identifying a device associated with the token and media content, wherein the device is associated with a first user; means for identifying that the device has moved to an area associated with a second user; and means for changing, in response to identifying that the device has moved to that area, the parameters of the token in the distributed ledger from indicating that the token is associated with a first user to indicating that the token is associated with a second user.

[0020] In some embodiments, the media content includes at least a portion of the sensor data. In some embodiments, the media content includes a modified version of at least a portion of the sensor data.

[0021] In some embodiments, the sensor data includes at least one image captured by at least one image sensor of at least one sensor of the media device, and the media content is based on at least one of the at least one image. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises detecting at least one portion of an environment in at least one image and determining the location of the media device based at least in part on the detection of at least that portion of the environment in at least one image. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises detecting at least one portion of an environment in at least one image and determining that at least that portion of the environment is located within a geographical area. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises detecting at least one portion of an individual in at least one image, determining the identity of that individual, and setting the parameters of a token to indicate that the token is associated with that identity.

[0022] In some embodiments, the sensor data includes positioning data based on the reception of at least one wireless signal by at least one sensor, and determining the location of the media device includes determining the location of the media device based on at least part of the positioning data. In some embodiments, the at least one wireless signal includes a short-range wireless signal from a local device that is at least within the transmission range of the media device during the reception of the at least one wireless signal by at least one sensor. In some embodiments, the at least one wireless signal includes a GNSS signal from a Global Navigation Satellite System (GNSS) satellite.

[0023] In some forms, media content includes maps of geographical areas.

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

[0025] In some aspects, the method is performed using an apparatus that includes a local device. In some aspects, the method is performed using an apparatus that includes a media device. In some aspects, the method is performed using an apparatus located within a geographic area.

[0026] In some aspects, one or more of the above-described methods, apparatuses, and computer-readable media further comprises, in response to determining that the location of the media device is within the geographic area, generating at least one block, and causing the at least one block to be added to a distributed ledger. In some aspects, the at least one block includes a hash of at least a portion of a previous block of the distributed ledger. In some aspects, one or more of the above-described methods, apparatuses, and computer-readable media further comprises, in response to determining that the location of the media device is within the geographic area, generating a distributed ledger. In some aspects, one or more of the above-described methods, apparatuses, and computer-readable media further comprises, in response to determining that the location of the media device is within the geographic area, transmitting a request to generate at least one block to a computing device, receiving the at least one block, and adding the at least one block to the distributed ledger.

[0027] In some aspects, one or more of the above-described methods, apparatuses, and computer-readable media further comprises setting a parameter of a token to indicate that the token is associated with a user, and the media device is associated with the user.

[0028] In some aspects, one or more of the above-described methods, apparatuses, and computer-readable media further comprise determining that the geographic area includes at least a threshold number of people, and generating the token corresponding to the media content is performed in response to determining that the geographic area includes at least the threshold number of people.

[0029] In some aspects, the sensor data includes image data captured by at least one image sensor of at least one sensor of a media device, the anchor element includes an object, and identifying the relationship between the media device and the anchor element includes identifying that the image data depicts the object. In some aspects, the object includes an optical glyph, and information indicating 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 identifying that the image data depicts the object includes comparing the image data to the reference image data.

[0030] In some aspects, the sensor data includes location data indicating the location of the media device, the anchor element includes an area, and identifying the 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 the location of the media device, the anchor element includes a position, 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 distance from the position.

[0031] In some aspects, the sensor data includes audio data captured by at least one microphone of at least one sensor of a media device, the anchor element includes a sound, and identifying the relationship between the media device and the anchor element includes identifying that the audio data includes the sound.

[0032] In some embodiments, outputting a representation of media content includes displaying at least a portion of the media content on a display.

[0033] In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises determining the media device orientation of a media device based on sensor data, determining the media content orientation relative to media content based on the media device orientation of the media device, and outputting a representation of the media content includes outputting a representation of the media content in orientation according to the media content orientation.

[0034] In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises: identifying, based on a distributed ledger, that the parameters of a token indicate that the token is associated with a first user; determining a visual effect on media content based on the parameters of the token indicating that the token is associated with a first user; and applying the visual effect to the media content, wherein outputting a representation of the media content includes outputting a representation of the media content together with the applied visual effect.

[0035] In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises determining, based on a data store, that a first user and a second user are associated according to a relationship, the media device is associated with the second user, and the visual effect on the media content corresponds to the relationship. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises determining, based on a data store, that the first user is a famous person, and the visual effect on the media content corresponds to the first user. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises determining, based on a data store, that a rating associated with the media content is corresponding to the rating.

[0036] In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises determining that a token is identified in a data store, and the visual effect on media content corresponds to the data store. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises retrieving information about a token from a distributed ledger and outputting information about a token. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises outputting information about a token including displaying at least some portion of the information on a display.

[0037] In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises identifying, based on a distributed ledger, that the parameters of a token indicate that the token relates to a first user, and the information identifies the first user. In some embodiments, the information identifies a distributed ledger. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises identifying, based on a distributed ledger, that the parameters of a token indicate that the token relates to a smart contract, and the information identifies the smart contract. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises identifying, based on a distributed ledger, that the information identifies the quantity of token instances. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises identifying a transfer platform configured for token transfer and outputting an interface element corresponding to media content, the interface element being configured to initiate a token transfer using the transfer platform upon interaction with the interface element.

[0038] In some embodiments, the device is configured to present media content.

[0039] In some embodiments, device identifiers are stored in a distributed ledger, and identifying a device is based on these identifiers.

[0040] In some embodiments, the device includes an interactive element that represents a token, and identifying the token is based on interaction with the interactive element. In some embodiments, the interaction includes an optical glyph, and the token identifier is optically encoded based on the optical glyph.

[0041] In some embodiments, this involves receiving image data, detecting that a device is represented in the image data, and identifying a token based on the detection that the device is represented in the image data.

[0042] In some embodiments, identifying that a device has moved to an area associated with a second user includes identifying that the device has moved from a first area associated with a first user. In some embodiments, identifying that a device has moved to an area associated with a second user includes identifying that one or more additional devices located in the area are associated with the second user. In some embodiments, identifying that a device has moved to an area associated with a second user includes identifying that a wireless local area network (WLAN) in the area is associated with the second user. In some embodiments, identifying that a device has moved to an area associated with a second user includes determining that location data from at least one of the device's location sensors indicates that the device is located in that area, where the area is a geographical area. In some embodiments, identifying that a device has moved to an area associated with a second user includes determining that location data from at least one of the device's location sensors indicates that the device is located within the range of the second user's location, where the area associated with the second user is within the range of the second user's location.

[0043] In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises modifying the parameters of a token in a distributed ledger so that a new block is added to the distributed ledger, the parameters of the token in the distributed ledger are modified based on the payload of the new block.

[0044] In some embodiments, ensuring that a new block is added to a distributed ledger involves generating a new block.

[0045] In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises sending an authorization request to a first user device relating to a first user to modify the parameters of a token in a distributed ledger from indicating that the token relates to a first user to indicating that the token relates to a second user, and receiving authorization from the first user device. In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises sending an authorization request to a second user device relating to a second user to modify the parameters of a token in a distributed ledger from indicating that the token relates to a first user to indicating that the token relates to a second user, and receiving authorization from the second user device.

[0046] In some embodiments, one or more of the methods, apparatus, and computer-readable media described above further comprises identifying a smart contract relating to a token in a distributed ledger, the smart contract indicating that the parameters of the token should be modified in response to a condition, and causing the parameters of the token in the distributed ledger to be modified includes executing the smart contract in response to identifying the condition, and identifying the condition is based on identifying that the device has moved to an area relating to a second user.

[0047] In some embodiments, the device includes a head-mounted display. In some embodiments, the device includes a mobile handset. In some embodiments, the device includes a wireless communication device. In some embodiments, the device includes a wearable device. In some embodiments, the device includes a server. In some embodiments, the device is located within a geographical area.

[0048] In some embodiments, the device is a wearable device, an extended 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 a so-called “smartphone” or other mobile device), a camera, a personal computer, a laptop computer, a server computer, a vehicle or a vehicle computing device or component, or any other device, part thereof, and / or including it. In some embodiments, the device includes a camera or a number of cameras for capturing one or more images. In some embodiments, the device further includes a display for displaying one or more images, notifications, and / or other displayable data. In some embodiments, the device described above may include one or more sensors (e.g., one or more gyrometers, one or more accelerometers, any combination thereof, and / or other sensors, or one or more inertial measuring units (IMUs)).

[0049] This summary is not intended to identify the main or essential features of the claimed subject matter, nor is it intended to be used independently to determine the scope of the claimed subject matter. The subject matter should be understood by referring to the entire specification of this patent, any or all of the drawings, and the appropriate portions of each claim.

[0050] The above will become clearer with reference to the following specification, claims, and accompanying drawings, along with other features and embodiments.

[0051] Exemplary embodiments of this application are described in detail below with reference to the following drawings. [Brief explanation of the drawing]

[0052] [Figure 1] This block diagram shows exemplary architectures of image acquisition and processing systems, with several examples. [Figure 2] This block diagram shows an exemplary architecture of a digital asset tracking system that may be used to track location-related digital assets, with several examples. [Figure 3A] This is a perspective view showing several examples of head-mounted displays (HMDs) used as media devices as part of a digital asset tracking system. [Figure 3B] Figure 3A is a perspective view showing a head-mounted display (HMD) being worn by a user, illustrating several examples. [Figure 4A] This is a perspective view showing the front of a mobile handset, including a front-facing camera, which can be used as a media device as part of a digital asset tracking system, with several examples. [Figure 4B] This is a perspective view showing the back of a mobile handset, including a rear camera, which can be used as a media device as part of a digital asset tracking system, with several examples. [Figure 5] The image shows three consecutive blocks of a blockchain ledger, which may be used to track digital assets related to locations within a geographical area, as illustrated by several examples. [Figure 6] This block diagram illustrates an exemplary token that may be non-fungible, which can represent a digital asset associated with a location within a geographical area, such as one tracked on a distributed ledger, using several examples. [Figure 7] This block diagram shows a directed acyclic graph (DAG) ledger configured to track digital assets related to locations within a geographical area, with several examples. [Figure 8A] This perspective view, with several examples, shows how a user uses a media device to capture digital assets (images), such as portraits in a museum. [Figure 8B] This is a conceptual diagram illustrating information about tokens related to digital assets in Figure 8A, using several examples. [Figure 9A]This is a perspective view showing how a user uses a media device to capture digital assets (images) of several people, including an individual identified as Bob, using several examples. [Figure 9B] This is a conceptual diagram illustrating information about tokens related to digital assets in Figure 9A, using several examples. [Figure 10A] This perspective view, with several examples, shows how a user uses a media device to generate digital assets (images) that include virtual objects superimposed onto real-world landscapes. [Figure 10B] This is a conceptual diagram illustrating information about tokens related to digital assets in Figure 10A, using several examples. [Figure 11A] This is a perspective view illustrating, through several examples, how a user might use a media device to generate a digital asset (map) of hiking trails. [Figure 11B] This is a conceptual diagram illustrating information about tokens related to digital assets in Figure 11A, using several examples. [Figure 12A] This perspective view illustrates, through several examples, how users utilize ownership devices to purchase digital assets (images), such as portraits in a museum. [Figure 12B] This is a conceptual diagram illustrating information about tokens related to digital assets in Figure 12A, using several examples. [Figure 13] This is a conceptual diagram illustrating, with several examples, the anchor elements associated with tokens and how the detection of these anchor elements by media devices triggers the display of the corresponding digital assets on the media devices. [Figure 14] This is a conceptual diagram illustrating, with several examples, token devices associated with tokens in a distributed ledger, and the transfer of token devices from a first user to a second user. [Figure 15A] This is a conceptual diagram illustrating the generation of smart contracts and their input into a distributed ledger, using several examples. [Figure 15B]This is a conceptual diagram illustrating the execution of a smart contract in one aspect of the present disclosure, using several examples. [Figure 16A] This flowchart illustrates the process of generating tokens in a context-dependent manner, using several examples. [Figure 16B] This flowchart illustrates the process of tracking location-related digital assets using several examples. [Figure 17] This flowchart illustrates the process for token-related media output in a context-dependent manner, using several examples. [Figure 18] This flowchart illustrates the process for managing token device transfers, using several examples. [Figure 19] This figure shows an example of a computing system for implementing some of the embodiments described herein. [Modes for carrying out the invention]

[0053] Several aspects and embodiments of this disclosure are provided below. As will be apparent to those skilled in the art, some of these aspects and embodiments may be applied independently, and some of them may be applied in combination. The following description includes specific details for illustrative purposes to provide a complete understanding of the embodiments of this application. However, it will be apparent that various embodiments may be practiced without these specific details. The figures and description are not intended to be limiting.

[0054] The following description provides only exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the following description of exemplary embodiments provides a description that enables the implementation of exemplary embodiments for those skilled in the art. It should be understood that various modifications may be made to the function and configuration of the elements without departing from the spirit and scope of this application as set forth in the appended claims.

[0055] People often find meaning in owning, using, or trading unique or rare physical items relating to a respected celebrity, activity, or position. For example, people often get their clothes or music albums signed by a famous musician at a concert venue as a memento of attending the concert, and then try to make the signed clothes or music album a unique item. Similarly, people often try to purchase costumes, props, animation stills, and other items used to create a movie or television show.

[0056] A camera is a device that uses an image sensor to receive light and capture image frames, such as still images or video frames. The terms “image,” “image frame,” and “frame” are used interchangeably herein. A camera can consist of various image capture and image processing settings. Different settings result in images with different appearances. Some camera settings, such as ISO, exposure time, aperture size, f / stop, shutter speed, focus, and gain, are determined and applied before or during the capture of one or more image frames. For example, settings or parameters may be applied to the image sensor for capturing one or more image frames. Other camera settings, such as contrast, brightness, saturation, sharpness, levels, curves, or color changes, can constitute post-processing of one or more image frames. 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 the image sensor.

[0057] Digital assets may include, for example, images or videos captured by a camera, audio clips captured by a microphone, 3D point clouds, and / or models from distance sensors. Generally, digital assets are interchangeable, meaning that any one copy of a given digital asset can be replaced by any other copy of the same digital asset.

[0058] In some examples, systems and techniques for creating, modifying, tracking, authenticating, and / or transferring non-fungible digital assets related to the location of a device are described herein. A 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 (SONAR) sensors, time-of-flight (ToF) sensors, structured light sensors), microphones, other sensors described herein, or combinations thereof. A media device may use its sensors to capture sensor data. A media device may generate and / or acquire media data based on its sensor data. Media data may include sensor data. In some examples, media data may include processed and / or modified forms of sensor data. For example, media data may include virtual content (e.g., virtual objects) generated for XR output. The media data may include maps generated based on positioning data from positioning sensors. The media data may also include high dynamic range (HDR) images generated by integrating multiple images.

[0059] Positioning data indicating the attitude of a media device during sensor data acquisition may be obtained from the media device, for example from the media device's positioning sensor, and / or based on one or more short-range wireless communications between the media device and a local device. Positioning data indicating the attitude of a media device during sensor data acquisition may be obtained from a local device communicating with the media device using one or more short-range wireless communications. The media device can transmit media data to a network device. Based on the positioning data, the network device can verify that the media device was in a given geographical area during sensor data acquisition. A geographical area could be, for example, a museum, a stadium, or a concert venue. In some cases, a geographical area can be defined by the range of the local device's short-range wireless communications, and verification of the media device's location may be based on verifying that communications transmitted between the media device and the local device were correctly received by the media device and / or the local device. In response to verifying that the media device was in a given geographical area during sensor data acquisition, the network device can generate a token for the media data. A network device can input tokens into a distributed ledger, such as a blockchain ledger, by generating a block with tokens in its payload and adding that block to the distributed ledger, or by requesting a block-generating device to generate a block with tokens in its payload and adding that block to the distributed ledger. Tokens may be associated with smart contracts stored in a distributed ledger that control the transfer of tokens related to media data. In some cases, the network device may be part of a media device.

[0060] 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 handset, or other devices. The environment is at least partially different from the real-world environment in which the user and device are located and may include, for example, virtual content. In some examples, the environment that the XR device displays to the user may be at least partially virtual. In some cases, the user can interactively change the view of the environment displayed by the XR device by, for example, tilting the XR device and / or moving the XR device laterally. Tilting the XR device may include tilting or rotating along the pitch, yaw, and roll axes, or a combination thereof. Lateral movement of the XR device may include lateral movement along a trajectory drawn in a three-dimensional volume having three orthogonal axes such as the X, Y, and Z axes. An XR device that tracks only rotation may be called a 3-degrees-of-freedom (3DoF) XR device. An XR device that tracks both tilt and lateral movement can be called a 6-degree-of-freedom (6DoF) XR device. Extended reality (XR) can include virtual reality (VR), augmented reality (AR), mixed reality (MR), or a combination of these.

[0061] Generating tokens corresponding to media data and entering those tokens into a distributed ledger may offer technical advantages over the normal transfer of images or other digital assets. Tokens transform media data from a fungible state to a non-fungible state, enabling individual copies or instances of media data to be securely, efficiently, and automatically tracked, owned, transferred, borrowed, and licensed. Making token generation based on verification that the media device's location during sensor data acquisition is within a geographical area can provide further security and verification regarding the authenticity of representations of objects, environments, or individuals in the media data.

[0062] Various aspects of application examples will be described with reference to the figures. Figure 1 is a block diagram showing the architecture of the image acquisition and processing system 100. The image acquisition and processing system 100 includes various components used to acquire and process images of a scene (for example, images of scene 110). The image acquisition and processing system 100 can acquire standalone images (or photographs) and / or video containing multiple 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 the lens 115 passes through an aperture controlled by one or more control mechanisms 120 and is received by the image sensor 130.

[0063] One or more control mechanisms 120 may control exposure, focus, and / or zoom based on information from the image sensor 130 and / or from the image processor 150. One or more control mechanisms 120 may include multiple 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 control mechanisms 125C. One or more control mechanisms 120 may also include additional control mechanisms not shown, such as control mechanisms for analog gain, flash, HDR, depth of field, and / or other image capture characteristics.

[0064] The focus control mechanism 125B of the control mechanism 120 can acquire the focus setting. In some examples, the focus control mechanism 125B stores the focus setting in a memory register. Based on the focus setting, the focus control mechanism 125B can adjust the position of the lens 115 relative to the position of the image sensor 130. For example, based on the focus setting, the focus control mechanism 125B can adjust the focus by moving the lens 115 closer to or further away from the image sensor 130 by acting a motor or servo. In some cases, the system 100 may include additional lenses, such as one or more microlenses on each photodiode of the image sensor 130, each of which bends the light received from the lens 115 toward the corresponding photodiode before it reaches the photodiode. The focus setting may be determined via contrast-detection autofocus (CDAF), phase-detection autofocus (PDAF), or any combination thereof. The focus setting may be determined using the control mechanism 120, the image sensor 130, and / or the image processor 150. Focus settings are sometimes referred to as image capture settings and / or image processing settings.

[0065] The exposure control mechanism 125A of the control mechanism 120 can acquire the exposure settings. In some cases, the exposure control mechanism 125A stores the exposure settings in a memory register. Based on these exposure settings, the exposure control mechanism 125A can control the aperture size (e.g., aperture size or F-stop), the duration for which the aperture is open (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 are sometimes referred to as the image acquisition settings and / or image processing settings.

[0066] The zoom control mechanism 125C of the control mechanism 120 can acquire the zoom setting. In some examples, the zoom control mechanism 125C stores the zoom setting in a memory register. Based on the zoom setting, the zoom control mechanism 125C can control the focal length of the lens assembly, which includes lens 115 and one or more additional lenses. For example, the zoom control mechanism 125C can control the focal length of the lens assembly by acting one or more motors or servos to move one or more of the lenses relative to each other. The zoom setting is sometimes referred to as the image acquisition setting and / or image processing setting. In some examples, the lens assembly may include a parfocal zoom lens or a variable-focus zoom lens. In some examples, the lens assembly may include a focusing lens (which may be lens 115) that initially receives light from the scene 110, and the light then passes through a no-focus 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, a non-focus zoom system may include two positive (e.g., converging, convex) lenses with equal or similar focal lengths (e.g., within a threshold difference) and a negative (e.g., diverging, concave) lens between them. In some cases, the zoom control mechanism 125C moves one or more of the lenses in the non-focus zoom system, such as the negative lens and one or both of the positive lenses.

[0067] 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 therefore measure light that matches the color of the filter covering the photodiode. For example, a Bayer color filter includes a red color filter, a blue color filter, and a green color filter, and each pixel in the image is produced based on data of red light from at least one photodiode covered by the red color filter, data of blue light from at least one photodiode covered by the blue color filter, and data of green light from at least one photodiode covered by the green color filter. Other types of color filters may use yellow, magenta, and / or blue-green (also called "emerald") color filters instead of, or in addition to, the red, blue, and / or green color filters. Some image sensors may lack color filters entirely and instead use different photodiodes (possibly stacked vertically) across the entire pixel array. Different photodiodes across the entire pixel array may have different spectral sensitivity curves, thus corresponding to different wavelengths of light. Monochrome image sensors may also lack color filters and therefore lack color depth.

[0068] In some cases, the image sensor 130 may, as an alternative or addition, include an opaque and / or reflective mask that prevents light from reaching some or some of the photodiodes at a given time and / or from a given angle, which may be used for phase-detection autofocus (PDAF). The image sensor 130 may also include an analog gain amplifier for amplifying the analog signal output by the photodiodes and / or analog-to-digital converter (ADC) and converting the analog signal output of the photodiodes (and / or amplified by the analog gain amplifier) ​​into a digital signal. In some cases, instead or in addition, some components or functions discussed with respect to one or more of the control mechanism 120 may be included in the image sensor 130. The image sensor 130 may be a charge-coupled device (CCD) sensor, an electron-multiplier CCD (EMCCD) sensor, an active pixel sensor (APS), a complementary metal-oxide-semiconductor (CMOS) sensor, an N-type metal-oxide-semiconductor (NMOS) sensor, a hybrid CCD / CMOS sensor (e.g., sCMOS), or any other combination thereof.

[0069] The image processor 150 may include one or more processors, such as one or more image signal processors (ISPs) (including ISP 154), one or more host processors (including host processor 152), and / or one or more of any other types of processors 1019 discussed in relation to the computing system 0019. The host processor 152 may be a digital signal processor (DSP) and / or other types of processors. In some implementations, the image processor 150 is a single integrated circuit or chip (referred to as a system-on-a-chip or SoC) including the host processor 152 and ISP 154. In some cases, the chip may also include one or more input / output ports (e.g., input / output (I / O) port 156), a central processing unit (CPU), a graphics processing unit (GPU), a broadband modem (e.g., 3G, 4G, or LTE, 5G, etc.), memory, connectivity components (e.g., Bluetooth®, Global Positioning System (GPS), etc.), any combination thereof, and / or other components. I / O port 156 may include any suitable input / output port or interface 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 Industry Processor Interface (MIPI) (such as MIPI CSI-2), a Physical (PHY) layer port or interface, an Advanced High-performance Bus (AHB) bus, any combination thereof, and / or other input / output ports. In an example for one explanation, the host processor 152 may communicate with the image sensor 130 using the I2C port, and the ISP 154 may communicate with the image sensor 130 using the MIPI port.

[0070] The image processor 150 may perform several tasks, such as mosaic removal, color space conversion, image frame downsampling, pixel interpolation, automatic exposure (AE) control, automatic gain control (AGC), CDAF, PDAF, automatic white balance, merging of image frames to form an HDR image, image recognition, object recognition, feature recognition, input reception, output management, memory management, or any combination thereof. The image processor 150 may store image frames and / or processed images in random access memory (RAM) 140 and / or 2019, read-only memory (ROM) 145 and / or 2519, a cache, memory units, another storage device, or any combination thereof.

[0071] Various input / output (I / O) devices 160 may be connected to the image processor 150. The I / O devices 160 may include a display screen, keyboard, keypad, touchscreen, trackpad, touch-sensitive surface, printer, any other output device 3519, any other input device 4519, or any combination thereof. In some cases, captions may be input to the image processing device 105B through the physical keyboard or keypad of the I / O device 160, or through the virtual keyboard or keypad of the touchscreen of the I / O device 160. The I / O 160 may include one or more ports, jacks, or other connectors that enable wired connections between the system 100 and one or more peripheral devices, through which the system 100 may receive data from and / or send data to one or more peripheral devices. The I / O 160 may include one or more wireless transceivers that enable wireless connectivity between the system 100 and one or more peripheral devices, through which the system 100 may receive data from and / or transmit data to one or more peripheral devices. The peripheral devices may include any of the previously discussed types of I / O devices 160, and when coupled to a port, jack, wireless transceiver, or other wired and / or wireless connector, they themselves may be considered I / O devices 160.

[0072] In some cases, the image acquisition and processing system 100 may be a single device. In some cases, the image acquisition and processing system 100 may be two or more separate devices, including an image acquisition 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 acquisition device 105A and the image processing device 105B may be coupled together, for example, via one or more wires, cables, or other electrical connectors and / or wirelessly via one or more wireless transceivers. In some implementations, the image acquisition device 105A and the image processing device 105B may be disconnected from each other.

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

[0074] The image acquisition and processing system 100 may include electronic devices such as mobile or fixed telephone handsets (e.g., smartphones, mobile phones, etc.), desktop computers, laptop or notebook computers, tablet computers, set-top boxes, televisions, cameras, display devices, digital media players, video gaming consoles, video streaming devices, Internet Protocol (IP) cameras, or any other suitable electronic devices. In some examples, the image acquisition and processing system 100 may include one or more wireless transceivers for wireless communication, such as cellular network communication, 802.11 Wi-Fi communication, wireless local area network (WLAN) communication, or any combination thereof. In some implementations, the image acquisition device 105A and the image processing device 105B may be different devices. For example, the image acquisition device 105A may include a camera device, and the image processing device 105B may include a computing device such as a mobile handset, a desktop computer, or other computing device.

[0075] While the image acquisition and processing system 100 is shown as comprising several components, those skilled in the art will understand that the image acquisition and processing system 100 may comprise more components than those shown in Figure 1. The components of the image acquisition and processing system 100 may comprise software, hardware, or one or more combinations of software and hardware. For example, in some implementations, the components of the image acquisition and processing system 100 may comprise and / or be implemented using one or more programmable electronic circuits (e.g., microprocessors, GPUs, DSPs, CPUs, and / or other suitable electronic circuits), electronic circuits, or other electronic hardware, and / or may comprise 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 comprise one or more instructions stored on a computer-readable storage medium and executable by one or more processors of the electronic devices implementing the image acquisition and processing system 100.

[0076] Figure 2 is a block diagram showing exemplary architectures of a digital asset tracking system 200 that may be used to track location-related digital assets, in several examples. The digital asset tracking system 200 includes a media device 205. The media device 205 may also be a computing system 0019. The media device 205 may also be an image acquisition device 105A, an image processing device 105B, and / or an image acquisition and processing system 100. In some embodiments, the media device 205 may be an extended reality (XR) device. In some examples, the media device 205 may be a mobile handset 410, a smartphone, a media player device, a camera, a head-mounted display (HMD) 310, a fitness tracker device, a smartwatch, a wearable device, or a combination thereof.

[0077] The media device 205 includes one or more sensors 210. Sensors 210 may include, for example, one or more attitude sensors 215 and one or more media sensors 220. 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 a combination thereof. 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. Distance sensors may include light detection and ranging (LIDAR) sensors, radio detection and ranging (RADAR) sensors, sound detection and ranging (SODAR) sensors, sound navigation and ranging (SONAR) sensors, time-of-flight (ToF) sensors, structured light sensors, or a combination thereof. The media device 205 may use sensors 210 to acquire attitude data 225 that identifies the attitude of the media device 205. In some cases, attitude data 225 may be referred to as location data or positioning data. The attitude data 225 of a media device may include the location of the media device 205 (e.g., latitude, longitude, and altitude, or another form of coordinates in 3D space), the orientation of the media device (e.g., pitch, yaw, and / or roll), or a combination thereof. In some examples, the media device 205 may use data acquired by the attitude sensor 215 to acquire the attitude data 225, at least in part, by determining the movement of the media device 205 based on the output of the attitude sensor 215 indicating the movement of the media device 205.In some examples, the media device 205 may use data acquired by the media sensor 220 (e.g., images acquired by the image sensor) to acquire pose data 225 and / or positioning data, at least in part, by identifying the movement of the media device 205 based on the fact that the field of view (FOV) of the media sensor 220 (e.g., the FOV of the environment shown in the data acquired by the media sensor 220) is changing or transitioning in a manner that indicates the movement of the media device 205. In some examples, the data acquired by the media sensor 220 (e.g., camera data from the image sensor) may be, and / or based on, the pose data 225 and / or positioning data. In some examples, the media device 205 may identify the 3D coordinates of features depicted in one or more images or other data acquired by the media sensor 220, for example, through feature detection, feature extraction, feature tracking, feature mapping, stereo mapping, environment mapping, visual localization, localization, or a combination thereof. In some examples, the media device 205 can generate a map of the environment based on one or more features that it has detected, extracted, tracked, and / or mapped.

[0078] The media device 205 may acquire 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 a combination thereof acquired by the media sensor 220. In some cases, the sensor data 230 may identify metadata that identifies image acquisition settings, such as acquisition timestamps and / or aperture velocity, aperture size, exposure time, ISO, focal length, focus, flash, zoom, analog gain, digital gain, auto white balance (AWB) settings, or a combination thereof. The media device 205 may acquire attitude data 225 at the same time as the acquisition of sensor data 230. The media device 205 may acquire sensor data 230 at the same time as the acquisition of attitude data 225. The media device 205 may acquire attitude data 225 in the time between the acquisitions of sensor data 230. The media device 205 may acquire sensor data 230 in the time between the acquisitions of attitude data 225.

[0079] The media device 205 may include a media processor 235. Using the media processor 235, sensor data 230, and / or attitude data 225, the media device 205 may generate and / or acquire media data 250. In some examples, the media data may be sensor data 230, attitude data 225, or both, or may include both. In such examples, the media device 205 may acquire the media data 250 directly from the sensor 210 and / or indirectly through the media processor 235, the media processor 235 may add additional data (e.g., a header), place the data 225-230 from the sensor 210 into one or more container files (e.g., an ISO container format or an ISO-based container format), integrate the attitude data 225 with the sensor data 230 and / or metadata (corresponding to the sensor data 230 and / or attitude data 225), or a combination thereof. In some examples, the media processor 235 may process the sensor data 230 and / or pose data 225 by performing, for example, any of the processing operations discussed with respect to the image processing device 105B or the image acquisition and processing system 100 in general. For example, the media processor 235 may perform demosaicing, noise reduction, sharpening, saturation adjustment, brightness adjustment, contrast adjustment, hue adjustment, color adjustment, gain, other processing tasks discussed herein, or a combination thereof. In some examples, the media processor 235 may include the image processor 150, the ISP 154, the host processor 152, the processor 1910, or a combination thereof. In some examples, the media processor 235 may synthesize multiple sensor data 230 by, for example, integrating multiple images into a high dynamic range (HDR) image which is at least part of the media data 250. In some examples, the media processor 235 may apply one or more filters to the sensor data 230 as part of generating the media data 250.

[0080] The media processor 235 may also include elements specific to XR operation, for example, if the media device 205 is an Extended Reality (XR) device. For example, the media processor 235 may include a virtual content generator 240 that generates virtual content such as virtual objects, virtual characters, virtual environments, virtual clothing, virtual costumes, virtual items, virtual sports equipment, and virtual weapons. The virtual content may include virtual objects, characters, environments, clothing, costumes, items, sports equipment, weapons, and / or other content relating to one or more video games or other XR experiences. An example of virtual content generated by the virtual content generator 240 is the virtual object 1045 (virtual dog) in Figures 10A-10B. The media processor 235 may also include an image synthesizer 245 that generates media data 250 by integrating the virtual content generated by the virtual content generator 240 with sensor data 230. For example, the image synthesizer 245 may superimpose the virtual content generated by the virtual content generator 240 onto multiple parts of the sensor data 230. In some examples, the image synthesizer 245 may adjust the orientation (e.g., position and / or orientation) of the virtual content to match the environment depicted in the sensor data 230 and / or based on the orientation data 225 (for example, so that the virtual content appears to be placed on a plane in the real environment depicted in the sensor data 230). In some examples, the image synthesizer 245 may adjust the lighting and / or color of the virtual content to match the environment depicted in the sensor data 230 and / or based on the orientation data 225 (for example, so that the lighting and / or color of the virtual object matches the real lighting of the real environment depicted in the sensor data 230).In some examples, the image synthesizer 245 may use the real-world object depicted in the sensor data 230 to obscure at least part of the virtual content if it determines (from the FOV of the sensor 210 of the media device 205) that a real-world object depicted in the sensor data 230 is in front of a location in the real environment depicted in the sensor data 230 where the image synthesizer 245 places the virtual content. For example, a person may appear to be walking "in front of" the virtual content, and the image synthesizer 245 may use that person to photorealistically obscure the view of the virtual content in the media data 250. An example of media data 250 containing virtual content is the digital asset 1040 in Figures 10A and 10B, which depict a virtual object 1045 (a virtual dog) superimposed on a real environment.

[0081] The media processor 235 may also include a map generator 247 that can generate one or more maps based on posture data 225 and / or sensor data 230. Such maps may identify one or more routes that the media device 205 has traveled over one or more periods of time. In some examples, the maps may show routes taken by a user carrying the media device 205, such as hiking routes, walking routes, jogging routes, running routes, cycling routes, skateboarding routes, public transport routes, driving routes, or routes traveled during sports activities. The media data 250 generated by the media processor 235 may include maps. For example, the digital asset 1140 in Figures 11A-11B is an example of media data 250 that includes maps generated by the map generator 247.

[0082] The media device 205 may include a communication interface 255, which may include one or more communication interfaces 1940. The communication interface 255 may include a short-range wireless transceiver 260. The short-range wireless transceiver 260 may receive and / or transmit communication 272 with the short-range wireless transceiver 275 of the local device 270 via one or more short-range communication signals in accordance with a short-range communication protocol. Either or both of the short-range wireless transceivers 260 and 275 may include, for example, Bluetooth® transceivers, Bluetooth® Low Energy (BLE) transceivers, iBeacon® transceivers, near-field communication (NFC) transceivers, radio frequency identification (RFID) transceivers, wireless transceivers, microwave transceivers, visible light communication (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, very low frequency transceivers, acoustic wave transceivers, any type of transceiver specified with respect to network transceivers 265 and 285, as well as other types of transceivers, or combinations thereof. In some examples, the media device 205 may receive and / or transmit one or more communications 272 with the local device 270 as part of capturing attitude data 225. For example, the local device 270 may have a verified location and may be a local device 270 installed and managed by a venue, such as a museum, concert hall, cinema, or stadium. The media device 205 is in close proximity to the local device 270 if the media device 205 and the local device 270 are within range of each other's short-range wireless communication signals (for example, within range of successful transmission and reception of one or more communications 272).

[0083] The local device 270 may determine and / or store communications 272 (block 277). For example, the local device 270 may determine and store the content of any communications 272 that the local device 270 sends to the media device 205. Similarly, the local device 270 may determine and store the content of any communications 272 that the local device 270 receives from the media device 205. The media device 205 may determine and / or store communications 272 (block 278). For example, the media device 205 may determine and store the content of any communications 272 that the media device 205 sends to the local device 270. Similarly, the media device 205 may determine and store the content of any communications 272 that the media device 205 receives from the local device 270. Ensuring that the stored contents of these communications 272 match those stored in the media device 205 and the local device 270 may be used to verify that the attitude of the media device 205 is within the geographic area associated with the local device 270 (block 290). In some examples, the media device 205 may transmit communications 272 to multiple local devices 270. In some examples, the local devices 270 may be known-location beacon devices. In some examples, the local devices 270 may be known-location wireless network access points (e.g., Wi-Fi, WLAN). In some examples, the local devices 270 may be known-location cellular network access points (e.g., cell towers).

[0084] The communication interface 255 of the media device 205 may include a network transceiver 265. The network transceiver 265 may receive and / or transmit communications 282 along the network to and / or from one or more network transceivers 285 of 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 specified with respect to short-range wireless transceivers 260 and 275, as well as other types of transceivers, or a combination thereof. The media device 205 may transmit media data 250 and / or attitude data 225 to the network device 280 via communications 282. The network device 280 may verify that the attitude of the media device 205 is within a geographical area (block 290). In some embodiments, the geographical area may be associated with a local device 270. For example, the local device 270 may be located within or adjacent to the geographical area. At least a portion of the geographical area may include the short-range wireless signal transmission and / or reception range of one or more local devices 270. In some examples, verifying that the attitude of the media device 205 is within a geographical area associated with a local device 270 (block 290) may include verifying that the contents of communication 272 match in the state stored in the local device 270 (block 277) and in the state stored in the media device 205 (block 278).For example, the content of a communication 272 sent from local device 270 to media device 205 matches what is stored in both devices (blocks 277 and 278), and / or the content of a communication 272 sent from media device 205 to local device 270 matches what is stored in both devices (blocks 277 and 278). In some examples, network device 280 may verify that the orientation of media device 205 is within a geographic area, at least in part, by verifying that the location of media device 205, indicated by orientation data 225, is within a predetermined boundary or geofence of a geographic area (block 290). In some examples, the geographic area may correspond to the interior of one or more structures corresponding to a museum, cinema, shopping mall, or another indoor venue. In some examples, the geographic area may correspond to the interior of an outdoor venue (e.g., an outdoor concert venue, an outdoor stadium) within, for example, a fence, wall, seating layout, or other boundary marker of the venue. In some examples, a geographical area may correspond to an outdoor area that includes one or more indoor areas, such as an outdoor food court with multiple restaurants, or an outdoor theme park with multiple attractions, some of which may be indoor attractions.

[0085] In some examples, the transmission and reception times of one or more communications 272 may be identified and / or stored (e.g., stored communications in block 277 and / or stored communications in block 278). In some examples, the transmission and reception times of one or more communications 272 may be used to identify the location of the media device 205 (e.g., as positioning data) and / or to verify that the attitude of the media device 205 is within a geographical area (block 290). For example, the transmission and reception times of one or more communications 272 may be subtracted to identify the length of time the communications 272 traveled, which may be used to determine the distance between the media device 205 and the local device 270.

[0086] In some examples, the signal frequencies of one or more transmits and received signals of one or more communications 272 may be identified and / or stored (e.g., stored communications in block 277 and / or stored communications in block 278). In some examples, the signal frequencies of one or more transmits and received signals of one or more communications 272 may be used to locate the media device 205 (e.g., as positioning data) and / or to verify that the attitude of the media device 205 is within a geographical area (block 290). For example, the signal frequencies of one or more transmits and received signals of one or more communications 272 may be subtracted to identify the difference in signal frequencies as communications 272 moves, which may be used to determine the distance between the media device 205 and the local device 270.

[0087] The location of the media device 205 may be determined as being along a circle drawn around a local device 270, having a radius of a distance determined (for example, based on the transmission and reception times, and / or based on the transmission and reception signal frequencies). The more local devices 270 used, the more precisely the location of the media device 205 may be determined based on the point where the resulting circles intersect. If three or more local devices 270 are used, the location of the media device 205 may be narrowed down to a single point, which may be called triangulation. Thus, triangulation based on signals from multiple local devices 270 may be used to determine the location of the media device 205 (for example, as positioning data) and / or to verify that the orientation of the media device 205 is within a geographical area (block 290).

[0088] In response to verifying that the media device 205's orientation is within a geographical area (block 290), the network device 280 may generate one or more tokens corresponding to the media data 250, generate one or more blocks in the distributed ledger 295 to store the tokens therein, and / or generate the 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 the distributed ledger 295 may include the blockchain ledger 500 and / or the directed acyclic graph (DAG) ledger 700. The network device 280 may store a copy of the distributed ledger 295. In some examples, the distributed network of other devices (in addition to the network device 280), such as the media device 205, the local device 270, and / or additional devices 297, may also store copies of the distributed ledger 295. In some examples, other devices in the decentralized network may also verify that the attitude of media device 205 is within a geographical area (block 290), verify that the token is valid, verify that the block is valid (for example, that the Merkle root accurately reflects the payload and the hash accurately reflects the previous block), or a combination of these. After generating the block and verifying its validity, the block may be added to the distributed ledger 295, and the block may be sent to other devices in the decentralized network to add the block to all copies of the distributed ledger 295.

[0089] In some examples, verifying that the orientation of media device 205 is within a geographical area (block 290) may also include receiving recorded audio information recorded by one or more microphones of media device 205 and comparing the recorded audio information with trusted audio information known to be from the geographical 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 local device 270. In an example for one explanation, media device 205 can capture images (example of sensor data 230) at a concert venue during a concert and simultaneously record audio clips of the audio at the concert. Network device 280 can receive the recorded audio clips from media device 205 along with media data 250 that includes and / or is based on the images. Network device 280 can also receive trusted audio clips from the concert and / or from local device 270 at the concert venue. Trusted audio clips may include audio from the same period as the recorded audio clips. A trusted audio clip may be recorded by one or more microphones of the local device 270 at the concert venue. A trusted audio clip may also be output by a speaker coupled to the local device 270 at the concert venue. The network device 280 can compare a recorded audio clip from the media device 205 with a trusted audio clip from the local device 270 to perform verification (block 290) that the media device 205 is located within a geographical area.If at least a portion of the recorded audio clip matches at least a portion of the trusted audio clip (for example, both audio clips play the same song from a concert), then the verification that media device 205 is located within a geographical area (block 290) is successful, meaning that the location of media device 205 is verified to be within a geographical area. If no portion of the recorded audio clip matches at least any portion of the trusted audio clip (or matches less than a certain threshold portion) (for example, the audio clip has no overlapping audio), then the verification that media device 205 is located within a geographical area (block 290) fails, meaning that the location of media device 205 is not verified to be within a geographical area, and / or, in some cases, the location of media device 205 may be verified to be outside a geographical area.

[0090] In some embodiments, several devices shown as separate devices in the digital asset tracking system 200 may be combined. In some examples, the local device 270 and the network device 280 may be combined. For example, part of communication 272 may include part of communication 282, and / or part of communication 282 may include part of communication 272. In some examples, the media device 205 and the network device 280 may be combined. For example, communication 282 may be located inside the media device 205. The media device 205 may verify itself that its position is within a geographical area (block 290). The media device 205 may generate one or more tokens corresponding to media data 250, generate one or more blocks in the distributed ledger 295 to store the tokens therein, and / or generate the distributed ledger 295 itself (block 292). In some examples, the media device 205 and the local device 270 may be combined. For example, media device 205 may have a known location within and / or near a geographic area, and / or may be associated with a geographic area (for example, owned, borrowed, or used by a venue corresponding to a geographic area), and may be a sensor-equipped concession stand device capable of verifying that its location is within a geographic area (block 290).

[0091] In some embodiments, several devices shown as a single device in the digital asset tracking system 200 may be divided into multiple devices. In some examples, these multiple devices may work together, for example, by transmitting data to each other. For example, the media device 205 may include more than one device. In an example for one explanation, the media device 205 may include a mobile handset (e.g., mobile handset 410), a head-mounted display (HMD) (e.g., HMD 310), a smartwatch, a pair of wireless headphones, a fitness tracker, another wearable device, or a combination thereof.

[0092] In some examples, the digital asset tracking system 200 may include a token device (not depicted 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, the 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 output devices such as a display and / or a speaker. The token device may output the digital asset associated with the token, for example, by displaying the visual content of the digital asset (e.g., images, videos) using the token device's display and / or by playing the audio content of the digital asset (e.g., sounds, music) using the token device's speaker. In some examples, the token device may be a physical representation of the token to which the token device is associated. An example of a token device is the token device 1405 in Figure 14.

[0093] In some examples, the digital asset tracking system 200 may include a data store 298. The data store 298 may include any type of data structure, including, for example, a data structure 650. In some examples, the data store 298 includes customization, personalization, and / or modification of a digital asset (e.g., digital asset 605) associated with a token (e.g., token 600). For example, in some examples, the digital asset may be immutable, but customization, personalization, and / or modification of the digital asset may be applied, removed, and / or modified. An example of a data store 298 used for customization, personalization, and / or modification of a digital asset is shown with respect to data store 1370 in Figure 13.

[0094] In some examples, the digital asset tracking system 200 may include an anchor element 299. In some examples, the anchor element 299 may include an object in the real-world environment related to the token. For example, detection of the anchor element 299 by the media device 205 using the sensor 210 can cause the media device 205 to output (e.g., display and / or play) the digital asset (e.g., digital asset 605) corresponding to the 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 barcode, an Aztec code, a dot code, a data matrix, a shot 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 can cause the media device 205 to output the digital asset corresponding to the token corresponding to the anchor element 299. In some examples, the anchor element 299 may include a specified position, and detection by the media device 205 using the sensor 210 that the media device 205 is located within a threshold range from the specified position can cause the media device 205 to output a digital asset corresponding to the token corresponding to the anchor element 299. In some examples, the token device may be the anchor element 299.

[0095] Figure 3A is a perspective view 300 showing a head-mounted display (HMD) used as a media device 205, which is part of a digital asset tracking system 200. The HMD 310 may be, for example, an augmented reality (AR) headset, a virtual reality (VR) headset, a mixed reality (MR) headset, an extended reality (XR) headset, or any combination thereof. The HMD 310 includes a first camera 330A and a second camera 330B on the front of the HMD 310. The first camera 330A and the second camera 330B (and / or their image sensors) may be examples of media sensors 220 of the media device 205. In some examples, the HMD 310 may have only a single camera with a single image sensor. In some examples, the HMD 310 may include one or more additional cameras in addition to the first camera 330A and the second camera 330B. One or more additional cameras (and / or their image sensors) may also be examples of media sensors 220 of the media device 205. In some examples, the HMD310 may include one or more additional sensors in addition to the first camera 330A and the second camera 330B, which may include other types of media sensors 220, attitude sensors 215 of the media device 205, and / or other sensors of the media device 205 as described herein.

[0096] The HMD310 may include one or more displays 340 visible to a user 320 wearing the HMD310 on their head. In some examples, the HMD310 may include one display 340 and two viewfinders. The two viewfinders may include a left viewfinder for the user 320's left eye and a right viewfinder for the user 320's right eye. The left viewfinder may be oriented so that the user 320's left eye looks at the left side of the display. The right viewfinder may be oriented so that the user 320's left eye looks at the right side of the display. In some examples, the HMD310 may include two displays 340, including a left display that shows content to the user 320's left eye and a right display that shows content to the user 320's right eye.

[0097] The HMD310 may include one or more earpieces 335, which may function as speakers and / or headphones that output audio to one or more ears of the user of the HMD310. Although one earpiece 335 is shown in Figures 3A and 3B, it should be understood that the HMD310 may include two earpieces, one for each ear of the user (left and right). In some examples, the HMD310 may also include one or more microphones (not shown). In some examples, the audio output to the user by the HMD310 through one or more earpieces 335 may include, or be based on, audio recorded using one or more microphones.

[0098] Figure 3B is a perspective view 350 showing the head-mounted display (HMD) of Figure 3A being worn by user 320. User 320 wears the HMD 310 on user 320's head, above user 320's eyes. The HMD 310 can capture images using a first camera 330A and a second camera 330B. In some examples, the HMD 310 displays one or more output images to user 320's eyes. The output images may include, for example, sensor data 230, media data 250, or both. The output images may be based on images captured by the first camera 330A and the second camera 330B. The output images may provide a stereoscopic view of the environment, along with potentially superimposed information and / or other modifications. For example, the HMD 310 may display a first display image to user 320's right eye, and the first display image is based on an image captured by the first camera 330A. The HMD310 can display a second display image to the user 320's left eye, and the second display image is based on an image captured by a second camera 330B. For example, the HMD310 may provide superposition information in the display image that is superimposed on the images captured by the first camera 330A and the second camera 330B. The earpiece 335 of the HMD310 is shown inside the user 320's ear. The HMD310 may output audio to the user 320 through the earpiece 335 and / or through another earpiece of the HMD310 (not shown) in the user 320's other ear (not shown).

[0099] Figure 4A is a perspective view 400 showing the front of a mobile handset 410, including a front camera, which may be used as a media device 205, part of a digital asset tracking system 200. The mobile handset 410 may be an example of the media device 205. The mobile handset 410 may be, for example, a mobile phone, satellite phone, portable game console, music player, health tracking device, wearable device, wireless communication device, laptop, mobile device, any other type of computing device or computing system discussed herein, or a combination thereof.

[0100] The front 420 of the mobile handset 410 includes a display 440. In some examples, the display 440 may display sensor data 230, media data 250, or both. The front 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 their image sensors) may be examples of media sensors 220 of the media device 205. The first camera 430A and the second camera 430B are shown within the bezel around the display 440 on the front 420 of the mobile handset 410. In some examples, the first camera 430A and the second camera 430B may be located within a notch or cutout removed from the display 440 on the front 420 of the mobile handset 410. In some examples, the first camera 430A and the second camera 430B may be under-display cameras positioned between the display 440 and the rest of the mobile handset 410, so 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 in the perspective view 400 are front cameras. The first camera 430A and the second camera 430B face in a direction perpendicular to the flat surface of the front 420 of the mobile handset 410. The first camera 430A and the second camera 430B may be two of one or more cameras of the mobile handset 410. The first camera 430A and the second camera 430B may be examples of media sensors 220 of the media device 205. In some examples, the front 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 their image sensors) may also be examples of media sensors 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 attitude sensors 215 of the media device 205. The front 420 of the mobile handset 410 also includes a display 440. In some cases, the front 420 of the mobile handset 410 includes one or more displays 440.

[0101] The mobile handset 410 may include one or more speakers 435A and / or other audio output devices (e.g., earphones or headphones or connectors to them) that can output audio to one or more ears of the user of the mobile handset 410. Although one speaker 435A is shown in Figure 4A, it should be understood that the mobile handset 410 may include one or more speakers and / or other audio devices. 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 one or more speakers 435A and / or other audio output devices may include, or be based on, audio recorded using one or more microphones.

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

[0103] 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 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 their image sensors) may also be examples of media sensors 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. One or more additional sensors may also be examples of other types of media sensors 220 and / or attitude sensors 215 of the media device 205.

[0104] The mobile handset 410 may include one or more speakers 435B and / or other audio output devices (e.g., earphones or headphones or connectors to them) that can output audio to one or more ears of the user of the mobile handset 410. Although one speaker 435B is shown in Figure 4B, it should be understood that the mobile handset 410 may include one or more speakers and / or other audio devices. 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 one or more speakers 435B and / or other audio output devices may include, or be based on, audio recorded using one or more microphones.

[0105] Figure 5 is a block diagram showing three consecutive blocks of blockchain ledger 500, which may be used to track digital assets related to locations within a geographic area, according to one aspect of this disclosure. Three blocks of blockchain ledger 500, including block A505, block B535, and block C565, are shown in Figure 5.

[0106] Each block contains a list of block headers 510 / 540 / 570 and one or more payloads 530 / 560 / 590. In some examples, block headers 510 / 540 / 570 contain hashes 515 / 545 / 575 of the previous block and / or hashes 515 / 545 / 575 of the block header of the previous block. For example, header 570 of block C565 contains hash 575 of header 540 of block B535. Header 540 of block B535 similarly contains hash 545 of header 510 of block A505. Header 510 of block A505 similarly contains hash 515 of the header (not depicted) of the previous block (not depicted) that precedes block A505 in blockchain ledger 500. Including the hash of the previous block's header secures the blockchain ledger 500 by preventing any modification of blocks in the blockchain ledger 500 after the block has been entered into the blockchain ledger 500, because any change to a particular block will render the hash 515 / 545 / 575 of the block header in the next block incorrect. Furthermore, any modification of the hash of the block header in the next block will render the hash 515 / 545 / 575 of the header of the next block in the block after the next block incorrect, and so on. A verification device can verify that a block has not been modified by calculating the hash of the block and / or the hash of the block header, and then comparing the calculated hash with the stored hash 515 / 545 / 575 stored in the next block. In some distributed ledgers, the block headers 510 / 540 / 570 may include hashes of multiple previous blocks and / or hashes of the block headers of multiple previous blocks, as shown in the directed acyclic graph (DAG) ledger 700 in Figure 7.

[0107] The block headers 510 / 540 / 570 of each block may contain Merkle roots 520 / 550 / 580. Merkle roots 520 / 550 / 580 may be generated based on the hashes of the tokens, transactions, smart contracts, and / or other elements identified in the payload 530 / 560 / 590 for that block. Any attempt to modify the payload after the block has been entered will alter the Merkle root. A verification device can verify that the payload 530 / 560 / 590 has not been modified by calculating the Merkle root and then comparing the calculated Merkle root with the stored Merkle roots 520 / 550 / 580 stored in the block headers 510 / 540 / 570. Changes to payloads 530 / 560 / 590 and / or Merkle roots 520 / 550 / 580 also change the hash for the block and / or block header, and the value for that is stored in the next block as hash 515 / 545 / 575. Each payload in each block may contain one or more tokens, one or more transactions, one or more smart contracts, other content, or a combination thereof.

[0108] The block header 510 / 540 / 570 of each block may also include various elements of metadata, such as the version number of the blockchain ledger platform, the version number of the block itself, a timestamp for the verification of each payload, a timestamp for the generation of the block, a timestamp for the input of the block into blockchain ledger 500, a timestamp for the request for block generation, a hardness target value (e.g., to adjust the mining difficulty), one or more randomized nonce values, a counter that identifies how many nonces have been attempted, the title of blockchain ledger 500, an identifier about what blockchain ledger 500 tracks (e.g., the history of digital assets 605 related to the location of a device in a certain geographical area), or a combination of these. Each additional individual element can further serve as information that can be verified by a verification device to determine whether the block and the payload within it are accurate and valid. One or more randomized nonce values ​​can serve to further complicate the hash and improve security.

[0109] Each block 505 / 535 / 565 of the 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 relating to any of the previously listed elements, or a combination thereof. For example, a token may be a non-fungible token. Token 600 may be an example of a token stored in the payload 530 / 560 / 590 for blocks 505 / 535 / 565. As discussed with respect to token 600, a portion of token 600 is stored in the payload 530 / 560 / 590 of the blockchain ledger 500 and is therefore stored "on-chain". As discussed with respect to token 600, a portion of token 600 includes an on-chain pointer that points to data outside the blockchain ledger 500, and such data is stored "off-chain". The payloads 530 / 560 / 590 of blockchain ledger 500 may store hashes of off-chain data, so a verification device can calculate a hash of the off-chain data and compare the calculated hash with the stored hash stored on-chain to verify that the off-chain data is accurate. In some examples, payloads 530 / 560 / 590 contain one or more smart contracts. The block may contain the code of the smart contracts stored in payloads 530 / 560 / 590 of blockchain ledger 500, so the code is stored on-chain. If payloads 530 / 560 / 590 contain smart contracts, the block may contain a hash of the smart contract code and / or a pointer to an off-chain data structure that stores the smart contract code, so the code is stored off-chain. In some examples, part of the smart contract code may be stored on-chain, while part of the smart contract code may be stored off-chain.In some examples, smart contracts may be used to create, modify, transfer, or otherwise manage tokens. In some examples, payloads 530 / 560 / 590 include a transaction. In some examples, the transaction may include the transfer of tokens from one account to another. In some examples, the transaction may include a change to any characteristic of the token or associated digital asset, such as a change to ownership, attributes, copyright, license, lease, or a combination thereof.

[0110] Figure 5 shows only three blocks 505 / 535 / 565 of blockchain ledger 500, but it should be understood that any blockchain ledger or distributed ledger discussed herein may be longer or shorter, and may have more or fewer than three blocks.

[0111] In one example for explanation, a first computing device can store a blockchain ledger containing multiple blocks. Each of the multiple computing devices (for example, in a decentralized architecture) also stores a copy of the blockchain ledger. The first computing device can receive a message that identifies an intended payload element (e.g., a token and / or a transaction and / or a smart contract). For example, the intended payload element may be a token relating to a digital asset (e.g., media data 250) associated with a location as described herein. The first computing device can verify that the intended payload element is valid. In some implementations of the blockchain ledger 500, the first computing device can verify that sufficient funds have been allocated to pay the execution fee for the intended payload element, for example, in the form of gas in the Ethereum blockchain ledger. For transactions such as token transfers, the first computing device can verify whether the transferor has a sufficient amount of assets to initiate the transaction (e.g., whether the transferor owns the tokens to be transferred). In a smart contract, the first computing device can verify that the smart contract references a valid account containing a sufficient amount of assets (e.g., tokens) to execute the smart contract (e.g., to transfer tokens), verify that the smart contract's code is executable (e.g., free from syntax errors or other errors), verify that all parties involved in the smart contract have agreed to the smart contract's terms, or a combination of these. For a given token, the first computing device can verify that the token references a valid digital asset, for example, a valid type of digital asset with a URI or other pointer that effectively points to the digital asset.

[0112] The first computing device can generate a hash of the most recent block or block header of the blockchain ledger 500. The first computing device can generate a new block header for a new block. The new block header may include at least a hash of the most recent block or block header of the blockchain ledger 500. The first computing device can generate a new block, which includes a new block header and a payload having one or more payload elements. The one or more payload elements may include at least the intended payload elements discussed above (e.g., tokens, smart contracts, transactions). The first computing device can generate a Merkle root based on the payload elements and include the Merkle root in the new block header. The first computing device can generate metadata and nonce values ​​based on the payload elements and include the metadata and nonce values ​​in the new block header. In response to verifying the intended payload elements, the first computing device can add the new block to multiple blocks of the blockchain ledger 500. In response to verifying the intended payload elements, the first computing device can send the new block to multiple computing devices, each storing the blockchain ledger 500. Each of the multiple computing devices also adds a new block to its respective copy of the blockchain ledger 500.

[0113] In an example for another explanation, a first computing device can store a blockchain ledger 500 containing multiple blocks. Each of the multiple computing devices (for example, in a decentralized architecture) also stores a copy of the blockchain ledger 500. The first computing device can receive a UI input that identifies the intended payload elements (e.g., a transaction and / or a smart contract). The first computing device can generate a message that identifies the intended payload elements. The first computing device can retrieve a private key associated with the account corresponding to the first computing device. The first computing device can modify a message by encrypting at least a portion of it with the private key. The first computing device can send a message to multiple computing devices other than the first computing device. A second computing device of the multiple computing devices verifies that the intended payload elements are valid, for example, as described in the previous paragraph. The first computing device receives a new block from the second computing device. The new block identifies and / or includes the intended payload elements (e.g., in its payload). The first computing device adds a new block to multiple blocks of blockchain ledger 500 on the first computing device.

[0114] Figure 6 is a block diagram showing an exemplary token 600 that may be nonfungible, which can represent a digital asset 605 associated with a location in a geographic area, such as one tracked on a distributed ledger. In some examples, token 600 is a nonfungible 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 on a blockchain ledger 500. In some examples, token 600 is tracked on an Ethereum-based blockchain ledger 500. In some examples, token 600 is tracked on a directed acyclic graph (DAG) ledger 700.

[0115] The digital asset 605 represented by token 600 may be an example of media data 250 from the media device 205 of the digital asset tracking system 200 in Figure 2. As discussed with respect to the digital asset tracking system 200 in Figure 2, the media data 250, and therefore the digital asset 605, may include one or more images, videos, audio clips, 3D point clouds, 3D models, sensor data 230, pose data 225, metadata related to the sensor data 230, metadata related to the pose 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 3D reconstructions based on 3D point clouds, such as a section of a forest, a section of a celebrity's house, a historical location, or a 3D reconstruction of a national park.

[0116] One or more token smart contracts 645 may be associated with token 600. For example, one or more token smart contracts 645 may manage the creation (or "minting") of token 600. One or more token smart contracts 645 may pay token 600, or a miner device that creates ("mints") batches of tokens, for calculating the time and resources required to mint token 600. One or more token smart contracts 645 may include conditions that must be met before the creation (minting) of token 600 can be successful. For example, one such condition may require that, at the same time as and / or during the capture of sensor data 230 corresponding to media data 250 of the digital asset 605, verification (e.g., block 290 in Figure 2) that the media device 205 was within a geographical area must be successfully performed by one or more verification devices (e.g., at least a threshold number of verification devices, such as the minimum number (quorum) in Figures 15A-15B) to allow the creation (minting) of the token 600. One or more token smart contracts 645 can control how ownership of the token 600 is determined and / or transferred. For example, one or more token smart contracts 645 can indicate initial ownership of the token 600 and / or specify conditions under which ownership is automatically transferred, such as when an offer meets or exceeds a threshold amount that can be modified by the owner. One or more token smart contracts 645 can indicate that the tokens 600 may be lent or licensed for temporary use or ownership by licensed users, for example, that the offer meets or exceeds a threshold amount that can be modified by the owner. One or more token smart contracts 645 can control the conditions under which the tokens 600 may be destroyed (for example, irreversibly destroyed and / or deleted).Elements identified as part of token 600 in Figure 6, including token identifier 610, token unit amount 615, token ownership 620, on-chain immutable metadata 625, on-chain mutable metadata 630, on-chain pointer to off-chain media 635, and on-chain pointer to off-chain metadata 640, may be stored as part of token 600, as part of token smart contract 645, or both. In some examples, the code of token smart contract 645 is stored at least partially on-chain. In some examples, the code of token smart contract 645 is stored off-chain at least partially in an off-chain location such as a data structure 650, and the off-chain location is identified by an on-chain pointer to the off-chain location.

[0117] Token 600 includes a token identifier 610, sometimes also called a tokenID. The token identifier 610 may be a unique identifier for token 600 and / or digital asset 605. The token identifier 610 may be used to distinguish a particular instance of digital asset 605 for which token 600 corresponds from any other instance of digital asset 605. In some examples, the token identifier may be created by the computing system creating (or "minting") token 600 by sequentially incrementing it by comparison with the token identifiers of previously created tokens to ensure that each token identifier is unique.

[0118] Token 600 may contain a token unit amount 615. The token unit amount 615 can identify the amount of token 600 that has been minted or is scheduled to be minted. In some examples, the token unit amount 615 is 1, in which case a single token 600 exists for a given digital asset 605. In some examples, the token unit amount 615 is greater than 1. For example, if the token unit amount 615 is 5, there are essentially five copies of this token 600 representing this single digital asset 605 that can be owned and / or transferred separately. In some examples, each of those five copies may correspond to a separate token. In some examples, all five copies may be represented by a single token. In some examples, those five copies may be interchangeable with one another, or they may be indistinguishable from one another. However, those five copies are still ininterchangeable, unique, distinct, and / or distinguishable with respect to any other instance, version, or variation of the digital asset 605. In some examples, the five copies are still distinguishable from one another by a corresponding token 600 for each copy, which includes an identifier (on-chain or off-chain) indicating which of the five copies the copy is (e.g., 1st, 2nd, 3rd, 4th, or 5th). The token unit amount 615 can control how rare token 600 is, and as an extension, how rare digital asset 605 is. If the token unit amount 615 is 1, token 600 and the corresponding digital asset 605 are unique. If the token unit amount 615 is greater than 1 but below the scarcity threshold, token 600 and the corresponding digital asset 605 are rare. If the token unit amount 615 is greater than 1 and above the scarcity threshold, token 600 and the corresponding digital asset 605 are common. In some examples, in addition to unique, rare, and common, or instead, there may be any number of scarcity ranges, such as legendary, very rare, slightly rare, not rare, and other classifications of scarcity.In some cases, the token unit amount 615 may be determined as part of the minting process and / or specified in one of the token smart contracts 645 that manages the minting process.

[0119] Token 600 may also identify token ownership 620, which may identify who owns token 600 and, as an extension, the corresponding digital asset 605. In some examples, token ownership 620 may first be assigned to an account associated with the creator of digital asset 605, such as a user associated with a media device 205 that ingested, acquired, or generated the media data 250 of digital asset 605. The user associated with media device 205 may also be the user who owns media device 205. The user associated with media device 205 may be the user who was using media device 205 when media device 205 ingested sensor data 230 and / or attitude data 225 associated with digital asset 605, the user who was using media device 205 when media device 205 ingested, acquired, or generated the media data 250 of digital asset 605, or a combination of these. In some examples, token ownership 620 may first be assigned to an account associated with an individual depicted or represented in the media data 250 of the digital asset 605, such as user Bob 945 in Figures 9A-9B. The token smart contract 645 can control the rules for the transfer of token ownership 620. Token ownership 620 may be transferred as a transaction recorded as a payload element in the payload of a block on a blockchain ledger or other distributed ledger.

[0120] Token 600 may include on-chain immutable metadata 625. On-chain immutable metadata 625 may include, for example, a description of token 600, a description of the digital asset 605 that token 600 represents, any immutable attributes or properties of the digital asset 605 and / or token 600, or any combination thereof. On-chain immutable metadata 625 may use the properties of the distributed ledger and / or the properties of the token smart contract 645 to ensure that the on-chain immutable metadata 625 remains unchanged. In some examples, on-chain immutable metadata 625 may identify a media device 205 that ingested, retrieved, or generated the media data 250 of the digital asset 605. In some examples, on-chain immutable metadata 625 may identify the category of media contained in the digital asset 605 (e.g., images, videos, audio clips, 3D point clouds, 3D models, maps, etc.). In some examples, the on-chain immutable metadata 625 can identify the location or orientation of the media device 205 at the same time as and / or during the acquisition of sensor data 230 associated with the digital asset 605. In some examples, the on-chain immutable metadata 625 can identify a geographical area.

[0121] Token 600 may include on-chain mutable metadata 630. On-chain mutable metadata 630 may include, for example, a description of token 600, a description of the digital asset 605 represented by token 600, any immutable attributes or properties of digital asset 605 and / or token 600, or any combination thereof. On-chain mutable metadata 630 may be mutable or modifiable. In some examples, changes to on-chain mutable metadata 630 may be recorded as transactions recorded as payload elements in the payload of a block on a blockchain ledger or other distributed ledger. In some examples, on-chain immutable metadata 625 may identify how many times digital asset 605 has been viewed, replayed, accessed, or used in a specified manner.

[0122] Token 600 may include an on-chain pointer to off-chain media 635. Off-chain media may include digital asset 605 and / or one or more representations of digital asset 605. For example, off-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 lot of storage space for storage, so storing them on-chain may be expensive in terms of fees (such as gas on the Ethereum blockchain ledger). Therefore, it may be more efficient to store this media off-chain at one or more off-chain locations, such as data structure 650. On-chain pointers may include uniform resource identifiers (URIs), such as uniform resource locators (URLs), that point to one or more network locations of one or more off-chain locations. In some examples, hashes may be stored from off-chain media so that a verification device can calculate a hash of the off-chain media and compare the calculated hash with a stored hash stored on-chain to verify that the off-chain media is accurate. In some examples, off-chain media may be immutable. In some examples, off-chain media may be mutable. In some examples, pointers may be immutable. In some examples, pointers may be mutable.

[0123] Token 600 may include an on-chain pointer to off-chain metadata 640. Off-chain metadata 630 may include, for example, a description of token 600, a description of the digital asset 605 that token 600 represents, any immutable attributes or properties of digital asset 605 and / or token 600, or any combination thereof. Some digital assets 605 and / or token 600 may require a large amount of metadata, which may require a lot of storage space for storage, and therefore may be expensive to store on-chain in terms of fees (such as gas on the Ethereum blockchain ledger). Therefore, it may be more efficient to store this metadata off-chain in one or more off-chain locations, such as data structure 650. On-chain pointers may include uniform resource identifiers (URIs), such as uniform resource locators (URLs), that point to one or more network locations of one or more off-chain locations. In some cases, hashes can be stored from off-chain metadata, so a verification device can calculate a hash of the off-chain metadata and compare the calculated hash with a stored hash stored on-chain to verify that the off-chain metadata is accurate. In some cases, off-chain metadata may be immutable. In some cases, off-chain metadata may be mutable. In some cases, pointers may be immutable. In some cases, pointers may be mutable.

[0124] Figure 7 is a block diagram showing a directed acyclic graph (DAG) ledger 700 configured to track digital assets related to locations within a geographic area, according to an aspect of this disclosure. While Figure 5 discusses the use of a blockchain ledger 500, it should be understood that nonlinear ledger structures, such as the directed acyclic graph (DAG) ledger structure of Figure 7, may be used instead of, or in addition to, the blockchain ledger 500 discussed herein. The term “distributed ledger” as used herein should be understood to refer to at least one of the blockchain ledger 500 (as in Figure 5), the DAG ledger 700 (as in Figure 7), or a combination thereof. In a DAG ledger, each block header contains hashes of blocks or block headers of a predetermined number of other “parent” blocks in the DAG ledger, selected randomly or in some other nonlinear manner, rather than hashes of a single previous block in the blockchain. If each block header contains hashes of different parent blocks or their headers, these hashes may be combined together (for example, using Merkle roots).

[0125] For example, in the DAG ledger of Figure 7, the predetermined number is 2, and at least the first two blocks are generated. In the web DAG ledger of Figure 7, parent blocks are indicated using arrows. Block 710 contains hashes of the block headers of parent blocks 720 and 750. Block 720 contains hashes of the block headers of parent blocks 740 and 760. Block 730 contains hashes of the block headers of parent blocks 720 and 760. Block 740 contains hashes of the block headers of parent blocks 710 and 730. Block 750 contains hashes of the block headers of parent blocks 710 and 720. Block 760 contains hashes of the block headers of parent blocks 710 and 750. The resulting structure is a directed acyclic graph (DAG) of blocks, where each vertex block contains a hash of its parent vertex block, rather than a linear stream of blocks as in a blockchain. DAG ledgers are sometimes called "web," "tangle," or "hash graph."

[0126] 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 minimum of two parents or a minimum of one parent, meaning that each block has at least a predetermined number of parent blocks. In some cases, each block in the DAG ledger may identify only a single payload element (e.g., token 600) rather than multiple payload elements, and therefore the Merkle roots 520 / 350 / 380 of the payload elements may be omitted and / or replaced with a hash of the single payload element. In other implementations, each block may identify multiple payload elements related to a predetermined period and / or include the Merkle roots 520 / 350 / 380 of the payload elements. In some examples, the DAG ledger 700 may offer advantages over the blockchain ledger 500 by providing parallelized validation, which can result in higher throughput.

[0127] Figure 8A is a perspective view 800 showing user 805 using media device 810 to capture digital asset 840 (image), which is a portrait inside a museum. Media device 810 captures the digital asset 840 using its image sensor 815, while the portrait (Mona Lisa) inside the museum (Louvre Museum) is within the field of view (FOV) 825 of media device 810's image sensor 815. Media device 810 may be an example of media device 205. The image sensor 815 of media device 810 may be an example of media sensor 220 of media device 205. Media device 810 may generate positioning data using its positioning sensor 820 at the same time as, and / or during, the capture of the image corresponding to the digital asset 840 by the image sensor 815. The positioning sensor 820 may be an example of attitude sensor 215. The positioning data may be an example of attitude data 225. The media device 810 may communicate with a local device 830 located within a geographic area (for example, inside a museum) or in the vicinity of a geographic area (for example, near a museum). The media device 810 may send and / or receive one or more communications 835 to and from the local device 830. The local device 830 may be an example of the local device 270. The communications 835 may be examples of communications 272. In some examples, the local device 830 may be a beacon.

[0128] In Figure 8A, the media device 810 is shown as a mobile handset 410, but in some examples, the media device 810 may be a media device 810 with a geographical area and / or geographically fixed to that geographical area. For example, the media device 810 may be a shop device geographically fixed to the Louvre Museum, from which a user 805 can approach and use to acquire digital assets 840. In this case, such a media device 810 can self-verify that it is located within a geographical area, for example, because the media device 810 is geographically fixed to that geographical area.

[0129] Figure 8B is a conceptual diagram 850 showing information 855 about token 860 related to digital asset 840 in Figure 8A. Token 860 may be an example of token 600. Information 855 may be partially identified in token 860 itself (e.g., as token identifier 610, on-chain immutable metadata 625, on-chain mutable 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 title 865, which is shown as "Look at the Mona Lisa!". Information 855 about token 860 includes a copy of digital asset 840 (e.g., retrieved using an on-chain pointer from token 860 to off-chain media 635). Information 855 about token 860 identifies the digital asset type 870 of digital asset 840 as an image. Information 855 about token 860 includes metadata 875 related to the incorporation of digital asset 840, which is a clip icon (indicating that clicking the clip icon will reveal metadata 875).

[0130] Information 855 about token 860 includes history 880. In some examples, each element of history 880 is identified as a payload element in a distributed ledger block that stores token 860. History 880 indicates that on 24 May 2021, at 2:03:36 p.m., while the positioning sensor 920 of media device 810 indicates that the orientation of media device 810 is facing north inside the Louvre Museum, and while media device 810 and local device 830 are within communication range (based on communication 835) inside the Louvre Museum, digital asset 840 is captured by user 805 using media device 810. History 880 indicates that on 26 May 2021, at 6:40:01 a.m., server 885 mints token 860 based on digital asset 840 whose ownership is set to user 805, after verifying that media device 810 was in the Louvre Museum during capture (for example, via object recognition and / or by verifying that data from positioning sensor 820 matches a known geographic area of ​​the Louvre Museum and / or by verifying communication in communication 835). Server 885 may be an example of network device 280. History 880 indicates that on 28 March 2021, at 1:22:54 p.m., ownership of token 860 is transferred from user 805 to user 890 after user 890 purchases token 860 from user 805.

[0131] In some examples, the venue may allow venue attendees to capture a limited amount of digital assets for which a network device 280 associated with the venue can mint tokens 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 example, tokens to be generated by five of the user’s images in the venue) for a certain number of images (or other digital assets) captured by users in the venue. The generation of tokens for such images can use the reputation of the token minter (venue and the network device 280 associated with the venue) to help a user prove that they were actually in the venue at a given date and time, for example, to prove that a user was at a particular concert, sporting event, movie screening, etc. The generation of tokens for such images can use the reputation of the token minter (venue and the network device 280 associated with the venue) to help a user prove that they were in a particular section of the venue (for example, a particular seat). In some cases, verification that the media device 205 was in a geographical area (e.g., a venue) at the same time as and / or during the capture of sensor data 230 related to the media data 250 of the digital asset may include cross-referencing the user's identity with a ticket to the venue and / or a specific section of the venue (e.g., a specific seat or section of seating). In some examples, a token for an image (or other media) captured from a seat or location within the venue (e.g., a front-row seat) may be more valuable than a token for an image (or other media) captured from another seat or location within the venue (e.g., a far-off seat or a "top floor" seat). In some examples, the geographical area may be a specific part of the venue, such as a specific seat or section of seating.

[0132] Figure 9A is a perspective view 900 showing a user 905 using a media device 910 to capture digital assets 940 (images) of several people, including an individual identified as Bob 945. The media device 910 captures the digital assets 940 using its image sensor 915 while the people, including Bob 945, are within the field of view (FOV) 925 of the image sensor 915 of the media device 910. The media device 910 may be an example of a media device 205. The image sensor 915 of the media device 910 may be an example of a media sensor 220 of a media device 205. The media device 910 may generate positioning data using its positioning sensor 920 at the same time as, and / or during, the capture of images corresponding to the digital assets 940 by the image sensor 915. The positioning sensor 920 may be an example of an attitude sensor 215. The positioning data may be an example of attitude data 225. Media device 910 may communicate with local device 930 located within or near a geographical area. Local device 930 may be, for example, Bob's device. In the context of Figures 9A and 9B, the geographical area may be near the people depicted in digital asset 940, including Bob 945. Verification that media device 910 is within a geographical area may help verify that the people depicted in digital asset 940 are indeed Bob 845 and other depicted people. Media device 910 may send and / or receive one or more communications 935 to and from local device 930. Local device 930 may be an example of local device 270. Communications 935 may be an example of communications 272.

[0133] Figure 9B is a conceptual diagram 950 showing information 955 about token 960 related to digital asset 940 in Figure 9A. Token 960 may be an example of token 600. Information 955 may be partially identified in token 960 itself (e.g., as token identifier 610, on-chain immutable metadata 625, on-chain mutable 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, which is shown as "The guys are here!". Information 955 about token 960 includes a copy of digital asset 940 (e.g., retrieved using an on-chain pointer from token 960 to off-chain media 635). Information 955 about token 960 identifies the digital asset type 970 of digital asset 940 as an image. Information 955 about token 960 includes metadata 975 related to the incorporation of digital asset 940. Metadata 975 is represented by a clip icon (indicating that clicking the clip icon will reveal metadata 975).

[0134] Information 955 about token 960 includes history 980. In some examples, each element of history 980 is identified as a payload element in a distributed ledger block that stores token 960. History 980 indicates that on 24 May 2021, at 2:03:36 p.m., while the positioning sensor 920 of media device 910 indicates that the orientation of media device 910 is near Bob's device 930, and while media device 910 and Bob's device 930 are within communication range (communication 935), digital asset 940 is captured by user 905 using media device 910. History 980 indicates that on 26 May 2021, at 6:40:01 a.m., server 985 mints token 960 based on digital asset 940, with ownership set to Bob945, after verifying (for example, via facial recognition and / or via verification of data from positioning sensor 920 near Bob's device 930 and / or by verifying communications 935) that Bob945 is depicted in digital asset 940. Server 985 may be an example of network device 280. History 980 indicates that on 28 March 2021, at 1:22:54 p.m., ownership of token 960 is transferred from Bob945 to user 990 after user 990 purchases token 960 from Bob945.

[0135] In some examples, one or more tokens 960 may be minted by a server 985 corresponding to a digital asset 940. For example, the server 985 may mint one or more tokens 960 so that a user 905 who has taken in the digital asset 940 may own one of the tokens 960, so that each of the people identified in the digital asset 940 (including Bob 945, as identified in information 955) may own one of the tokens 960.

[0136] Figure 10A is a perspective view 1000 showing a user 1005 using a media device 1010 to generate a digital asset 1040 (image) that includes a virtual object 1045 which is then composited onto a real-world landscape. The media device 1010 captures the digital asset 1040 using the image sensor 1015 of the media device 1010 while the virtual object 1045 (a virtual dog) in a geographic area (a park) is within 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, for example, as part of a video game in which different virtual objects appear in different geographic areas, so the user 1005 may wander to different geographic areas to "catch," meet, or otherwise encounter different virtual objects 1045 (for example, different virtual pets). The media device 1010 may be an example of a media device 205. The image sensor 1015 of media device 1010 may be an example of the media sensor 220 of media device 205. Media device 1010 may generate positioning data using the positioning sensor 1020 at the same time as, and / or during, the acquisition of an image of the park corresponding to the digital asset 1040 by the image sensor 1015. A virtual object 1045 may be generated (for example, via a virtual content generator 240) and added to the image of the park (for example, via an image synthesizer 245). The positioning sensor 1020 may be an example of an attitude sensor 215. The positioning data may be an example of an attitude data 225. Media device 1010 may communicate with a local device 1030 located within a geographical area (for example, inside a museum) or in the vicinity of a geographical area (for example, near a museum). Media device 1010 may send and / or receive one or more communications 1035 to and / or from the local device 1030. The local device 1030 may be an example of a local device 270. Communication 1035 may be an example of communication 272.

[0137] Figure 10B is a conceptual diagram 1050 showing information 1055 about token 1060 related to digital asset 1040 in Figure 10A. Token 1060 may be an example of token 600. Information 1055 may be partially identified in token 1060 itself (e.g., as token identifier 610, on-chain immutable metadata 625, on-chain mutable 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, which is shown as "Just met my virtual pet, Sparky!". Information 1055 about token 1060 includes a copy of digital asset 1040 (e.g., retrieved using an on-chain pointer to the off-chain media 635 of token 1060). Information 1055 about token 1060 identifies the digital asset type 1070 of digital asset 1040 as an image. Information 1055 about token 1060 includes metadata 1075 related to the ingestion of digital asset 1040, which is a clip icon (indicating that clicking the clip icon will reveal metadata 1075).

[0138] Information 1055 about token 1060 includes history 1080. In some examples, each element of history 1080 is identified as a payload element in a distributed ledger block that stores token 1060. History 1080 indicates that on 24 May 2021, at 2:03:36 p.m., while the positioning sensor 1020 of media device 1010 indicates that the orientation of media device 1010 is facing north in the park, and while media device 1010 and local device 1030 are within communication range (communication 1035) in the park, digital asset 1040 was captured and / or generated by user 1005 using media device 1010. As indicated, the park includes real objects 1047 (e.g., trees and / or other objects). History 1080 indicates that on 26 May 2021, at 6:40:01 a.m., the media device 1010 verified (for example, by verifying that the data from the positioning sensor 1020 matches the geographic data and / or by verifying the communication 1035) that the virtual object 1045 appeared in the geographic area during capture, and that the server 1085 minted token 1060 based on the digital asset 1040 whose ownership is set to user 1005. Server 1085 may be an example of network device 280. History 1080 indicates that on 28 March 2021, at 1:22:54 p.m., ownership of token 1060 is transferred from user 1005 to user 1090 after user 1090 purchases token 1060 from user 1005.

[0139] In some examples, the generation of virtual object 1045 and / or associated token 1060 may be part of a video game and may be driven by a scarcity function that takes into account factors such as the number of users (number of users of the video game), the location of users (geographic distribution of users of the video game), market transaction history (recent transfers of virtual object 1045 and / or associated token 1060 (indicating user base interest)), user engagement (time spent playing the video game per user), or a combination thereof.

[0140] Figure 11A is a perspective view 1100 showing a user 1105 using a media device 1110 to generate a digital asset 1140 (map) of hiking trails. The media device 1110 uses its positioning sensor 1120 to acquire sensor data. The sensor data may be an example of attitude data 225 and / or sensor data 230. The positioning sensor 1120 may be an example of an attitude sensor 215 and / or media sensor 220. The media device 1110 may use a map generator 247 to generate the digital asset 1140 (map) of hiking trails. At least some of the sensor data may be acquired by the positioning sensor 1120 while the media device 1110 is in a geographical area (for example, a park in which the hiking trails are located).

[0141] The media device 1110 may communicate with a local device 1130 located within a geographical area (for example, inside a museum) or in the vicinity of a geographical area (for example, near a museum). The media device 1110 may send and / or receive one or more communications 1135 to and from the local device 1130. The local device 1130 may be an example of a local device 270. The communications 1135 may be an example of a communications 272.

[0142] Figure 11B is a conceptual diagram 1150 showing information 1155 about token 1160 related to the digital asset 1140 in Figure 11A. Token 1160 may be an example of token 600. The information 1155 may be partially identified in token 1160 itself (for example, as token identifier 610, on-chain immutable metadata 625, on-chain mutable metadata 630, off-chain media 635, off-chain metadata 640, rules of one or more smart contracts 645, or a combination thereof). The information 1155 about token 1160 includes a title 1165, which is shown as "Look at the Mona Lisa!". The information 1155 about token 1160 includes a copy of the digital asset 1140 (for example, retrieved using an on-chain pointer to the off-chain media 635 of token 1160). Information 1155 about token 1160 identifies the digital asset type 1170 of digital asset 1140 as an image. Information 1155 about token 1160 includes metadata 1175 related to the ingestion of digital asset 1140, which is a clip icon (indicating that clicking the clip icon will reveal the metadata 1175).

[0143] Information 1155 about token 1160 includes history 1180. In some examples, each element of history 1180 is identified as a payload element in a distributed ledger block that stores token 1160. History 1180 indicates that on 24 May 2021, at 2:03:36 p.m., while the positioning sensor 920 of media device 1110 indicates that the orientation of media device 1110 is facing west in the park, and while media device 1110 and local device 1130 (e.g., beacon) are within communication range (communication 1135) in the park, digital asset 1140 is captured / generated by user 1105 using media device 1110. History 1180 indicates that on 26 May 2021, at 6:40:01 a.m., server 1185 mints token 1160 based on digital asset 1140 whose ownership is set to user 1105, after verifying that media device 1110 was in the park during the capture (for example, by verifying that data from positioning sensor 1120 matches the park and / or by verifying communication 1135). Server 1185 may be an example of network device 280. History 1180 indicates that on 28 March 2021, at 1:22:54 p.m., ownership of token 1160 is transferred from user 1105 to user 1190 after user 1190 purchases token 1160 from user 1105.

[0144] In some examples, additional information may need to be verified (e.g., by one or more smart contracts 645) (e.g., by the network device 280) before the network device 280 can mint tokens corresponding to a particular digital asset. For example, in addition to verifying that the media device was geographically located, additional information that may need to be verified may include fitness or activity results (e.g., steps, calories burned, first runner on a new trail), level of difficulty of the result (e.g., steps on a steep mountain vs. steps on flat ground), personal records, local records, world records, or a combination of these. This information may be based on posture data 225, positioning data, fitness app data, health app data, fitness tracker data, wearable device data, etc.

[0145] Figure 12A is a perspective view 1200 showing user 1205 using ownership device 1210 to purchase digital asset 1240 (image), which is a portrait in a museum. Ownership device 1210 displays a purchase user interface with a "Purchase" button 1245. By pressing the purchase button 1245, ownership device 1210 makes it possible to purchase existing tokens 1260 for digital asset 1240 or to request the creation (minting) of new tokens 1260 for digital asset 1240. Digital asset 1240 may be captured by one or more sensors of a media device (for example, 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 separate from the media device that captures digital asset 1240. For example, the media device that captures digital asset 1240 may be media device 810 in Figure 8A. The ownership device 1210 may include a positioning sensor 1220. The ownership device 1210 may use its positioning sensor 1220 to generate positioning data. The positioning sensor 1220 may be an example of an attitude sensor 215. The positioning data may be an example of attitude data 225. The ownership device 1210 may communicate with a local device 1230 located within a geographical area (e.g., inside a museum) or in the vicinity of a geographical area (e.g., near a museum). The ownership device 1210 may send and / or receive one or more communications 1235 to and / or from the local device 1230. The local device 1230 may be an example of a local device 270. The communications 1235 may be an example of a communications 272. In some examples, the ownership device 1210 may be offered to purchase ownership (and / or create / mint) of token 1260 only if the ownership device 1210 is verified to be located within a geographical area (e.g., inside the Louvre Museum).In some examples, ownership device 1210 may only be able to become the owner of token 1260 (and / or cause its creation / minting) if ownership device 1210 is verified to be located within a geographical area (for example, inside the Louvre Museum).

[0146] Figure 12B is a conceptual diagram 1250 showing information 1255 about token 1260 related to digital asset 1240 in Figure 12A. Token 1260 could be an example of token 600. Information 1255 can be partially identified in token 1260 itself (for example, as token identifier 610, on-chain immutable metadata 625, on-chain mutable metadata 630, off-chain media 635, off-chain metadata 640, rules of one or more smart contracts 645, or a combination thereof). Information 1255 about token 1260 includes a title 1265, which is shown as "Louvre Official Digital Mona Lisa". Information 1255 about token 1260 includes a copy of digital asset 1240 (for example, retrieved using an on-chain pointer to the off-chain media 635 of token 1260). Information 1255 about token 1260 identifies the digital asset type 1270 of digital asset 1240 as an image. Information 1255 about token 1260 includes metadata 1275 related to the ingestion of digital asset 1240. Metadata 1275 is represented by a clip icon (indicating that clicking the clip icon will reveal the metadata 1275).

[0147] Information 1255 about token 1260 includes history 1280. In some examples, each element of history 1280 is identified as a payload element in a distributed ledger block that stores token 1260. History 1280 indicates that on 24 May 2021, at 2:03:36 p.m., while the media device's positioning sensor indicates that the media device's orientation is facing north inside the Louvre Museum, and while the media device and local device 1230 are within communication range inside the Louvre Museum, the digital asset 1240 is captured by the media device. History 1280 indicates that on 26 May 2021, at 6:40:01 a.m., server 1285 mints token 1260 based on digital asset 1240, which is owned by user 1205, after verifying that ownership device 1210 was in the Louvre Museum during the request for digital asset 1240 (for example, by verifying that data from positioning sensor 1220 matches the Louvre Museum and / or verifying communication 1235), and / or verifying that media device was in the Louvre Museum during the ingestion of digital asset 1240. Server 1285 may be an example of network device 280. History 1280 indicates that on 28 March 2021, at 1:22:54 p.m., ownership of token 1260 is transferred from user 1205 to user 1290 after user 1290 purchases token 1260 from user 1205.

[0148] In some examples, the user interface of the ownership device 1210 (with a purchase button 1245) may select which digital assets 1240 and / or associated tokens 1260 are available for the same thing, based on factors such as credentials (using a specific app to find specific content based on scene information, or specifying NFT content for viewing or purchase by a selected user), user selection, user filtering, crowdsourced feedback (number of views, likes, comments, requests, etc.), and / or learned user behavior (behavioral learning using machine learning algorithms, for example).

[0149] In some examples, the tracked history of tokens such as history 880, 980, 1080, 1180, and 1280 may track a chain of management 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, a user may view the history and / or chain of management of several tokens. For example, a visitor to a museum (e.g., the Louvre Museum) may be interested in viewing the history and / or chain of management of official tokens for a digital copy of a particular work of art in the museum (e.g., an official digital copy of the Mona Lisa portrait created by museum staff).

[0150] Figure 13 is a conceptual diagram 1300 showing an anchor element 1350 associated with token 1360, and that detection of the anchor element 1350 by the media device 1310 triggers the display of the digital asset 1340 corresponding to the token on the media device 1310. The anchor element 1350 may be an example of the anchor element 299 in Figure 2. The anchor element 1350 is represented as an optical glyph, specifically a QR code. In some examples, the optical glyph of the anchor element 1350 may include a QR code, barcode, Aztec code, dot code, data matrix, shot code, or a combination thereof. Other real-world objects 1347 (e.g., a tree) are also shown. In some examples, the optical glyph may optionally optically encode information identifying token 1360, information about token 1360, information indicating token 1360, or a combination thereof. The media device 1310 uses its image sensor 1315 to detect the optical glyph of the anchor element 1350. In some examples, the media device 1310 uses its image sensor 1315 to scan the optical glyph of the anchor element 1350 and decode the information optically encoded in the optical glyph of the anchor element 1350. Based on this information, the media device 1310 determines that the anchor element 1350 is associated with a token 1360 (e.g., token 600) stored in a distributed ledger 1365 (e.g., blockchain ledger 500 and / or DAG ledger 700).

[0151] The media device 1310 determines that token 1360 is associated with digital asset 1340 based on the information it decrypts about token 1360 from anchor element 1350 and / or based on the information it reads about token 1360 in distributed ledger 1365. In the example shown in Figure 13, digital asset 1340 is virtual object 1345, which is shown as a virtual dog, similar to virtual object 1045 in Figure 10A. The media device 1310 displays digital asset 1340 (for example, virtual object 1345) on its display. The media device 1310 can also display information 1355 about token 1360 associated with digital asset 1340. For example, information 1355 may include the ownership of token 1360 (e.g., the name of the owner of token 1360 or any other identifier of the owner), the identifier and / or type of the distributed ledger 1365 on which token 1360 is minted (e.g., Ethereum®, Cardano®, distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledger 1365, distributed ledger 1415, etc.), information about the smart contract related to token 1360 (e.g., a third-party security audit of the contract, when token 1360 was minted, when the smart contract came into effect, when the smart contract expires). This may include information about whether it has been updated or when the conditions of the smart contract have been met, when token 1360 was created and / or minted, token identifier 610, token unit amount 615 (for example, how many instances of token 1360 exist and which instance is this particular token 1360), token ownership 620, any on-chain immutable metadata 625, on-chain mutable metadata 630, off-chain media 635, on-chain media, off-chain metadata 640, token smart contract 645, any other parameters of token 1360, or any combination thereof.In some examples, information 1355 may include interface elements (e.g., buttons, links, URLs, pointers) to a transfer platform that can enable the transfer of token 1360 (e.g., being purchased, sold, leased, licensed, or any combination thereof). If user 1305 is the current owner of token 1360, the interface elements 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 elements may instruct media device 1310 to buy token 1360 using the transfer platform.

[0152] The media device 1310 may also communicate with the data store 1370 to retrieve information about the token 1360, the digital asset 1340, and / or any modifications, customizations, and / or personalizations. The data store 1370 may be an example of the data store 298 and / or the data structure 650. In some examples, some of the information 1355 may be retrieved by the media device 1310 from the data store 1370. In some examples, the data store 1370 may store modifications, customizations, and / or personalizations to the digital asset 1340 (e.g., virtual object 1345). For example, in Figure 13, one such customization 1357 stored in the data store 1370 is shown as a hat (e.g., a party hat) for the virtual object 1345 (e.g., a virtual dog). In some examples, modifications, customizations, and / or personalizations to the digital asset 1340 may be added by the owner of the token 1360. In some examples, modifications, customizations, and / or personalizations to digital asset 1340 may be added by the previous owner of token 1360. In some examples, modifications, customizations, and / or personalizations to digital asset 1340 may be added by viewers of digital asset 1340 corresponding to token 1360. Different users and / or owners of token 1360 may set different settings that specify who can and cannot add modifications, customizations, and / or personalizations to digital asset 1340.

[0153] In some cases, any modification, customization, and / or personalization of the digital asset 1340 may be automatically applied to the digital asset 1340 to help user 1305 learn some information about the digital asset 1340 and / or associated token 1360. For example, if user 1305 owns token 1360, a first effect (e.g., one or more modifications, customizations, and / or personalizations) may be applied to the digital asset 1340 so that it is displayed by the media device 1310. If someone known to user 1305 (e.g., a friend, family member, colleague, acquaintance, or acquaintance of another relationship) owns token 1360, a second effect (e.g., one or more modifications, customizations, and / or personalizations) may be applied to the digital asset 1340 so that it is displayed by the media device 1310. If a well-known person (e.g., a celebrity) owns token 1360, a third effect (e.g., one or more modifications, customizations, and / or personalizations) may be applied to the digital asset 1340 so as to be displayed by the media device 1310. In some examples, different relationships (e.g., friends vs. family vs. colleagues) may be associated with different effects (e.g., one or more modifications, customizations, and / or personalizations). In some examples, different types of well-known people (e.g., politicians, star athletes, musicians, movie stars, TV stars, renowned scientists, etc.) may be associated with different effects (e.g., one or more modifications, customizations, and / or personalizations).

[0154] While media device 1310 is shown as the first to display a depiction of anchor element 1350, it should be understood that it is intended to show that media device 1310's image sensor 1315 has captured an image of anchor element 1350. In some examples, the anchor element 1350 itself is displayed by media device 1310, for example, in an image preview window corresponding to image sensor 1315. In some examples, the anchor element 1350 itself is never displayed by media device 1310; instead, media device 1310 displays a virtual object 1345 (for example, with information 1355 and / or customization 1357).

[0155] In some examples, the anchor element 1350 may be an anchor element of a different type than an optical glyph. For example, in some examples, the anchor element 1350 may be an object, and a reference image of the object is stored in the data store 1370 and / or in the distributed ledger 1365 (for example, using an on-chain pointer to an off-chain reference image). The media device 1310 may detect and recognize an object in an image captured using the image sensor 1315 by comparing the image captured using the image sensor 1315 with a reference image of the object. The data store 1370 may also identify a token 1360 along with the reference image of the object, allowing the media device 1310 to determine the token 1360 once the object is detected and / or recognized, and then the media device 1310 proceeds as described above and outputs the digital asset 1340 (for example, with information 1355 and / or customization 1357).

[0156] In some examples, the anchor element 1350 may include a designated area identified in the data store 1370 and / or distributed ledger 1365, such as the one associated with the token 1360. Detection by the media device 1310 of its location in the designated area using the positioning sensor 1320 and / or image sensor 1315 (for example, by recognizing an image of the environment in the designated area) can cause the media device 1310 to output the digital asset 1340 corresponding to the token 1360 corresponding to the anchor element 1350 (for example, along with information 1355 and / or customization 1357). In some examples, the anchor element 1350 may include a designated location identified in the data store 1370 and / or distributed ledger 1365, such as the one associated with the token 1360. Detection by the media device 1310 using the positioning sensor 1320 and / or image sensor 1315 (for example, by recognizing an image of the environment in a specified area) that the media device 1310 is located within a threshold range from a specified position can cause the media device 1310 to output a digital asset 1340 corresponding to a token 1360 corresponding to an anchor element 1350 (for example, along with information 1355 and / or customization 1357).

[0157] Figure 14 is a conceptual diagram showing a token device 1405 associated with token 1420 in a distributed ledger 1415, and the transfer of token device 1405 from a first user 1410 to a 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, which may be associated with digital asset 1425. Digital asset 1425 is shown in Figure 14 as containing images of a dog and a tree. Token device 1405 may include output devices such as a display and / or speaker. The token device 1405 may output the digital asset 1425 associated with the token 1420, for example, by displaying the visual content (e.g., images, videos) of the digital asset 1425 using the token device's display and / or by playing the audio content (e.g., sounds, music) of the digital asset 1425 using the token device's speaker. In Figure 14, the token device 1405 is shown as including a display that shows images of a dog and a tree, which are part of the digital asset 1425. In some examples, the digital asset 1425 may include videos or animated images, and the token device 1405 may display the videos or animated images, for example, in a loop. In some examples, the token device 1405 may be a physical representation of the token 1420 to which the token device 1405 is associated.

[0158] As shown in scenario 1400A at the top of Figure 14, the distributed ledger 1415 associated with token 1420 (e.g., blockchain ledger 500 and / or DAG ledger 700) indicates that token 1420 is owned by a first user 1410. In the intermediate scenario 1400B and the lower scenario 1400C of Figure 14, the first user 1410 is shown as transferring token device 1405 to a second user 1430. In intermediate scenario 1400B, the distributed ledger 1415 is not updated, leading to a split ownership scenario where the first user 1410 still owns token 1420 according to the distributed ledger 1415, but the second user 1430 owns token device 1405. This scenario can be confusing because token device 1405 may be considered a physical representation of token 1420. For example, the first user 1410 could offer to sell token 1420 to the second user 1430, but instead might only sell token device 1405 to the second user 1430. If the second user 1430 is unaware of token 1420 and token device 1405, this could lead to a negative outcome where the second user 1430 believes they have purchased both token 1420 and token device 1405, when in reality they have only purchased token device 1405 without token 1420.

[0159] In scenario 1400C below, 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 moved (e.g., from another area associated with first user 1410) to an area associated with second user 1430. The transfer system may detect that token device 1405 is in an area associated with second user 1430 based on the fact that token device 1405 has come within range of communication with one or more devices associated with second user 1430, such as local device 1435, wireless local area network (WLAN), other token devices owned by second user 1430 and associated with tokens owned by 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 positioning sensor of the token device 1405 indicating that the token device 1405 is in a geographic area previously designated as associated with the second user 1430 (for example, in the distributed ledger 1415 and / or data store 298). The transfer system may also detect that the token device 1405 is in an area associated with the second user 1430 based on the positioning sensor of the token device 1405 indicating that the token device 1405 is within a threshold range from the location of the second user 1430 (for example, the location of the second user 1430's media device 205).

[0160] In some examples, the distributed ledger 1415 may store a smart contract associated with the token 1420. The smart contract may have been previously agreed upon by the first user 1410. The smart contract may indicate that if the token device 1405 moves to an area associated with another user (e.g., the second user 1430), it should be transferred to the other user (e.g., the second user 1430). In some examples, when the transfer system detects that the token device 1405 has moved to an area associated with the second user 1430, it may query the media device 205 associated with the first user 1410 to agree to transfer the token 1420 to the second user 1430, and upon receiving confirmation of agreement from the media device 205 associated with the first user 1410, it may proceed to initiate the transfer of the token 1420 from the first user 1410 to the second user 1430 (for example, by generating and / or adding a new block with a payload that records the transfer, by ensuring that the transfer of the token 1420 from the first user 1410 to the second user 1430 is recorded in the distributed ledger 1415). In some examples, when the transfer system detects that the token device 1405 has moved to an area associated with the second user 1430, it may query the media device 205 associated with the second user 1430 to agree to transfer the token 1420 to the second user 1430, and upon receiving confirmation of agreement from the media device 205 associated with the second user 1430, it may proceed to initiate the transfer of the token 1420 from the first user 1410 to the second user 1430 (for example, by generating and / or adding a new block with a payload that records the transfer, by ensuring that the transfer of the token 1420 from the first user 1410 to the second user 1430 is recorded in the distributed ledger 1415).

[0161] Figure 15A is a conceptual diagram 1500 illustrating the generation of a smart contract and its input into a distributed ledger according to an aspect of the present disclosure. The distributed computing architecture comprises multiple computing systems (referred to here as computers), which may include a computing system 1900 that stores and modifies the distributed ledger. The first computer issues a request 1505 requesting the input of a smart contract into the distributed ledger according to specific rules. The second computer issues a response 1510 indicating that the second computer has generated a new block for inputting the requested smart contract into the distributed ledger. The third, fourth, and fifth computers submit Verifications 1520A–1520C indicating that they have verified that the block correctly implements the smart contract, that the smart contract code is executable (e.g., free from syntax errors or other errors), that all parties involved in the smart contract have submitted agreement to the smart contract's clauses, that the on-chain pointer correctly points to valid off-chain smart contract code, and / or that sufficient funds are allocated to pay the execution fees for the intended payload elements. The second computer submits an input confirmation indicating that the input of the new block to the distributed ledger for the requested smart contract will be successful, in response to verification by the minimum number of devices.

[0162] A process similar to that shown in Figure 15A may be used to input tokens, and the corresponding verifications 1520A-1520C verify, for example, that the tokens refer 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 are allocated to pay the execution fee for the intended payload elements. A process similar to that shown in Figure 15A may be used to input transactions, and the corresponding verifications 1520A-1520C verify, for example, that the transferor has a sufficient amount of assets for the transaction to occur (e.g., that the transferor owns the tokens to be transferred), and / or that sufficient funds are allocated to pay the execution fee for the intended payload elements.

[0163] Figure 15B is a conceptual diagram 1550 illustrating the execution of a smart contract according to one aspect of the present disclosure. The first computer submits an identification 1555 indicating that the first computer has executed the smart contract code, identified that the conditions in the smart contract have been met, and identified the actions to be taken. The second, third, and fourth computers submit verifications 1510A to 1510C indicating that the second, third, and fourth computers have executed the smart contract code, verified that the conditions in the smart contract have been met, and verified the actions to be taken. The fifth computer shows an error 1515 in the case of no verification. The third computer shows an action 1520 indicating that the third computer has executed the smart contract code and performed the action in response to verification by a minimum number of devices (e.g., verifications 1510A to 1510C).

[0164] Figure 16A is a flowchart illustrating an example of process 1600 for context-dependent token generation, using several 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 in Figure 2, or a portion thereof. In some examples, the imaging system may include, for example, an image acquisition and processing system 100, an image acquisition device 105A, an image processing device 105B, an image processor 150, an ISP 154, a host processor 152, a digital asset tracking system 200, a media device 205, a network device 280, a local device 270, an additional device 297, a data store 298, an anchor element 299, an HMD 310, a mobile handset 410, a media device 810, a local device 830, a media device 910, a local device 930, a media device 1010, a local device 103 0, 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 computing systems of Figure 15A, one or more computing systems of Figure 15B, a digital asset tracking system running process 1650, a digital asset management system running process 1700, a digital asset management system running process 1800, computing system 1900, processor 1910, or a combination thereof.

[0165] In operation 1605, the digital asset management system is configured to receive and be able to receive media content based on sensor data captured by at least one sensor of a media device. Examples of media devices may include the image acquisition and processing system 100, the image acquisition device 105A, the image processing device 105B, the media device 205, the HMD 310, the mobile handset 410, the media device 810, the media device 910, the media device 1010, the media device 1110, the ownership device 1210, the media device 1310, the distributed ledger 1365, the data store 1370, the token device 1405, the computing system shown in Figures 15A-15B, the computing system 1900, or a combination thereof. Examples of at least one sensor include an image sensor 130, one or more sensors 210, one or more attitude sensors 215, one or more media sensors 220, a first camera 330A, a second camera 330B, a first camera 430A, a second camera 430B, a third camera 430C, a fourth camera 430D, an image sensor 815, an image sensor 915, an image sensor 1015, an image sensor 1315, a positioning sensor 820, a positioning sensor 920, a positioning sensor 1020, a positioning sensor 1120, a positioning sensor 1120, a positioning sensor 1220, a positioning sensor 1320, or a combination thereof. Examples of sensor data may include sensor data 230, attitude 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 in block 278, or these communications.Examples of media data may include media data 250, sensor data 230, attitude 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 in block 278, digital assets 605, digital assets 840, digital assets 940, digital assets 1040, digital assets 1140, digital assets 1240, digital assets 1340, virtual objects 1345, digital assets 1425, or combinations thereof.

[0166] In some examples, a digital asset tracking system includes one or more sensor connectors coupled to one or more sensors. Media data may be received using one or more sensor connectors. Sensor data captured by one or more sensors may be received using one or more sensor connectors. One or more sensor connectors may include ports, jacks, wires, input / output (IO) pins, conductive paths on a printed circuit board (PCB), any other type of connector discussed herein, or any combination thereof. In some examples, a digital asset tracking system includes one or more sensors.

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

[0168] In some examples, media content includes an altered or modified portion of sensor data. Altering sensor data may include processing the sensor data, for example, as discussed with respect to the image processing device 105B and / or media processor 235. In some embodiments, the media device generates media data by altering the sensor data to add virtual content to it. The virtual content may be generated by a virtual content generator 240. The virtual content may be added to the sensor data (e.g., integrated with the sensor data) using an image synthesizer 245. Examples of virtual content include a virtual object 1045 (a virtual dog) that appears in the digital asset 1040 (an example of media data) but does not appear in the sensor data captured by the image sensor 1015, a virtual object 1345 (a virtual dog) that appears in the digital asset 1340 (an example of media data) but does not appear in the sensor data captured by the image sensor 1315, or a combination thereof. The digital asset 1140 may also be an example of media content that includes an altered variation of at least a portion of sensor data, and the map of the digital asset 1140 is processed and / or modified in the form of location data (for example, collected using the positioning sensor 1120 and / or based on communication between the media device 1110 and the local device 1130).

[0169] In operation 1610, the digital asset management system is configured to determine and can determine the location of a media device. In some examples, the digital asset management system can determine the location of a media device based on sensor data. Examples of media device locations include: attitude data 225, sensor data 230, positioning information determined based on one or more communications 272 (e.g., by media device 205 and / or local device 270 and / or digital asset tracking system), stored communications in block 277, stored communications in block 278, positioning information determined using image sensor 815 and / or positioning sensor 820, positioning information determined based on one or more communications 835 (e.g., by media device 810 and / or local device 830 and / or digital asset tracking system), positioning information determined using image sensor 915 and / or positioning sensor 920, positioning information determined based on one or more communications 935 (e.g., by media device 910 and / or local device 930 and / or digital asset tracking system), image sensor 101 This includes positioning information determined using positioning sensor 1020 and / or positioning sensor 1020, positioning information determined based on one or more communications 1035 (for example, by media device 1010 and / or local device 1030 and / or digital asset tracking system), positioning information determined using positioning sensor 1120, positioning information determined based on one or more communications 1135 (for example, by media device 1110 and / or local device 1130 and / or digital asset tracking system), positioning information determined using positioning sensor 1220, positioning information determined based on one or more communications 1235 (for example, by ownership device 1210 and / or local device 1230 and / or digital asset tracking system), positioning information determined using image sensor 1315 and / or positioning sensor 1320, location of token device 1405, or a combination thereof.

[0170] In some examples, sensor data includes positioning data based on the reception 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, at least one wireless signal includes a GNSS signal (e.g., a GPS signal) from a Global Navigation Satellite System (GNSS) satellite (e.g., a GPS satellite) which is received, for example, using a positioning receiver. In some examples, at least one wireless signal includes a short-range wireless signal (e.g., Bluetooth®, Wi-Fi, cellular, WLAN) from a local device which is at least within the transmission range of the media device during the reception of at least one wireless signal by at least one sensor. Examples of local devices may include the image acquisition and processing system 100, the image acquisition device 105A, the 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 shown in Figures 15A to 15B, the computing system 1900, or a combination thereof. Examples of positioning receivers may include one or more short-range wireless transceivers 275, positioning sensors 820, 920, 1020, 1120, 1220, 1320, or a combination thereof. Examples of 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.

[0171] In operation 1615, the digital asset management system is configured and can determine whether the location of a media device is within a geographic area. In some examples, the digital asset management system can determine whether the location of a media device is within a geographic area based on sensor data. Examples of geographic areas include museums (e.g., as shown in Figures 8A-8B and 12A-12B), offices (e.g., as shown in Figures 9A-9B), parks (e.g., as shown in Figures 10A-10B and 13), paths (e.g., as shown in Figures 11A-11B), areas associated with a first user 1410, areas associated with a second user 1430, indoor areas, outdoor areas, stadiums, concert venues, cinemas, shopping malls, the transmission range of one or more short-range wireless transceivers 275 of one or more local devices 270, the 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. An example of determining that the location of a media device is within a geographical area is block 290 of the digital asset tracking system 200 in Figure 2, which may be performed by a network device 280, a media device 205, a local device 270, or a combination thereof.

[0172] In some examples, sensor data includes at least one image captured by at least one image sensor of at least one sensor of a media device. 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, image sensor of first camera 330A, image sensor of second camera 330B, image sensor of first camera 430A, image sensor of second camera 430B, image sensor of third camera 430C, image sensor of fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, or combinations thereof. Examples of media data that are, include, or are 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 combinations thereof.

[0173] In some examples, determining the location of a media device involves detecting at least a portion of an environment in at least one image and determining the location of the media device based at least in part on the detection of at least that portion of the environment in at least one image. In some examples, determining that the location of a media device is within a geographical area involves detecting at least a portion of an environment in at least one image and determining that at least that portion of the environment is located within a geographical area. For example, in the context of Figure 8A, the digital asset tracking system can verify that digital asset 840 depicts an object (Mona Lisa) located within a geographical area (Louvre Museum), and therefore can verify that media device 810 is within a geographical area (Louvre Museum). In the context of Figure 9A, the digital asset tracking system can verify that digital asset 940 depicts an object (Bob 945) located within a geographical area (park), and therefore can verify that media device 910 is within a geographical area (park). In the context of Figure 10A, the digital asset tracking system can verify that digital asset 1040 depicts objects (virtual object 1045 and real object 1047) located within a geographical area (park), and therefore can verify that media device 1010 is located within a geographical area (park). In the context of Figure 11A, the digital asset tracking system can verify that digital asset 1140 depicts objects (hiking trails) located within a geographical area (Yosemite), and therefore can verify that media device 1110 is located within a geographical area (Yosemite). In the context of Figure 13, the digital asset tracking system can verify that digital asset 1340 depicts objects (virtual object 1345 and real object 1347) located within a geographical area (park), and therefore can verify that media device 1310 is located within a geographical area (park).

[0174] In some embodiments, a digital asset management system may be configured to detect at least a portion of an individual in at least one image, determine the individual's identity, and set token parameters (e.g., token ownership 620, token smart contract 645) to indicate that the token is associated with that identity. In the context of Figure 9A, the digital asset tracking system may identify that an image captured by the image sensor 915 (and corresponding to the digital asset 940) contains a depiction of an individual (Bob 945) with a recognized identity. In some embodiments, the digital asset tracking system may be configured to set ownership of a token in an account associated with an individual with a recognized identity. In the context of Figures 9A-9B, the digital asset tracking system may set ownership of token 960 in Bob 945.

[0175] In some examples, media content includes maps of geographical areas, such as the map in digital asset 1140.

[0176] In some examples, determining that the location of a media device is within a geographical area is based on at least one communication between the media device and a local device associated with the geographical area (e.g., communication 272, communication 835, communication 935, communication 1035, communication 1135, communication 1235, etc.). Examples of local devices may include the image acquisition and processing system 100, the image acquisition device 105A, the 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 shown in Figures 15A-15B, the computing system 1900, or a combination thereof.

[0177] In operation 1620, in response to the determination in operation 1615 that the location of the media device is within a geographical area, the digital asset management system is configured and can generate tokens corresponding to the media content. The payload of at least one block of the distributed ledger identifies the tokens. Examples of tokens may include token 600, token 860, token 960, token 1060, token 1160, token 1260, token 1360, token 1420, or combinations thereof. Examples of distributed ledgers may include distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledger 1365, distributed ledger 1415, the distributed ledgers corresponding to the smart contracts in Figures 15A-15B, or combinations thereof. Examples of blocks include Block A505, Block B535, Block C565, Block 710, Block 720, Block 730, Block 740, Block 750, Block 760, or combinations thereof. Examples of payloads include Block A payload 530, Block B payload 560, and Block C payload 590. Tokens may be non-fungible tokens (NFTs).

[0178] In some examples, a digital asset management system can be configured to generate at least one block in response to determining that the location of a media device is within a geographical area, and to add at least one block to a distributed ledger. In some examples, at least one block contains hashes of at least a portion of previous blocks in the distributed ledger (e.g., hashes 515 / 545 / 575, Merkle roots 520 / 550 / 580). In some examples, a digital asset management system can be configured to generate a distributed ledger in response to determining that the location of a media device is within a geographical area.

[0179] In some examples, a digital asset management system is configured to send a request to a computing device to generate at least one block in response to determining that the location of a media device is within a geographical area, receive at least one block, and add at least one block to a distributed ledger, and can do so.

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

[0181] In some examples, a digital asset management system can be configured and capable of determining that a geographical area contains at least a threshold number of people. Generating tokens corresponding to media content may be performed in response to the determination that a geographical area contains at least a threshold number of people.

[0182] In some examples, the digital asset management system running process 1600 may include media devices, local devices, or a combination of these. In some examples, the digital asset management system running process 1600 may be located within a geographical area.

[0183] In some examples, a digital asset management system performing process 1600 may include at least one of the following: a head-mounted display (HMD) (e.g., HMD310), a mobile handset (e.g., mobile handset410), a wireless communication device, or a combination thereof.

[0184] 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 the location of the media device, means for determining that the location of the media device is within a geographical area, and means for generating a token corresponding to the media content in response to the determination that the location of the media device is within a geographical area, wherein the payload of at least one block of the distributed ledger identifies the token.

[0185] In some examples, the means for receiving media content include an image acquisition and processing system 100, an image sensor 130, a digital asset tracking system 200, one or more sensors 210, one or more attitude sensors 215, one or more media sensors 220, a first camera 330A, a second camera 330B, a first camera 430A, a second camera 430B, a third camera 430C, a fourth camera 430D, an image sensor 815, an image sensor 915, an image sensor 1015, an image sensor 1315, a positioning sensor 820, a positioning sensor 920, a positioning sensor 1020, a positioning sensor 1120, a positioning sensor 1220, a positioning sensor 1320, a media device 205, a network device 280, and a local device. The system includes a chair 270, additional devices 297, a data store 298, an anchor element 299, an HMD 310, a mobile handset 410, a media device 810, a local device 830, a media device 910, a local device 930, a media device 1010, a local device 1030, a media device 1110, a local device 1130, an ownership device 1210, a local device 1230, a media device 1310, a distributed ledger 1365, a data store 1370, a token device 1405, one or more computing systems from Figure 15A, one or more computing systems from Figure 15B, a computing system 1900, an input device 1945, or a combination thereof.

[0186] In some examples, the means for determining the location of a media device and / or determining that the location of a media device is within a geographic area include: an image acquisition and processing system 100, an image sensor 130, a digital asset tracking system 200, one or more sensors 210, one or more attitude sensors 215, one or more media sensors 220, a first camera 330A, a second camera 330B, a first camera 430A, a second camera 430B, a third camera 430C, a fourth camera 430D, an image sensor 815, an image sensor 915, an image sensor 1015, an image sensor 1315, a positioning sensor 820, a positioning sensor 920, a positioning sensor 1020, a positioning sensor 1120, a positioning sensor 1220, a positioning sensor 1320, a media device 205, and a network data The system includes a vice 280, a local device 270, an additional device 297, a data store 298, an anchor element 299, an HMD 310, a mobile handset 410, a media device 810, a local device 830, a media device 910, a local device 930, a media device 1010, a local device 1030, a media device 1110, a local device 1130, an ownership device 1210, a local device 1230, a media device 1310, a distributed ledger 1365, a data store 1370, a token device 1405, one or more computing systems from Figure 15A, one or more computing systems from Figure 15B, a computing system 1900, a communication interface 1940, an input device 1945, or a combination thereof.

[0187] In some examples, the means for generating tokens include a digital asset tracking system 200, a media device 205, a network device 280, a local device 270, a distributed ledger 295, an additional device 297, a data store 298, an anchor element 299, an HMD 310, a mobile handset 410, a blockchain ledger 500, a token 600, a data structure 650, a DAG ledger 700, a media device 810, a local device 830, a media device 910, a local device 930, and a media device 1 The system includes 010, 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 computing systems of Figure 15A, one or more computing systems of Figure 15B, computing system 1900, output device 1935, communication interface 1940, or a combination thereof.

[0188] Figure 16B is a flowchart illustrating an example of a process 1650 for tracking location-related digital assets, using several 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 in Figure 2, or a portion thereof. In some examples, the imaging system may include, for example, an image acquisition and processing system 100, an image acquisition device 105A, an image processing device 105B, an image processor 150, an ISP 154, a host processor 152, a digital asset tracking system 200, a media device 205, a network device 280, a local device 270, an additional device 297, an HMD 310, a mobile handset 410, a media device 810, a local device 830, a media device 910, a local device 930, a media device 1010, a local device 1030, a media device 1110, a local device 1130, an ownership device 1210, a local device 1230, one or more computing systems in Figure 15A, one or more computing systems in Figure 15B, a computing system 1900, a processor 1910, or a combination thereof.

[0189] In operation 1655, the digital asset tracking system is configured to receive and can receive media data from the media device based on sensor data captured by one or more sensors of the media device. Examples of media devices may include the image acquisition and processing system 100, the image acquisition device 105A, the image processing device 105B, the media device 205, the HMD 310, the mobile handset 410, the media device 810, the media device 910, the media device 1010, the media device 1110, the ownership device 1210, the media device 1310, the distributed ledger 1365, the data store 1370, the token device 1405, the computing system shown in Figures 15A-15B, the computing system 1900, or a combination thereof. Examples of one or more sensors include an image sensor 130, one or more sensors 210, one or more attitude sensors 215, one or more media sensors 220, a first camera 330A, a second camera 330B, a first camera 430A, a second camera 430B, a third camera 430C, a fourth camera 430D, an image sensor 815, an image sensor 915, an image sensor 1015, an image sensor 1315, a positioning sensor 820, a positioning sensor 920, a positioning sensor 1020, a positioning sensor 1120, a positioning sensor 1120, a positioning sensor 1220, a positioning sensor 1320, or a combination thereof. Examples of sensor data may include sensor data 230, attitude 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 in block 278, or these communications.Examples of media data may include media data 250, sensor data 230, attitude 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 in block 278, digital assets 605, digital assets 840, digital assets 940, digital assets 1040, digital assets 1140, digital assets 1240, digital assets 1340, virtual objects 1345, digital assets 1425, or combinations thereof.

[0190] In some examples, a digital asset tracking system includes one or more sensor connectors coupled to one or more sensors. Media data may be received using one or more sensor connectors. Sensor data captured by one or more sensors may be received using one or more sensor connectors. One or more sensor connectors may include ports, jacks, wires, input / output (IO) pins, conductive paths on a printed circuit board (PCB), any other type of connector discussed herein, or any combination thereof. In some examples, a digital asset tracking system includes one or more sensors.

[0191] Media data may be sensor data. Media data may include sensor data. For example, media device 205 can acquire media data 250 by receiving sensor data 230 and / or attitude data 225. Digital asset 840 is an example of media data that may be sensor data captured by the image sensor 815 of media device 810. Digital asset 940 is an example of media data that may be sensor data captured by the image sensor 915 of media device 910.

[0192] A media device generates media data, at least partially, by modifying sensor data. Modifying sensor data may include processing the sensor data, for example, as discussed with respect to the image processing device 105B and / or media processor 235. In some embodiments, a media device generates media data, at least partially, by modifying sensor data to add virtual content to it. The virtual content may be generated by a virtual content generator 240. The virtual content may be added to the sensor data (for example, integrated with the sensor data) using an image synthesizer 245. An example of virtual content includes a virtual object 1045 (a virtual dog), which appears in the digital asset 1040 (an example of media data) even though it does not appear in the sensor data captured by the image sensor 1015.

[0193] Sensor data may include one or more images captured by one or more image sensors of one or more sensors of a media device. 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, the image sensor of the first camera 330A, the image sensor of the second camera 330B, the image sensor of the first camera 430A, the image sensor of the second camera 430B, the image sensor of the third camera 430C, the image sensor of the fourth camera 430D, image sensor 815, image sensor 915, image sensor 1015, or a combination thereof. Examples of media data that are, include, or are 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.

[0194] In operation 1660, the digital asset tracking system is configured to receive and can receive positioning data indicating the location of the media device at the same time as sensor data is acquired by one or more sensors of the media device. Examples of positioning data include: attitude data 225, sensor data 230, positioning information determined based on one or more communications 272 (e.g., by media device 205 and / or local device 270 and / or the digital asset tracking system), stored communications in block 277, stored communications in block 278, positioning information determined using image sensor 815 and / or positioning sensor 820, positioning information determined based on one or more communications 835 (e.g., by media device 810 and / or local device 830 and / or the digital asset tracking system), positioning information determined using image sensor 915 and / or positioning sensor 920, positioning information determined based on one or more communications 935 (e.g., by media device 910 and / or local device 930 and / or the digital asset tracking system), image sensor 1015 and This includes positioning information determined using positioning sensor 1020, positioning information determined based on one or more communications 1035 (for example, by media device 1010 and / or local device 1030 and / or digital asset tracking system), positioning information determined using positioning sensor 1120, positioning information determined based on one or more communications 1135 (for example, by media device 1110 and / or local device 1130 and / or digital asset tracking system), positioning information determined using positioning sensor 1220, positioning information determined based on one or more communications 1235 (for example, by ownership device 1210 and / or local device 1230 and / or digital asset tracking system), positioning information determined using image sensor 1315 and / or positioning sensor 1320, the location of token device 1405, or a combination thereof.

[0195] Sensor data may include positioning data, which is determined based on the reception of one or more positioning signals by a positioning receiver of one or more sensors of the media device. For example, at least a portion of the positioning data may include attitude data 225 from one or more attitude sensors 215 and / or positioning information determined by the media device 205 based on communication 272. Media data may include maps generated by the media device based on the positioning data. The media device can generate media data at least in part by generating maps based on positioning data and / or sensor data. An example of such a map includes a map in the digital asset 1140, where the media device 1110 generates the map based on positioning sensor data from positioning sensor 1120.

[0196] Sensor data may include secondary positioning data determined based on the reception of one or more positioning signals by a positioning receiver of one or more sensors of the media device. Examples of 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 one or more positioning signals may include signals carrying communication 272 between media device 205 and local device 270, signals carrying communication 835 between mobile device 810 and local device 830, signals carrying communication 935 between mobile device 910 and local device 930, signals carrying communication 1035 between mobile device 1010 and local device 1030, signals carrying communication 1135 between mobile device 1110 and local device 1130, signals carrying communication 1235 between mobile device 1210 and local device 1230, or combinations thereof. Media data may include maps generated by the media device based on the positioning data. A media device can generate media data, at least partially, by generating a map based on positioning data and / or sensor data. An example of such a map includes a map in the digital asset 1140, and the media device 1110 generates the map based on positioning sensor data from the positioning sensor 1120. An example of a positioning receiver may include a short-range wireless transceiver 260, a short-range wireless transceiver 275, or a combination thereof.

[0197] To receive positioning data, the digital asset tracking system can receive positioning data from a media device. The positioning data may be based on the reception of one or more positioning signals by a positioning receiver of one or more sensors of the media device. For example, at least a portion of the positioning data may include attitude data 225 from one or more attitude sensors 215 and / or positioning information determined by the media device 205 based on communication 272. An example of a positioning receiver may include a GNSS receiver such as a GPS receiver. An example of one or more positioning signals may include GNSS signals such as GPS signals. An example of a positioning receiver may include positioning sensor 820, positioning sensor 920, positioning sensor 1020, positioning sensor 1120, positioning sensor 1220, or a combination thereof. An example of a positioning receiver may include one or more short-range wireless transceivers 260, positioning sensors 820, 920, 1020, 1120, 1220, 1320, or a combination thereof. An example of 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.

[0198] To receive positioning data, the digital asset tracking system may receive positioning data from a local device separate from the media device. Positioning data may be obtained based on the reception of one or more positioning signals by the positioning receiver of the local device. Examples of local devices may include the image acquisition and processing system 100, the image acquisition device 105A, the 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 shown in Figures 15A-15B, the computing system 1900, or a combination thereof. Examples of positioning receivers may include one or more short-range wireless transceivers 275. Examples of one or more positioning signals may include a signal that carries communication 272 between media device 205 and local device 270, a signal that carries communication 835 between mobile device 810 and local device 830, a signal that carries communication 935 between mobile device 910 and local device 930, a signal that carries communication 1035 between mobile device 1010 and local device 1030, a signal that carries communication 1135 between mobile device 1110 and local device 1130, a signal that carries communication 1235 between mobile device 1210 and local device 1230, or a combination thereof.

[0199] The positioning receiver may be a short-range wireless communication receiver configured to receive one or more short-range wireless communication signals. An example of a short-range wireless communication receiver includes one or more short-range wireless transceivers 260. One or more short-range wireless communication signals may be transmitted by local devices within a geographical area. Examples of local devices may include an image acquisition and processing system 100, an image acquisition device 105A, an image processing device 105B, a local device 270, a local device 830, a local device 930, a local device 1030, a local device 1130, a local device 1230, the computing system shown in Figures 15A-15B, a computing system 1900, or a combination thereof. Examples of 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 geographical area may correspond to the transmission range of one or more short-range wireless communication signals by the local device. In some examples, the positioning receiver may be a GNSS receiver configured to receive one or more Global Navigation Satellite System (GNSS) signals from one or more satellites.

[0200] In some embodiments, the digital asset tracking system includes a local device. In some embodiments, the digital asset tracking system includes a media device.

[0201] In operation 1665, the digital asset tracking system is configured and can verify, based on positioning data, that the location of a media device at the time of sensor data acquisition is within a geographic area. An example of verifying that the location of a media device at the time of sensor data acquisition is within a geographic area includes block 290 of the digital asset tracking system 200 in Figure 2, which may be performed by a network device 280, a media device 205, a local device 270, or a combination thereof. Examples of geographic areas include museums, stadiums, concert halls, cinemas, shopping malls, the transmission range of one or more short-range wireless transceivers 275 of one or more local devices 270, the 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.

[0202] To verify that the location of a media device is within a geographical area at the time of sensor data acquisition, the digital asset tracking system can verify the content of one or more communications between the media device and local devices associated with the geographical area. To verify that the location of a media device is within a geographical area at the time of sensor data acquisition, the digital asset tracking system can verify the transmission and / or reception timing of one or more communications between the media device and local devices associated with the geographical area. To verify that the location of a media device is within a geographical area at the time of sensor data acquisition, the digital asset tracking system can verify the transmission and / or reception frequencies of one or more communications between the media device and local devices associated with the geographical area. Examples of local devices may include the image acquisition and processing system 100, the image acquisition device 105A, the 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 shown in Figures 15A-15B, the computing system 1900, or a combination thereof. One or more characteristics of a communication, such as its content, transmission timing, reception timing, transmission frequency, and / or reception frequency, may be stored in the local device for the communication stored in block 277, and / or in the media device 205 for the communication stored in block 278.Examples of 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.

[0203] To verify that the location of a media device is within a geographical area at the same time as sensor data acquisition, the digital asset tracking system can verify that the sensor data (and / or media data) describes an object visible within the geographical area. For example, in the context of Figure 8A, the digital asset tracking system can verify that digital asset 840 describes an object (Mona Lisa) located within the geographical area (Louvre Museum), and therefore can verify that media device 810 is located within the geographical area (Louvre Museum). In the context of Figure 9A, the digital asset tracking system can verify that digital asset 940 describes an object (Bob 945) located within the geographical area (park), and therefore can verify that media device 910 is located within the geographical area (park). In the context of Figure 10A, the digital asset tracking system can verify that digital asset 1040 describes objects (virtual object 1045 and real object 1047) located within the geographical area (park), and therefore can verify that media device 1010 is located within the geographical area (park). In the context of Figure 11A, the digital asset tracking system can verify that digital asset 1140 depicts an object (hiking trail) located within a geographical area (Yosemite), and therefore can verify that media device 1110 is located within a geographical area (Yosemite). In the context of Figure 13, the digital asset tracking system can verify that digital asset 1340 depicts objects (virtual object 1345 and real object 1347) located within a geographical area (park), and therefore can verify that media device 1310 is located within a geographical area (park).

[0204] In operation 1670, the digital asset tracking system is configured and can automatically generate tokens corresponding to media data in response to verifying that the location of a media device is within a geographical area, and the tokens are identified in the payload of a distributed ledger block. Examples of tokens may include token 600, token 860, token 960, token 1060, token 1160, token 1260, token 1360, token 1420, or combinations thereof. Examples of distributed ledgers include distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledger 1365, distributed ledger 1415, the distributed ledgers corresponding to the smart contracts in Figures 15A-15B, or combinations thereof. Examples of blocks include block A505, block B535, block C565, block 710, block 720, block 730, block 740, block 750, block 760, or combinations thereof. Examples of payloads include block A payload 530, block B payload 560, and block C payload 590. Tokens may be non-fungible tokens (NFTs).

[0205] In some embodiments, the digital asset tracking system is configured and can automatically generate a block for a distributed ledger in response to verifying that the location of a media device is within a geographical area. In some embodiments, the digital asset tracking system is configured and can add a block to multiple blocks of a distributed ledger. In some embodiments, the digital asset tracking system is configured and can send a block to multiple computing devices so that multiple computing devices can add a block to each copy of the distributed ledger. Examples of multiple computing devices may include additional device 297, the computing systems of Figures 15A-15B, computing system 1900, or a combination thereof.

[0206] In some embodiments, the digital asset tracking system is configured and can automatically send a request to a block-generating computing device to generate a block for a distributed ledger in response to verifying that the location of a media device is within a geographical area. In some embodiments, the digital asset tracking system is configured and can receive a block from a block-generating computing device. In some embodiments, the digital asset tracking system is configured and can add a block to multiple blocks of a distributed ledger. Examples of block-generating computing devices may include one of the additional devices 297, one of the computing systems in Figures 15A-15B, computing system 1900, or a combination thereof.

[0207] A block may contain hashes of at least a portion of previous blocks in the distributed ledger. Examples of hashes include hashes 515, 545, and 575. A block may contain Merkle roots of multiple elements of the block's payload. Examples of Merkle roots include Merkle roots 520, 550, and 580. A token may correspond to at least one of multiple elements of the block's payload. In some embodiments, a digital asset tracking system may be configured and capable of automatically generating a distributed ledger in response to verifying that the location of a media device is within a geographical area.

[0208] In some embodiments, the digital asset tracking system can be configured to set ownership of tokens to accounts associated with users associated with media devices. For example, in the context of Figures 8A-8B, the digital asset tracking system can set ownership of token 860 to user 805. In the context of Figures 9A-9B, the digital asset tracking system can set ownership of token 960 to user 905. In the context of Figures 10A-10B, the digital asset tracking system can set ownership of token 1060 to user 1005. In the context of Figures 11A-11B, the digital asset tracking system can set ownership of token 1160 to user 1105. In the context of Figures 12A-12B, the digital asset tracking system can set ownership of token 1260 to user 1205. In the context of Figure 13, the digital asset tracking system can set ownership of token 1360 to user 1305. In the context of Figure 13, the digital asset tracking system can set ownership of token 1420 to a first user 1410 and / or a second user 1430. In some examples, token ownership may be stored on-chain, for example, in token ownership 620, on-chain immutable metadata 625, and / or on-chain mutable metadata 630. In some examples, token ownership may be stored off-chain, for example, in off-chain metadata 640.

[0209] In some embodiments, a digital asset tracking system can be configured to identify that sensor data contains a representation of an individual with a recognized identity. In the context of Figure 9A, the digital asset tracking system can identify that an image captured by the image sensor 915 (and corresponding to the digital asset 940) contains a depiction of an individual with a recognized identity (Bob 945). In some embodiments, the digital asset tracking system can be configured to set ownership of a token to an account associated with an individual with a recognized identity. In the context of Figures 9A-9B, the digital asset tracking system can set ownership of token 960 to Bob 945.

[0210] In some embodiments, the media device includes a head-mounted display such as HMD310. In some embodiments, the media device includes 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 embodiments, the media device includes a wearable device. In some embodiments, the media device is located within a geographical area.

[0211] In some embodiments, the digital asset tracking system includes a head-mounted display such as an HMD310. In some embodiments, the digital asset tracking system includes a mobile handset such as a mobile handset 410, a media device 810, a media device 910, a media device 1010, a media device 1110, an ownership device 1210, or a combination thereof. In some embodiments, the digital asset tracking system includes a wearable device. In some embodiments, the digital asset tracking system includes a server. In some embodiments, the digital asset tracking system is located within a geographical area.

[0212] In some embodiments, the digital asset tracking system may include means for receiving media data based on sensor data captured by one or more sensors of a media device. In some embodiments, the digital asset tracking system may include means for receiving positioning data indicating the location of the media device at the same time as the sensor data is captured by one or more sensors of the media device. In some embodiments, the digital asset tracking system may include means for verifying, based on the positioning data, that the location of the media device at the same time as the sensor data is captured is within a geographical area. In some embodiments, the digital asset tracking system may include means for automatically generating a token corresponding to the media data in response to the verification that the location of the media device is within a geographical area, the token being identified in the payload of a distributed ledger block.

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

[0214] In some examples, the means for receiving positioning data includes a network device 280. In some examples, the means for receiving positioning data includes a media device 205, a media device 810, a media device 910, a media device 1010, a media device 1110, an ownership device 1210, or a combination thereof. In some examples, the means for receiving positioning data includes a local device 270, a local device 830, a local device 930, a local device 1030, a local device 1130, a local device 1230, or a combination thereof. In some examples, the means for receiving positioning data includes an HMD 310. In some examples, the means for receiving positioning data includes a mobile handset 410. In some examples, means for receiving positioning data include receiving attitude data in a network transceiver (such as network transceiver 285) from a network transceiver (such as network transceiver 265) of the media device 205 via communication 282 (e.g., as attitude data 225, and / or as part of media data 250, and / or as part of information about communication 272). In some examples, means for receiving positioning data include capturing attitude data 225 and / or sensor data 230 by one or more sensors 210 of the media device 205. In some examples, means for receiving positioning data include receiving a stored copy of communication 272 (e.g., stored communication block 277 and / or stored communication block 278). In some examples, means for receiving positioning data include generating and / or acquiring media data 250 in the media device 205 (e.g., media data based at least in part on and / or including attitude data 225). In some examples, means for receiving media data include receiving media data from a network transceiver (such as network transceiver 265) of a media device 205 via communication 282 to a network transceiver (such as network transceiver 285).In some examples, means for receiving positioning data include positioning sensor 820, positioning sensor 920, positioning sensor 1020, positioning sensor 1120, positioning sensor 1220, or a combination thereof. In some examples, means for receiving positioning data include a digital asset tracking system performing process 1650. In some examples, means for receiving positioning data include receiving data from media device 205 and / or local device 270 for communication 272, receiving data from media device 810 and / or local device 830 for communication 835, receiving data from media device 910 and / or local device 930 for communication 935, receiving data from media device 1010 and / or local device 1030 for communication 1035, receiving data from media device 1110 and / or local device 1130 for communication 1135, receiving data from ownership device 1210 and / or local device 1230 for communication 1235, or a combination thereof. In some examples, the means for receiving positioning data includes a first camera 330A and / or a 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.

[0215] In some examples, means for verifying the location of a media device include a network device 280. In some examples, means for verifying the location of a media device include a media device 205, a media device 810, a media device 910, a media device 1010, a media device 1110, an ownership device 1210, or a combination thereof. In some examples, means for verifying the location of a media device include a local device 270, a local device 830, a local device 930, a local device 1030, a local device 1130, a local device 1230, or a combination thereof. In some examples, means for verifying the location of a media device include an HMD 310. In some examples, means for verifying the location of a media device include a mobile handset 410. In some examples, means for verifying the location of a media device include a media device 205. In some examples, means for verifying the location of a media device include a local device 270. In some examples, means for verifying the location of a media device include verification that the orientation of media device 205 is within a geographic area associated with local device 270 (block 290). In some examples, means for verifying the location of a media device include receiving positioning data from a network transceiver (such as network transceiver 265) of a media device 205 to a network transceiver (such as network transceiver 285) via communication 282 and comparison of positioning data to a geographic area. In some examples, means for verifying the location of a media device include a token smart contract 645. In some examples, means for verifying the location of a media device include the smart contracts shown in Figures 15A and 15B. In some examples, means for verifying the location of a media device include a digital asset tracking system that performs process 1650.

[0216] In some examples, the means for generating tokens corresponding to media data includes a network device 280. In some examples, the means for generating tokens corresponding to media data includes media devices 205, 810, 910, 1010, 1110, ownership device 1210, or a combination thereof. In some examples, the means for generating tokens corresponding to media data includes local devices 270, 830, 930, 1030, 1130, 1230, or a combination thereof. In some examples, the means for generating tokens corresponding to media data includes an HMD 310. In some examples, the means for generating tokens corresponding to media data includes a mobile handset 410. In some examples, the means for generating tokens corresponding to media data includes a distributed ledger 295, a blockchain ledger 500, a DAG ledger 700, a distributed ledger corresponding to the smart contracts in Figures 15A-15B, or a combination thereof. In some examples, the means for generating tokens corresponding to 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 tokens corresponding to media data includes token smart contract 645. In some examples, the means for generating tokens corresponding to media data includes the smart contract shown in Figures 15A to 15B. In some examples, the means for generating tokens corresponding to media data includes the computing system shown in Figures 15A to 15B. In some examples, the means for generating tokens corresponding to media data includes computing system 1900. In some examples, the means for generating tokens corresponding to media data includes a digital asset tracking system that performs process 1650.

[0217] Figure 17 is a flowchart showing process 1700 for context-dependent token-related 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 in Figure 2, or a portion thereof. In some examples, the imaging system may include, for example, an image acquisition and processing system 100, an image acquisition device 105A, an image processing device 105B, an image processor 150, an ISP 154, a host processor 152, a digital asset tracking system 200, a media device 205, a network device 280, a local device 270, an additional device 297, a data store 298, an anchor element 299, an HMD 310, a mobile handset 410, a media device 810, a local device 830, a media device 910, a local device 930, a media device 1010, a local device 103 This may include 0, 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 computing systems of Figure 15A, one or more computing systems of Figure 15B, a digital asset management system running process 1600, a digital asset tracking system running process 1650, a digital asset management system running process 1800, computing system 1900, processor 1910, or a combination thereof.

[0218] In operation 1705, the digital asset management system is configured to receive and be able to receive sensor data captured by at least one sensor of a media device. Examples of media devices may include the image acquisition and processing system 100, the image acquisition device 105A, the image processing device 105B, the media device 205, the HMD 310, the mobile handset 410, the media device 810, the media device 910, the media device 1010, the media device 1110, the ownership device 1210, the media device 1310, the distributed ledger 1365, the data store 1370, the token device 1405, the computing system shown in Figures 15A-15B, the computing system 1900, or a combination thereof. Examples of at least one sensor include an image sensor 130, one or more sensors 210, one or more attitude sensors 215, one or more media sensors 220, a first camera 330A, a second camera 330B, a first camera 430A, a second camera 430B, a third camera 430C, a fourth camera 430D, an image sensor 815, an image sensor 915, an image sensor 1015, an image sensor 1315, a positioning sensor 820, a positioning sensor 920, a positioning sensor 1020, a positioning sensor 1120, a positioning sensor 1120, a positioning sensor 1220, a positioning sensor 1320, or a combination thereof. Examples of sensor data may include sensor data 230, attitude 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 in block 278, or these communications.

[0219] In some examples, a digital asset tracking system includes one or more sensor connectors coupled to one or more sensors. Media data may be received using one or more sensor connectors. Sensor data captured by one or more sensors may be received using one or more sensor connectors. One or more sensor connectors may include ports, jacks, wires, input / output (IO) pins, conductive paths on a printed circuit board (PCB), any other type of connector discussed herein, or any combination thereof. In some examples, a digital asset tracking system includes one or more sensors.

[0220] In operation 1710, the digital asset management system is configured to identify and can identify a relationship between a media device and an anchor element associated with a certain token, based on sensor data. In some examples, the relationship between a media device and an anchor element may include interactions between the media device and the anchor element. Examples of anchor elements include anchor element 299, anchor element 1350, optical glyphs, specified areas, specified locations, specified sounds, etc.

[0221] In some examples, sensor data includes image data captured by at least one image sensor of at least one sensor of a media device. Anchor elements may include objects. Identifying the relationship between the media device and the anchor elements may include identifying that the image data depicts an object. For example, in some examples, an object includes an optical glyph, and information indicating a token is optically encoded based on the optical glyph, as shown in anchor element 1350. Examples of optical glyphs include quick response (QR) codes, barcodes, Aztec codes, dot codes, data matrices, shot codes, or combinations thereof. In some examples, reference image data depicting an object is stored in a data store (e.g., data store 298, data structure 650, data store 1370), and identifying that the image data depicts an object includes comparing the image data with the reference image data.

[0222] In some examples, the sensor data includes location data indicating the location of the media device. Examples of location data include: attitude data 225, sensor data 230, positioning information determined based on one or more communications 272 (e.g., by media device 205 and / or local device 270 and / or digital asset tracking system), stored communications in block 277, stored communications in block 278, positioning information determined using image sensor 815 and / or positioning sensor 820, positioning information determined based on one or more communications 835 (e.g., by media device 810 and / or local device 830 and / or digital asset tracking system), positioning information determined using image sensor 915 and / or positioning sensor 920, positioning information determined based on one or more communications 935 (e.g., by media device 910 and / or local device 930 and / or digital asset tracking system), image sensor 1015 and This includes positioning information determined using positioning sensor 1020, positioning information determined based on one or more communications 1035 (for example, by media device 1010 and / or local device 1030 and / or digital asset tracking system), positioning information determined using positioning sensor 1120, positioning information determined based on one or more communications 1135 (for example, by media device 1110 and / or local device 1130 and / or digital asset tracking system), positioning information determined using positioning sensor 1220, positioning information determined based on one or more communications 1235 (for example, by ownership device 1210 and / or local device 1230 and / or digital asset tracking system), positioning information determined using image sensor 1315 and / or positioning sensor 1320, the location of token device 1405, or a combination thereof.

[0223] In some examples, the anchor element includes an area, and identifying the relationship between the media device and the anchor element includes identifying that the media device's location is within that area. In some examples, the anchor element includes a location, and identifying the relationship between the media device and the anchor element includes identifying that the media device's location is within a threshold range from that location. In some examples, the threshold range for the area and / or location includes an area within the communication range of the local device. Examples of local devices may include the image acquisition and processing system 100, the image acquisition device 105A, the 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 shown in Figures 15A-15B, the computing system 1900, or a combination thereof.

[0224] In some examples, 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, an anchor element contains sound, and identifying the relationship between the media device and the anchor element includes identifying that the audio data contains sound. For example, if a particular song or a particular sound is playing in a certain area, the relationship between the media device and the anchor element may be identified by detecting the sound from the microphone recording by the media device.

[0225] In operation 1715, the digital asset management system is configured to identify and be able to identify a token in the payload of at least one block of the distributed ledger, and the token corresponds to media content according to the distributed ledger. For example, in the context of Figure 13, in response to identifying the relationship between media device 1310 and anchor element 1350 (e.g., media device 1310 scanning the QR code of anchor element 1350), the digital asset management system can identify token 1360 in the distributed ledger 1365, and token 1360 may correspond to digital asset 1340 (e.g., media content).

[0226] Examples of tokens may include tokens 600, 860, 960, 1060, 1160, 1260, 1360, 1420, or combinations thereof. Examples of distributed ledgers may include distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledger 1365, distributed ledger 1415, the distributed ledgers corresponding to the smart contracts in Figures 15A-15B, or combinations thereof. Examples of blocks may include block A505, block B535, block C565, block 710, block 720, block 730, block 740, block 750, block 760, or combinations thereof. Examples of payloads may include block A payload 530, block B payload 560, and block C payload 590. Tokens may be non-fungible tokens (NFTs).

[0227] In operation 1720, the digital asset management system is configured and can generate a representation of media content corresponding to a token. In operation 1725, in response to the identification of the relationship between the media device and the anchor element in operation 1720, the digital asset management system is configured and can output a representation of media content. For example, in the context of Figure 13, the representation of media content corresponding to a token may include the digital asset 1340, the virtual object 1345, information 1355 about the token 1360 associated with the digital asset 1340, one or more customizations 1357, or a combination thereof.

[0228] In some examples, outputting a representation of media content includes displaying at least a portion of the media content on a display (e.g., output device 1935). In some examples, outputting a representation of media content includes transmitting the representation of media content to a receiving device (e.g., using a communication interface 1940). An example of a receiving device may include any of the examples of media devices enumerated herein.

[0229] In some examples, a digital asset management system is configured to identify and be able to identify the media device orientation of a media device based on sensor data. Based on the media device orientation of the media device, the digital asset management system can determine the media content orientation of media content. In some examples, outputting a representation of media content includes outputting a representation of media content in orientation according to the media content orientation. Examples of media content orientation include customization 1357 of digital asset 1340, and / or any other modifications, customizations, and / or personalizations.

[0230] In some examples, a digital asset management system is configured and can identify, based on a distributed ledger, that the parameters of a token (e.g., token ownership 620, token smart contract 645) indicate that the token is associated with a first user. Based on the token parameters indicating that the token is associated with a first user, the digital asset management system can determine the visual effects for media content. The digital asset management system can apply the visual effects to the media content. In some examples, outputting a representation of the media content includes outputting a representation of the media content along with the applied visual effects. Examples of visual effects include customization 1357 of the digital asset 1340, as well as / or any other modifications, customizations, and / or personalizations.

[0231] In some examples, a digital asset management system can be configured and can determine, based on a data store, that a first user and a second user are associated according to their relationship. A media device is associated with the second user. Visual effects on media content can correspond to the relationship. For example, visual effects can indicate whether the first user and the second user are family, friends, spouses, significant others, colleagues, acquaintances, employer / employee, contractor / contractor, mentor / mentee, girlfriend / boyfriend, partner, or in some other relationship.

[0232] In some examples, a digital asset management system is configured and can determine that a media device is associated with a first user. Visual effects on media content correspond to the first user. For example, visual effects may indicate to the first user that the media content is unique to that first user and / or associated with a unique token of that first user.

[0233] In some examples, a digital asset management system can be configured and capable of determining, based on a data store, that a first user is a famous person. The visual effects on media content correspond to the first user being a famous person. In some examples, famous people of different categories may have different visual effects to distinguish them, for example, politicians, star athletes, musicians, movie stars, TV stars, famous scientists, etc.

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

[0235] In some examples, a digital asset management system is configured and can determine that tokens are identified in a data store. Visual effects for media content correspond to data stores. For example, a data store may contain records of tokens and / or media content. These records can identify and / or store visual effects. Examples of data stores include data store 298, data structure 650, and / or data store 1370.

[0236] In some examples, a digital asset management system can be configured to retrieve information about tokens from a distributed ledger and output information about tokens. An example of information about a token includes information 1355 about token 1360. In some examples, outputting information about a token includes displaying at least a portion of the information on a display, for example, as shown in Figure 13, where information 1355 is displayed on a media device 1310 together with the digital asset 1340. In some examples, the information identifies the distributed ledger. In some examples, a digital asset management system can be configured to identify, based on the distributed ledger, that the parameters of a token (e.g., token ownership 620, token smart contract 645) indicate that the token is associated with a first user. This information can identify the first user.

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

[0238] In some examples, a digital asset management system can be configured and can identify, based on a distributed ledger, that a token parameter (e.g., token smart contract 645) indicates that the token is associated with a smart contract. This information can identify the smart contract. In some examples, a digital asset management system can be configured and can identify, based on a distributed ledger, that a token parameter (e.g., token unit amount 615) indicates the amount of token instances, and this information identifies the amount of token instances.

[0239] In some examples, a digital asset management system can be configured to identify a transfer platform configured for token transfers (for example, for tokens to be purchased, sold, borrowed, licensed, or any combination thereof). The digital asset management system can output interface elements (for example, buttons, menus, or other user interface elements) corresponding to media content. The interface elements may be configured to initiate a token transfer using the transfer platform (for example, selling a token, buying a token, borrowing a token, leasing a token, and / or licensing a token) upon interaction with the interface element (for example, by a user of the digital asset management system through input device 1945).

[0240] In some examples, a digital asset management system performing process 1700 may include at least one of the following: a head-mounted display (HMD) (e.g., HMD310), a mobile handset (e.g., mobile handset410), a wireless communication device, or a combination thereof.

[0241] 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 a token based on the sensor data; means for identifying a token in the payload of at least one block 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 a representation of the media content in response to identifying the relationship between the media device and the anchor element.

[0242] In some examples, means for receiving sensor data include an image acquisition and processing system 100, an image sensor 130, a digital asset tracking system 200, one or more sensors 210, one or more attitude sensors 215, one or more media sensors 220, a first camera 330A, a second camera 330B, a first camera 430A, a second camera 430B, a third camera 430C, a fourth camera 430D, an image sensor 815, an image sensor 915, an image sensor 1015, an image sensor 1315, a positioning sensor 820, a positioning sensor 920, a positioning sensor 1020, a positioning sensor 1120, a positioning sensor 1220, a positioning sensor 1320, a media device 205, a network device 280, and a local device. The system includes S270, additional devices297, datastore298, anchor elements299, HMD310, mobile handset410, media device810, local device830, media device910, local device930, media device1010, local device1030, media device1110, local device1130, ownership device1210, local device1230, media device1310, distributed ledger1365, datastore1370, token device1405, one or more computing systems of Figure 15A, one or more computing systems of Figure 15B, computing system1900, input device1945, or a combination thereof.

[0243] In some examples, the means for identifying relationships and / or tokens are: 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 10 10, including 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 computing systems of Figure 15A, one or more computing systems of Figure 15B, computing system 1900, or a combination thereof.

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

[0245] Figure 18 is a flowchart showing 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 in Figure 2, or a part thereof. In some examples, the imaging system may include, for example, an image acquisition and processing system 100, an image acquisition device 105A, an image processing device 105B, an image processor 150, an ISP 154, a host processor 152, a digital asset tracking system 200, a media device 205, a network device 280, a local device 270, an additional device 297, a data store 298, an anchor element 299, an HMD 310, a mobile handset 410, a media device 810, a local device 830, a media device 910, a local device 930, a media device 1010, a local device 103 0, 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 computing systems of Figure 15A, one or more computing systems of Figure 15B, a digital asset management system running process 1600, a digital asset tracking system running process 1650, a digital asset management system running process 1700, computing system 1900, processor 1910, or a combination thereof.

[0246] In operation 1805, the digital asset management system is configured to identify and be able to identify a token corresponding to media content in the payload of at least one block of the distributed ledger. The token parameter in the distributed ledger indicates that the token is associated with a first user. Examples of tokens may include token 600, token 860, token 960, token 1060, token 1160, token 1260, token 1360, token 1420, or combinations thereof. Examples of distributed ledgers include distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledger 1365, distributed ledger 1415, the distributed ledgers corresponding to the smart contracts in Figures 15A-15B, or combinations thereof. Examples of blocks include block A505, block B535, block C565, block 710, block 720, block 730, block 740, block 750, block 760, or combinations thereof. Examples of payloads include block A payload 530, block B payload 560, and block C payload 590. Tokens may be non-fungible tokens (NFTs).

[0247] In operation 1810, the digital asset management system is configured to identify and be able to identify devices associated with tokens and media content. The devices are associated with a first user. Examples of devices include the image acquisition and processing system 100, image acquisition device 105A, image processing device 105B, media device 205, HMD 310, mobile handset 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 systems in Figures 15A-15B, computing system 1900, or combinations 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.

[0248] In some examples, the device is configured to display media content. For example, the device may be configured to display media content, as shown with respect to the token device 1405 which displays a digital asset 1425 corresponding to, for example, token 1420.

[0249] In some examples, device identifiers are stored in a distributed ledger (e.g., distributed ledger 295, blockchain ledger 500, DAG ledger 700, distributed ledger 1365, distributed ledger 1415, the distributed ledger corresponding to the smart contracts in Figures 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 identifying a device is based on its identifier.

[0250] In some examples, the device includes an interactive element that indicates a token, and identifying the token in operation 1805 is based on interaction with the interactive element. In some examples, the interaction includes an optical glyph, and the token identifier is optically encoded based on the optical glyph. In some examples, the optical glyph includes one or more QR codes, barcodes, Aztec codes, dot codes, data matrices, shot codes, or a combination thereof. Interacting with an interactive element that includes an optical glyph may include scanning the optical glyph and decoding the information optically encoded therein (e.g., a uniform resource locator (URL) and / or a uniform resource identifier (URI)). The interactive element may include a short-range wireless communication transceiver such as Near Field Communication (NFC), Radio Frequency Identification (RFID), Bluetooth®, WLAN, PAN, or any combination thereof. Interaction with an interaction element, including a short-range wireless communication transceiver, may include communicating with the short-range wireless communication transceiver (for example, transmitting and / or receiving one or more wireless signals to and / or from the short-range wireless communication transceiver).

[0251] In some examples, a digital asset management system is configured to receive image data and detect whether a device is represented in the image data. In some examples, based on the detection that a device is represented in the image data, the digital asset management system may identify a token in operation 1805. For example, in some examples, a digital asset management system may detect and / or recognize a device in image data based on a comparison with reference image data depicting the device and / or media content. In some examples, a digital asset management system may detect and / or recognize elements on a device, such as optical glyphs, by scanning the optical glyphs and decoding the information optically encoded therein (e.g., uniform resource locator (URL) and / or uniform resource identifier (URI)).

[0252] In operation 1815, the digital asset management system is configured and can identify that a device has moved to an area associated with a 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 one example for illustrative purposes, the first user in operation 1810 is first user 1410 in Figure 14, and the second user in operation 1815 is second user 1430 in Figure 14. In another example for illustrative purposes, the first user in operation 1810 is second user 1430 in Figure 14, and the second user in operation 1815 is first user 1410 in Figure 14.

[0253] In some examples, identifying that a device has moved to an area associated with a second user involves identifying that one or more additional devices located in that area are associated with the second user. For example, other devices in the area associated with the second user (e.g., other token devices, media devices, and / or computing systems) may contain information indicating that these devices belong to and / or are associated with the second user. The device may obtain this information by communicating with one or more of these additional devices, and the digital asset management system may identify the movement based on these communications.

[0254] In some examples, identifying that a device has moved to an area associated with a second user involves identifying that a wireless local area network (WLAN) within that area is associated with the second user. For example, a device may include a wireless network transceiver, which may search for and / or connect to WLAN networks, and may be capable of finding and / or connecting to a WLAN associated with the second user within an area associated with the second user, and a digital asset management system may identify the movement based on the device's discovery and / or connection to this WLAN.

[0255] In some examples, determining that a device has moved to an area related to a second user involves determining that location data from at least one of the device's location sensors indicates that the device is located in that area, and the area is a geographical area.

[0256] In some examples, determining that a device has moved to an area associated with a second user involves determining that location data from at least one of the device's location sensors indicates that the device is within range of the second user's location, and the area associated with the second user is within range of the second user's location. For example, the device may include location sensors such as a GNSS positioning receiver (e.g., positioning sensor 820, positioning sensor 920, positioning sensor 1020, positioning sensor 1120, positioning sensor 1220, positioning sensor 1320, or a combination thereof). The device's location sensors can determine the device's location, and the digital asset management system can determine the movement based on whether the device's location is within a predetermined geographical area associated with a second user.

[0257] In some examples, identifying that a device has moved to an area associated with a second user includes identifying that a device has moved from a first area associated with a first user. For example, when token device 1405 moves to an area associated with a second user 1430, token device 1405 also moves from an area associated with a first user 1410. Detection that a device has moved from a first area associated with a first user may be based on any of the types of detections listed above with respect to detecting that a device has moved to an area associated with a second user. For example, a digital asset management system may identify movement from a first area based on the fact that a device is no longer able to communicate with other devices associated with a first user in the first area, based on the fact that a device is no longer able to detect and / or connect to a WLAN associated with and / or within the first area, based on the fact that a user location sensor indicates a location that is no longer within a given geographic area associated with a first user, or a combination of these.

[0258] In operation 1820, in response to the determination that the device has moved to that area in operation 1815, the digital asset management system is configured and can be configured to modify the parameters of a token in the distributed ledger (e.g., token ownership 620, token smart contract 645) 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 can modify the parameters from indicating that the token is associated with a first user 1410 to indicating that the token is associated with a second user 1430.

[0259] In some examples, modifying the parameters of a token in a distributed ledger includes adding a new block to the distributed ledger. The parameters of a token in a distributed ledger can be modified based on the payload of a new block. In some examples, adding a new block to a distributed ledger includes generating a new block.

[0260] In some examples, a digital asset management system is configured and can send an authorization request to a first user device associated with a first user to modify the parameters of a token in a distributed ledger from indicating that the token is associated with a first user to indicating that the token is associated with a second user. The digital asset management system can receive authorization from the first user device. In some examples, the digital asset management system changes the parameters in operation 1820 in response to receiving this authorization from the first user device.

[0261] In some examples, a digital asset management system is configured and can send an authorization request to a second user device associated with a second user to modify the parameters of a token in a distributed ledger from indicating that the token is associated with a first user to indicating that the token is associated with a second user. The digital asset management system can receive authorization from the second user device. In some examples, the digital asset management system changes the parameters in operation 1820 in response to receiving this authorization from the second user device.

[0262] In some examples, a digital asset management system is configured to identify, and can identify, a smart contract associated with a token in a distributed ledger. The smart contract indicates that the token's parameters should be modified in response to a condition. Making the token's parameters in the distributed ledger modified, as in operation 1820, may involve executing a smart contract in response to identifying a condition. Identifying the condition is based on identifying that the device has moved to an area associated with a second user. Examples of smart contracts include token smart contract 645, the smart contracts in Figures 15A–15B, or combinations thereof. Smart contracts may be shown in a distributed ledger. An example of a condition is the condition in Figure 15B.

[0263] In some examples, a digital asset management system performing process 1800 may include at least one of the following: a head-mounted display (HMD) (e.g., HMD310), a mobile handset (e.g., mobile handset410), a wireless communication device, or a combination thereof.

[0264] In some examples, a digital asset management system includes, in the payload of at least one block of a distributed ledger, means for identifying a token corresponding to media content, wherein the parameters of the token in the distributed ledger indicate that the token is associated with a first user; means for identifying a device associated with the token and media content, wherein the device is associated with a first user; means for identifying that the device has moved to an area associated with a second user; and means for, in response to identifying that the device has moved to that area, to modify the parameters of the token in the distributed ledger from indicating that the token is associated with a first user to indicating that the token is associated with a second user.

[0265] In some examples, the means for identifying tokens and / or modifying token parameters are: 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, me The system includes a dea device 1010, a local device 1030, a media device 1110, a local device 1130, an ownership device 1210, a local device 1230, a media device 1310, an anchor element 1350, a distributed ledger 1365, a data store 1370, a token device 1405, a distributed ledger 1415, a token 1420, a local device 1435, one or more computing systems from Figure 15A, one or more computing systems from Figure 15B, a computing system 1900, or a combination thereof.

[0266] In some examples, means for identifying a device and / or for identifying that a device has moved to an area related to a second user include: 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 This includes 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 computing systems of Figure 15A, one or more computing systems of Figure 15B, computing system 1900, or a combination thereof.

[0267] In some examples, the processes described herein (for example, 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 the digital asset tracking system 200 shown in Figure 2. In some examples, process 1650 may be performed by a media device 205, a network device 280, a local device 270, or a combination thereof. In another example, process 1650 may be performed by a computing device with the computing system 1900 shown in Figure 19.

[0268] The computing device may include any suitable device, such as a mobile device (e.g., a cell phone), a desktop computing device, a tablet computing device, a wearable device (e.g., a VR headset, an AR headset, AR glasses, a network-connected watch or smartwatch, or other wearable device), a server computer, an autonomous vehicle or computing device for an autonomous vehicle, a robotic device, a television, and / or any other computing device having the resource capacity 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, the computing device may include a display, a network interface configured to communicate and / or receive data, any combination thereof, and / or other components. The network interface may be configured to communicate and / or receive Internet Protocol (IP) based data or other types of data.

[0269] The components of a computing device may be implemented in circuitry. For example, a component may include and / or be implemented using one or more programmable electronic circuits (e.g., a microprocessor, a graphics processing unit (GPU), a digital signal processor (DSP), a central processing unit (CPU), and / or other suitable electronic circuits), electronic circuits, or other electronic hardware, and / or may include and / or be implemented using computer software, firmware, or any combination thereof to perform the various operations described herein.

[0270] Process 1650 is presented as a logical flow diagram, and its operation represents a set of operations that can be implemented by hardware, computer instructions, or a combination thereof. In the context of computer instructions, operation represents a computer-executable instruction stored in one or more computer-readable storage media that, when executed by one or more processors, performs the described operation. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc., that perform a particular function or implement a particular data type. The order in which operations are described is not intended to be interpreted as restrictive, and any number of operations described may be combined in any order and / or in parallel to implement the process.

[0271] In addition, process 1650 and / or other processes described herein may be executed under the 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 executed collectively on one or more processors, by hardware, or in combination thereof. As stated 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 multiple instructions executable by one or more processors. The computer-readable or machine-readable storage medium may be non-temporary.

[0272] Figure 19 shows an example of a system for implementing several aspects of this technique. Specifically, Figure 19 shows an example of a computing system 1900, which could be, for example, an internal computing system, a remote computing system, a camera, or any computing device comprising any of those components of the system that communicate with each other using connections 1905. Connection 1905 could be a physical connection using a bus, or a direct connection to a processor 1910 in a chipset architecture, for example. Connection 1905 could also be a virtual connection, a network connection, or a logical connection.

[0273] In some embodiments, the computing system 1900 is a distributed system in which the functions described herein can be distributed across a data center, multiple data centers, a peer network, and so on. In some embodiments, one or more of the described system components represent many components, each performing some or all of the functions that are the subject of the component's description. In some embodiments, the components may be physical or virtual devices.

[0274] An exemplary system 1900 includes at least one processing unit (CPU or processor) 1910 and a connector 1905 that connects various system components to the processor 1910, including system memory 1915 such as read-only memory (ROM) 1920 and random access memory (RAM) 1925. The computing system 1900 may include a high-speed memory cache 1912 that is directly connected to the processor 1910, very close to the processor 1910, or integrated as part of the processor 1910.

[0275] Processor 1910 may include any general-purpose processors and hardware or software services, such as services 1932, 1934, and 1936, stored in memory device 1930, which are configured to control the processor 1910 and dedicated processors such that software instructions are incorporated into actual processor designs. Processor 1910 may essentially be a fully self-contained computing system including multiple cores or processors, buses, memory controllers, caches, etc. Multicore processors may be symmetrical or asymmetrical.

[0276] To enable user interaction, the computing system 1900 includes an input device 1945 which can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, a keyboard, a mouse, motion input, and speech. The computing system 1900 may also include an output device 1935 which may be one or more of several output mechanisms. In some cases, a multimodal system may allow the user to provide multiple types of input / output for communication with the computing system 1900. The computing system 1900 may include a communication interface 1940 which can generally control and manage user input and system output.Communication interfaces include audio jacks / plugs, microphone jacks / plugs, Universal Serial Bus (USB) ports / plugs, Apple® Lightning® ports / plugs, Ethernet ports / plugs, fiber optic ports / plugs, proprietary wired ports / plugs, Bluetooth® wireless signal transmission, Bluetooth® low energy (BLE) wireless signal transmission, IBEACON® wireless signal transmission, Radio Frequency Identification (RFID) wireless signal transmission, Near Field Communication (NFC) wireless signal transmission, Dedicated Short Range Communication (DSRC) wireless signal transmission, 802.11 Wi-Fi wireless signal transmission, Wireless Local Area Network (WLAN) signal transmission, Visible Light Communication (VLC), and Worldwide Interoperability for Microwave Access. The communication interface 1940 may perform or facilitate the reception and / or transmission of wired or wireless communications using wired and / or wireless transceivers, including but not limited to (WiMAX), infrared (IR) communication wireless signal transmission, public switched telephone network (PSTN) signal transmission, integrated services digital network (ISDN) signal transmission, 3G / 4G / 5G / LTE cellular data network wireless signal transmission, ad hoc network signal transmission, radio wave signal transmission, microwave signal transmission, infrared signal transmission, visible light signal transmission, ultraviolet light signal transmission, wireless signal transmission along the electromagnetic spectrum, or any combination thereof. The communication interface 1940 may also include one or more GNSS receivers or transceivers used to determine the position of the computing system 1900 based on the reception of one or more signals from one or more satellites associated with one or more Global Navigation Satellite Systems (GNSS) systems. GNSS systems include, but are not limited to, the US Global Positioning System (GPS), Russia's Global Navigation Satellite System (GLONASS), China's Beidou Navigation Satellite System (BDS), and Europe's Galileo GNSS.Since there are no constraints that apply to any specific hardware configuration, as development progresses, this basic feature may be easily replaced by improved hardware or firmware configurations.

[0277] The storage device 1930 may be a non-volatile and / or non-transitory and / or computer-readable memory device, may be a hard disk, or may be a magnetic cassette, a flash memory card, a solid-state memory device, a digital versatile disc, a cartridge, a floppy disk, a flexible disk, a hard disk, a magnetic tape, a magnetic strip / stripe, any other magnetic storage medium, a flash memory, a memristor memory, any other solid-state memory, a compact disc read only memory (CD-ROM) optical disc, a rewritable compact disc (CD) optical disc, a digital video disc (DVD) optical disc, a Blu-ray disc (BDD) optical disc, a holographic optical disc, another optical medium, a secure digital (SD) card, a micro secure digital (microSD) card, a Memory Stick (registered trademark) card, a smart card chip, an EMV chip, a subscriber identity module (SIM) card, a mini / micro / nano / pico SIM card, another integrated circuit (IC) chip / card, a random access memory (RAM), a static RAM (SRAM), a dynamic RAM (DRAM), a read only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a flash EPROM (FLASHEPROM), a cache memory (L1 / L2 / L3 / L4 / L5 / L#), a resistive random access memory (RRAM / ReRAM), a phase change memory (PCM), a spin transfer torque RAM (STT-RAM), another memory chip or cartridge, and / or a combination thereof, or any other type of computer-readable medium capable of storing computer-accessible data.

[0278] The memory device 1930 may include software services, servers, services, and the like, wherein when code defining such software is executed by the processor 1910, it causes the system to perform functions. In some embodiments, a hardware service that performs a particular function may include software components stored on a computer-readable medium that are connected to necessary hardware components such as the processor 1910, a connection 1905, and an output device 1935 to perform the function.

[0279] 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 instructions and / or data. A computer-readable medium may include non-transitory media on which data may be stored, excluding carrier waves and / or transitory electronic signals propagating wirelessly or over a wired connection. Examples of non-transitory media may include, but are not limited to, magnetic disks or magnetic tapes, optical storage media such as compact discs (CDs) or digital versatile discs (DVDs), flash memory, memories, or memory devices. A computer-readable medium may store code and / or machine-executable instructions that may represent a procedure, function, subprogram, program, routine, subroutine, module, software package, class, 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, and the like may be passed, forwarded, or transmitted using any suitable means, including memory sharing, message passing, token passing, network transmission, and the like.

[0280] In some embodiments, computer-readable storage devices, media, and memory may include cables or wireless signals, such as bitstreams. However, non-temporary computer-readable storage media, as referred to, explicitly exclude media such as energy, carrier signals, electromagnetic waves, and signals themselves.

[0281] Specific details are provided in the above description to give a complete understanding of the embodiments and examples provided herein. However, it will be understood by those skilled in the art that these embodiments may be practiced without these specific details. For clarity of description, in some cases the art may be presented as including individual functional blocks, each comprising a device, device components, and software, or steps or routines in a manner embodied in 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 as components in the form of block diagrams, so as not to obscure the embodiments with unnecessary details. In other cases, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary details, so as not to obscure the embodiments.

[0282] Individual embodiments may be described above as processes or methods represented as flowcharts, flow diagrams, data flow diagrams, structural diagrams, or block diagrams. While flowcharts may describe operations as sequential processes, many operations may be performed in parallel or simultaneously. In addition, the order of operations may be rearranged. A process terminates when its operations are complete, but may have additional steps not shown in the diagram. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to a calling function or main function.

[0283] The processes and methods described above may be implemented using computer-executable instructions that are stored or otherwise available from computer-readable media. Such instructions may include, for example, instructions and data that cause a general-purpose computer, a dedicated computer, or a processing device to perform a particular function or group of functions, or otherwise configure a general-purpose computer, a dedicated computer, or a processing device to perform such a function. The portion of computer resources used may be accessible over a network. Computer-executable instructions may be binary or intermediate format instructions, such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and / or information created during the methods described above include magnetic or optical disks, flash memory, USB devices with non-volatile memory, and network-connected storage devices.

[0284] Devices that implement processes and methods in accordance with 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, program code or code segments (e.g., computer program products) for performing the required tasks may be stored in computer-readable or machine-readable media. A processor may perform the required tasks. Typical examples of form factors include laptops, smartphones, mobile phones, tablet devices or other small form factor personal computers, personal digital assistants, rack-mount devices, and standalone devices. The functions described herein may also be embodied in peripheral devices or add-in cards. Such functions may also, as a further example, be implemented on circuit boards in different chips or on different processes running within a single device.

[0285] Instructions, a medium for transmitting such instructions, computing resources for executing the instructions, and other structures for supporting such computing resources are exemplary means for providing the functionality described herein.

[0286] In the above description, aspects of this application are described with reference to those specific embodiments, but those skilled in the art will recognize that this application is not limited thereto. Therefore, while exemplary embodiments of this application are described in detail herein, the concepts of the present invention may be embodied or utilized in various other ways, and it should be understood that, apart from the limitations of the prior art, the appended claims are intended to be interpreted as including such variations. Various features and aspects of the applications described above may be used individually or together. Furthermore, embodiments may be utilized in any number of environments and applications other than those described herein without departing from the broader spirit and scope of this specification. Therefore, this specification and the drawings should be considered illustrative rather than restrictive. For illustrative purposes, the methods have been described in a particular order. It should be understood that in alternative embodiments, the methods may be performed in an order different from that described.

[0287] Those skilled in the art will understand that the symbols or terms less than ("<") and greater than (">") used herein may be replaced by the symbols less than or equal to ("≦") and greater than or equal to ("≧"), respectively, without departing from the scope of this description.

[0288] When a component is described as "configured to perform certain actions," such configuration can be achieved, for example, by designing electronics or other hardware to perform the actions, by programming programmable electronics (e.g., a microprocessor or other suitable electronics) to perform the actions, or by any combination thereof.

[0289] The phrase "connected" refers to any component that is physically connected to another component, either directly or indirectly, and / or communicates with another component, either directly or indirectly (for example, connected to another component via a wired or wireless connection and / or other preferred communication interface).

[0290] The wording of a claim that includes "at least one of" a set and / or "one or more" of a set indicates that one member of the set or multiple members of the set (in any combination) satisfy the claim. For example, the wording of a claim that includes "at least one of A and B" means A, B, or A and B. In another example, the wording of a claim that includes "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 words "at least one of" a set and / or "one or more" of a set do not limit the set to items enumerated in the set. For example, the wording of a claim that includes "at least one of A and B" could mean A, B, or A and B, and could also include items not enumerated in the set A and B.

[0291] The various exemplary logic blocks, modules, circuits, and algorithmic steps described in relation to the embodiments disclosed herein may be implemented as electronic hardware, computer software, firmware, or a combination thereof. To clearly demonstrate this hardware- and software compatibility, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their function. Whether such functions are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functions in various ways for each specific application, but such decisions on implementation should not be construed as causing a departure from the scope of this application.

[0292] 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 a variety of devices, such as general-purpose computers, wireless communication device handsets, or integrated circuit devices with multiple applications, including applications in wireless communication device handsets and other devices. Any feature described as a module or component may be implemented together in an integrated logic device, or separately as individual but interoperable logic devices. When implemented in software, the technique may be at least partially implemented by a computer-readable data storage medium comprising program code that, when executed, performs 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 materials. The computer-readable medium may comprise memory or data storage media such as random access memory (RAM), for example 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, etc. The technique may, as an addition or alternative, be at least partially implemented by a computer-readable communication medium that carries or communicates program code in the form of instructions or data structures, such as propagating signals or waves, and which can be accessed, read, and / or executed by a computer.

[0293] 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 circuit configurations. Such processors may be configured to perform any of the techniques described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working with a DSP core, or any other such configuration. Accordingly, the term “processor” as used herein may refer to any of the above structures, any combination thereof, or any other structure or device suitable for implementing the techniques described herein. In addition, in some embodiments, the functions described herein may be provided in a dedicated software module or hardware module configured for encoding and decoding, or incorporated in a composite video encoder decoder (codec).

[0294] The embodiments for explaining this disclosure include the following:

[0295] Embodiment 1A. A device for generating tokens, the device comprising at least one memory and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to receive media content based on sensor data captured by at least one sensor of a media device, determine the location of the media device, determine that the location of the media device is within a geographical area, and generate a token corresponding to the media content in response to the determination that the location of the media device is within that geographical area, wherein the payload of at least one block of a distributed ledger identifies the token.

[0296] Embodiment 2A. The apparatus of Embodiment 1A, wherein the media content includes at least a portion of the sensor data.

[0297] Embodiment 3A. An apparatus according to either Embodiment 1A or 2A, wherein the media content includes an altered or modified version of at least a portion of the sensor data.

[0298] Embodiment 4A. An apparatus according to any one of Embodiments 1A to 3A, wherein the sensor data includes at least one image captured by at least one image sensor of at least one sensor of a media device, and the media content is based on at least one of the at least one image.

[0299] Embodiment 5A. An apparatus according to any one of Embodiments 1A to 4A, wherein at least one processor is configured to detect at least a portion of an environment in at least one image, and to determine the location of a media device based at least in part on the detection of at least that portion of the environment in at least one image.

[0300] Aspect 6A. The apparatus according to any one of Aspects 1A to 5A, wherein to determine that the location of the media device is within the geographical area, at least one processor is configured to detect at least a portion of an environment in at least one image and determine that at least the portion of the environment is located within the geographical area.

[0301] Aspect 7A. The apparatus according to any one of Aspects 1A to 6A, wherein at least one processor is configured to detect at least a portion of an individual in at least one image, determine the identity of the individual, and set a parameter of the token to indicate that the token is associated with the identity.

[0302] Aspect 8A. The apparatus according to any one of Aspects 1A to 7A, wherein sensor data includes positioning data based on reception of at least one wireless signal by at least one sensor, and to determine the location of the media device, at least one processor is configured to determine the location of the media device based at least in part on the positioning data.

[0303] Aspect 9A. The apparatus according to any one of Aspects 1A to 8A, wherein the at least one wireless signal includes 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.

[0304] Aspect 10A. The apparatus according to any one of Aspects 1A to 9A, wherein the at least one wireless signal includes a Global Navigation Satellite System (GNSS) signal from a GNSS satellite.

[0305] Aspect 11A. The apparatus according to any one of Aspects 1A to 10A, wherein the media content includes a map of the geographical area.

[0306] Embodiment 12A. An apparatus of any embodiment 1A to 11A, wherein at least one processor is configured to determine that the location of a media device is within a geographic area based on at least one communication between the media device and a local device associated with the geographic area.

[0307] Embodiment 13A. An apparatus according to any of Embodiments 1A to 12A, wherein the apparatus includes a local device.

[0308] Embodiment 14A. An apparatus according to any of Embodiments 1A to 13A, wherein the apparatus includes a media device.

[0309] Embodiment 15A. An apparatus according to any of Embodiments 1A to 14A, wherein the apparatus is located within a geographical area.

[0310] Embodiment 16A. An apparatus of any of Embodiments 1A to 15A, wherein at least one processor is configured to generate at least one block in response to determining that the location of a media device is within a geographical area, and at least one block is added to a distributed ledger.

[0311] Embodiment 17A. A device according to any of Embodiments 1A to 16A, wherein at least one block contains a hash of at least a portion of a previous block of a distributed ledger.

[0312] Embodiment 18A. An apparatus of any one of Embodiments 1A to 17A, wherein at least one processor is configured to generate a distributed ledger in response to determining that the location of a media device is within a geographical area.

[0313] Embodiment 19A. An apparatus of any embodiment 1A to 18A, wherein at least one processor is configured to send a request to a computing device to generate at least one block in response to determining that the location of a media device is within a geographical area, to receive at least one block, and to add at least one block to a distributed ledger.

[0314] Embodiment 20A. An apparatus according to any of Embodiments 1A to 19A, wherein at least one processor is configured to set the parameters of a token to indicate that the token is associated with a user, and the media device is associated with a user.

[0315] Embodiment 21A. An apparatus of any one of Embodiments 1A to 20A, wherein at least one processor is configured to determine, based on sensor data, that a geographic area contains at least a threshold number of people, and at least one processor is configured to generate a token corresponding to media content in response to the determination that the geographic area contains at least a threshold number of people.

[0316] Embodiment 22A. An apparatus according to any of Embodiments 1A to 21A, wherein the apparatus includes at least one of a head-mounted display (HMD), a mobile handset, or a wireless communication device.

[0317] Embodiment 23A. A method for generating a token, comprising the steps of: receiving media content based on sensor data captured by at least one sensor of a media device; determining the location of the media device and determining that the location of the media device is within a geographical area; and generating a token corresponding to the media content in response to the determination that the location of the media device is within that geographical area, wherein the payload of at least one block of a distributed ledger identifies the token.

[0318] Embodiment 24A. The method of Embodiment 23A, wherein the media content includes at least a portion of the sensor data.

[0319] Embodiment 25A. Any method of Embodiments 23A to 24A, wherein the media content includes an altered or modified portion of the sensor data.

[0320] Embodiment 26A. Any method of Embodiments 23A to 25A, wherein the sensor data includes at least one image captured by at least one image sensor of at least one sensor of a media device, and the media content is based on at least one of the at least one image.

[0321] Embodiment 27A. Any method of Embodiments 23A to 26A, wherein the step of determining the location of a media device includes the steps of detecting at least a portion of an environment in at least one image, and determining the location of a media device based at least in part on the detection of at least that portion of the environment in at least one image.

[0322] Embodiment 28A. Any method of Embodiments 23A to 27A, wherein the step of determining that the location of a media device is within a geographical area includes the steps of detecting at least a portion of an environment in at least one image and determining that at least that portion of the environment is located within a geographical area.

[0323] Embodiment 29A. Any method of Embodiments 23A to 28A, further comprising the steps of detecting at least a portion of an individual in at least one image, determining the identity of the individual, and setting parameters of a token to indicate that the token is associated with that identity.

[0324] Embodiment 30A. Any method of Embodiments 23A to 29A, wherein the sensor data includes positioning data based on the reception of at least one wireless signal by at least one sensor, and the step of determining the location of a media device includes the step of determining the location of a media device based at least a portion of the positioning data.

[0325] Embodiment 31A. Any method of Embodiments 23A to 30A, wherein at least one wireless signal includes a short-range wireless signal from a local device that is within the transmission range of the media device at least during the reception of at least one wireless signal by at least one sensor.

[0326] Embodiment 32A. Any method of Embodiments 23A to 31A, wherein at least one wireless signal includes a GNSS signal from a Global Navigation Satellite System (GNSS) satellite.

[0327] Embodiment 33A. Any method of Embodiments 23A to 32A, wherein the media content includes a map of a geographical area.

[0328] Embodiment 34A. Any method of Embodiments 23A to 33A, wherein the step of determining that the location of a media device is within a geographical area includes the step of determining that the location of a media device is within a geographical area based on at least one communication between the media device and a local device associated with the geographical area.

[0329] Embodiment 35A. Any of embodiments 23A to 34A, wherein the method is performed using an apparatus that includes a local device.

[0330] Embodiment 36A. Any of embodiments 23A to 35A, wherein the method is performed using an apparatus that includes a media device.

[0331] Embodiment 37A. Any of embodiments 23A to 36A, wherein the method is performed using an apparatus located within a geographical area.

[0332] Embodiment 38A. Any method of Embodiments 23A to 37A, further comprising the steps of generating at leas...

Claims

1. A device for managing the transfer of token devices, At least one memory, At least one processor coupled to the at least one memory, Identifying a token corresponding to media content in the payload of at least one block of a distributed ledger, wherein the parameters of the token in the distributed ledger indicate 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 and is configured to present the media content. Identifying that the device has moved to an area related to a second user, In response to the device identifying that it has moved to the area, the parameter of the token in the distributed ledger is modified from indicating that the token is associated with the first user to indicating that the token is associated with the second user. A processor configured to perform the following: A device equipped with the following features.

2. The apparatus according to claim 1, wherein an identifier for the device is stored in the distributed ledger, and the at least one processor is configured to identify the device based on the identifier.

3. The apparatus according to claim 1, wherein the device includes an interactive element that represents the token, and the at least one processor is configured to identify the token based on interaction with the interactive element.

4. The apparatus according to claim 3, wherein the dialogue element includes an optical glyph, and the identifier of the token is optically encoded based on the optical glyph.

5. The aforementioned at least one processor, Receive image data, The device is detected to be represented in the image data, Identifying the token based on the detection that the device is represented in the image data. The apparatus according to claim 1, configured as follows.

6. To determine that the device has moved to the area associated with the second user The at least one processor is The device has moved away from the first area associated with the first user. One or more additional devices located in the area are related to the second user. The thing, and / or The wireless local area network (WLAN) within the aforementioned area is for the second user Related to The apparatus according to claim 1, configured to identify.

7. The apparatus according to claim 1, wherein, in order to determine that the device has moved to the area relating to the second user, the at least one processor is configured to determine that location data from at least one location sensor of the device indicates that the device is located in the area, and the area is a geographical area.

8. The apparatus according to claim 1, wherein, in order to determine that the device has moved to the area relating to the second user, the at least one processor is configured to determine that location data from at least one location sensor of the device indicates that the device is located within the range of the second user's location, and the area relating to the second user is within the range of the second user's location.

9. The apparatus according to claim 1, wherein the at least one processor is configured to add a new block to the distributed ledger so that the parameters of the token in the distributed ledger are modified based on the payload of the new block.

10. The apparatus according to claim 9, wherein the at least one processor is configured to generate the new block so that the new block is added to the distributed ledger.

11. The aforementioned at least one processor, A request for authorization is sent to a first user device associated with the first user to modify the 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. The approval is obtained from the first user device. The apparatus according to claim 1, configured as follows.

12. The aforementioned at least one processor, A request for authorization is sent to a second user device associated with the second user to modify the 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. The approval is obtained from the second user device. The apparatus according to claim 1, configured as follows.

13. The aforementioned at least one processor, The apparatus according to claim 1, wherein the distributed ledger is configured to identify a smart contract relating to the token, the smart contract indicates that the parameters of the token should be modified in response to a condition, the at least one processor is configured to execute the smart contract in response to the identification of a condition so that the parameters of the token in the distributed ledger are modified, and the at least one processor is configured to identify the condition in response to the identification of the device moving to the area relating to the second user.

14. The apparatus according to claim 1, wherein the apparatus includes at least one of a head-mounted display (HMD), a mobile handset, or a wireless communication device.

15. A method for managing token device transfer, performed by at least one processor, A step of identifying a token corresponding to media content in the payload of at least one block of a distributed ledger, wherein the parameters of the token in the distributed ledger indicate that the token is associated with a first user. A step of identifying a device associated with the token and the media content, wherein the device is associated with the first user and is configured to present the media content; The steps include determining that the device has moved to an area associated with a second user, In response to the device identifying that it has moved to the area, the parameter of the token in the distributed ledger is modified from indicating that the token is associated with a first user to indicating that the token is associated with a second user. A method that includes [a certain feature].

Images