Patent Publication Number: US-2023162168-A1

Title: System for implementing resource access protocols within a networked medium

Description:
FIELD OF THE INVENTION 
     The present invention embraces a system for implementing resource access protocols within a networked medium. 
     BACKGROUND 
     As metaverse systems rise in prominence, users may be interested in owning virtual real estate within one or more interactive virtual worlds with ownership of such virtual real estate represented in the form of an NFT. There is a need for a system for implementing resource access protocols within a networked medium. 
     SUMMARY 
     The following presents a simplified summary of one or more embodiments of the present invention, in order to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments and is intended to neither identify key or critical elements of all embodiments nor delineate the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments of the present invention in a simplified form as a prelude to the more detailed description that is presented later. 
     In one aspect, a system for implementing resource access protocols within a networked medium is presented. The system comprising: at least one non-transitory storage device; and at least one processing device coupled to the at least one non-transitory storage device, wherein the at least one processing device is configured to: electronically receive, from a second user input device of a second user, a request to access a resource in the metaverse, wherein the resource is associated with a first user; retrieve, from a distributed ledger associated with the first user, a non-fungible token (NFT) of the resource in response to the request; retrieve, from a licensing layer associated with the NFT of the resource, one or more licensing rules associated with access to the resource; determine, using a valuation engine, a value associated with access to the resource based on at least the one or more licensing rules; transmit control signals configured to cause the one or more licensing rules and the value associated with the access to the resource to be displayed on the second user input device; electronically receive, from the second user input device, an indication acknowledging the one or more licensing rules and a digital transfer of an amount of funds corresponding to the value associated with the access to the resource; and authorize the second user input device to access the resource in the metaverse. 
     In some embodiments, the at least one processing device is further configured to: receive an indication that the second user input device has accessed the resource; generate, using an NFT generator, an updated NFT for the resource based on at least receiving the indication that the second user input has accessed the resource; and link the updated NFT for the resource with the second user input device. 
     In some embodiments, linking the updated NFT for the resource with the second user input device further comprises: retrieving a unique device identifier associated with the second user input device; generating, using the NFT generator, a first metadata layer for the updated NFT for the resource; and storing the unique device identifier in the first metadata layer of the updated NFT for the resource. 
     In some embodiments, the at least one processing device is further configured to: determine, using the valuation engine, an updated value of the resource based on at least receiving the indication that the second user input has accessed the resource; generate, using the NFT generator, a second metadata layer of the updated NFT for the resource; and store the updated value of the resource in the second metadata layer of the updated NFT for the resource. 
     In some embodiments, the at least one processing device is further configured to: record the updated NFT for the resource on the distributed ledger; and transmit control signals configured to cause a first user input device of the first user to display a notification indicating the recording. 
     In some embodiments, wherein recording the updated NFT for the resource on the distributed ledger further comprises: generating a first transaction object for the updated NFT for the resource; and deploying the first transaction object on the distributed ledger. 
     In some embodiments, deploying the first transaction object further comprises: capturing a distributed ledger address associated with the recording; generating a notification indicating that the first transaction object has been created for the updated NFT for the resource in the distributed ledger, wherein the notification comprises at least the distributed ledger address; and transmitting control signals configured to cause the first user input device to display the notification. 
     In another aspect, a computer program product for implementing resource access protocols within a networked medium is presented. The computer program product comprising a non-transitory computer-readable medium comprising code causing a first apparatus to: electronically receive, from a second user input device of a second user, a request to access a resource in the metaverse, wherein the resource is associated with a first user; retrieve, from a distributed ledger associated with the first user, a non-fungible token (NFT) of the resource in response to the request; retrieve, from a licensing layer associated with the NFT of the resource, one or more licensing rules associated with access to the resource; determine, using a valuation engine, a value associated with access to the resource based on at least the one or more licensing rules; transmit control signals configured to cause the one or more licensing rules and the value associated with the access to the resource to be displayed on the second user input device; electronically receive, from the second user input device, an indication acknowledging the one or more licensing rules and a digital transfer of an amount of funds corresponding to the value associated with the access to the resource; and authorize the second user input device to access the resource in the metaverse. 
     In yet another aspect, a method for implementing resource access protocols within a networked medium is presented. The method comprising: electronically receiving, from a second user input device of a second user, a request to access a resource in the metaverse, wherein the resource is associated with a first user; retrieving, from a distributed ledger associated with the first user, a non-fungible token (NFT) of the resource in response to the request; retrieving, from a licensing layer associated with the NFT of the resource, one or more licensing rules associated with access to the resource; determining, using a valuation engine, a value associated with access to the resource based on at least the one or more licensing rules; transmitting control signals configured to cause the one or more licensing rules and the value associated with the access to the resource to be displayed on the second user input device; electronically receiving, from the second user input device, an indication acknowledging the one or more licensing rules and a digital transfer of an amount of funds corresponding to the value associated with the access to the resource; and authorizing the second user input device to access the resource in the metaverse. 
     The features, functions, and advantages that have been discussed may be achieved independently in various embodiments of the present invention or may be combined with yet other embodiments, further details of which can be seen with reference to the following description and drawings. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The patent or application file contains at least one drawing executed in color. Copies of this patent or patent application publication with color drawing(s) will be provided by the Office upon request and payment of the necessary fee. 
       Having thus described embodiments of the invention in general terms, reference will now be made the accompanying drawings, wherein: 
         FIG.  1    illustrates technical components of a system for implementing resource access protocols within a networked medium, in accordance with an embodiment of the invention; 
         FIG.  2    illustrates a process flow for implementing resource access protocols within a networked medium, in accordance with an embodiment of the invention. 
     
    
    
     DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION 
     Embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Where possible, any terms expressed in the singular form herein are meant to also include the plural form and vice versa, unless explicitly stated otherwise. Also, as used herein, the term “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein. Furthermore, when it is said herein that something is “based on” something else, it may be based on one or more other things as well. In other words, unless expressly indicated otherwise, as used herein “based on” means “based at least in part on” or “based at least partially on.” Like numbers refer to like elements throughout. 
     As used herein, an “entity” may be any institution employing information technology resources and particularly technology infrastructure configured for processing large amounts of data. Typically, these data can be related to the people who work for the organization, its products or services, the customers or any other aspect of the operations of the organization. As such, the entity may be any institution, group, association, financial institution, establishment, company, union, authority or the like, employing information technology resources for processing large amounts of data. 
     As described herein, a “user” may be an individual associated with an entity. As such, in some embodiments, the user may be an individual having past relationships, current relationships or potential future relationships with an entity. In some embodiments, a “user” may be an employee (e.g., an associate, a project manager, an IT specialist, a manager, an administrator, an internal operations analyst, or the like) of the entity or enterprises affiliated with the entity, capable of operating the systems described herein. In some embodiments, a “user” may be any individual, entity or system who has a relationship with the entity, such as a customer or a prospective customer. In other embodiments, a user may be a system performing one or more tasks described herein. 
     As used herein, a “user interface” may be any device or software that allows a user to input information, such as commands or data, into a device, or that allows the device to output information to the user. For example, the user interface includes a graphical user interface (GUI) or an interface to input computer-executable instructions that direct a processing device to carry out specific functions. The user interface typically employs certain input and output devices to input data received from a user second user or output data to a user. These input and output devices may include a display, mouse, keyboard, button, touchpad, touch screen, microphone, speaker, LED, light, joystick, switch, buzzer, bell, and/or other user input/output device for communicating with one or more users. 
     As used herein, an “engine” may refer to core elements of a computer program, or part of a computer program that serves as a foundation for a larger piece of software and drives the functionality of the software. An engine may be self-contained, but externally-controllable code that encapsulates powerful logic designed to perform or execute a specific type of function. In one aspect, an engine may be underlying source code that establishes file hierarchy, input and output methods, and how a specific part of a computer program interacts or communicates with other software and/or hardware. The specific components of an engine may vary based on the needs of the specific computer program as part of the larger piece of software. In some embodiments, an engine may be configured to retrieve resources created in other computer programs, which may then be ported into the engine for use during specific operational aspects of the engine. An engine may be configurable to be implemented within any general purpose computing system. In doing so, the engine may be configured to execute source code embedded therein to control specific features of the general purpose computing system to execute specific computing operations, thereby transforming the general purpose system into a specific purpose computing system. 
     As used herein, “authentication credentials” may be any information that can be used to identify of a user. For example, a system may prompt a user to enter authentication information such as a username, a password, a personal identification number (PIN), a passcode, biometric information (e.g., iris recognition, retina scans, fingerprints, finger veins, palm veins, palm prints, digital bone anatomy/structure and positioning (distal phalanges, intermediate phalanges, proximal phalanges, and the like), an answer to a security question, a unique intrinsic user activity, such as making a predefined motion with a user device. This authentication information may be used to authenticate the identity of the user (e.g., determine that the authentication information is associated with the account) and determine that the user has authority to access an account or system. In some embodiments, the system may be owned or operated by an entity. In such embodiments, the entity may employ additional computer systems, such as authentication servers, to validate and certify resources inputted by the plurality of users within the system. The system may further use its authentication servers to certify the identity of users of the system, such that other users may verify the identity of the certified users. In some embodiments, the entity may certify the identity of the users. Furthermore, authentication information or permission may be assigned to or required from a user, application, computing node, computing cluster, or the like to access stored data within at least a portion of the system. 
     It should also be understood that “operatively coupled,” as used herein, means that the components may be formed integrally with each other, or may be formed separately and coupled together. Furthermore, “operatively coupled” means that the components may be formed directly to each other, or to each other with one or more components located between the components that are operatively coupled together. Furthermore, “operatively coupled” may mean that the components are detachable from each other, or that they are permanently coupled together. Furthermore, operatively coupled components may mean that the components retain at least some freedom of movement in one or more directions or may be rotated about an axis (i.e., rotationally coupled, pivotally coupled). Furthermore, “operatively coupled” may mean that components may be electronically connected and/or in fluid communication with one another. 
     As used herein, an “interaction” may refer to any communication between one or more users, one or more entities or institutions, and/or one or more devices, nodes, clusters, or systems within the system environment described herein. For example, an interaction may refer to a transfer of data between devices, an accessing of stored data by one or more nodes of a computing cluster, a transmission of a requested task, or the like. 
     As used herein, “metaverse” may refer to a collection of persistent, shared, three-dimensional virtual spaces linked into a perceived virtual universe. In some embodiments, metaverse may not only refer to virtual worlds, but the Internet as a whole, including the spectrum of augmented reality. Metaverse may include a number of different elements such as video conferencing, digital currencies, virtual reality platforms, social media, live data streaming, digital representations of real-life objects and/or the like. In some embodiments, the metaverse may include virtual properties, such as virtual land parcels and estates for users to create and build-on, or structures that reflect real-life properties and/or completely original creations. These spaces may be represented by co-ordinates on the metaverse platform where users can meet up using their avatars to socialize and decorate their own spaces with collectibles. Any combination of the aforementioned elements may form a computer-mediated virtual environment, i.e., a virtual world, within the metaverse. Within this self-sustaining, persistent, and shared realm, users may exist and interact with each other using their digital avatars. 
     As used herein, a “resource” may generally refer to objects, products, devices, real estate, goods, commodities, services, and the like, and/or the ability and opportunity to access and use the same in the metaverse. Some example implementations herein contemplate digital property held by a user, including property that is stored and/or maintained by a third-party entity. 
     As used herein, a “resource transfer,” “resource distribution,” or “resource allocation” may refer to any transaction, activities, or communication between one or more entities, or between the user and the one or more entities in dealing with a resource. A resource transfer may refer to any distribution of resources such as, but not limited to, a payment, processing of funds, purchase of goods or services, a return of goods or services, a payment transaction, a credit transaction, or other interactions involving a user’s resource. In some embodiments, the user may authorize a resource transfer using at least a resource transfer instrument (credit cards, debit cards, checks, digital wallets, currency, loyalty points), and/or payment credentials (account numbers, resource transfer instrument identifiers). Unless specifically limited by the context, a “resource transfer” a “transaction”, “transaction event” or “point of transaction event” may refer to any activity between a user, a merchant, an entity, or any combination thereof. In some embodiments, a resource transfer or transaction may refer to financial transactions involving direct or indirect movement of funds through traditional paper transaction processing systems (i.e. paper check processing) or through electronic transaction processing systems in dealing with a resource. 
     As used herein, a “non-fungible token” or “NFT” may refer to a digital unit of data used as a unique digital identifier for a resource. An NFT may be stored on a distributed ledger that certifies ownership and authenticity of the resource. For purposes of this invention, a distributed ledger (e.g., blockchain) may be a database that is consensually shared and synchronized across multiple sites, institutions, or geographies, accessible by multiple people. A distributed ledger may be associated with independent computers (referred to as nodes) that record, share and synchronize transactions in their respective electronic ledgers (instead of keeping data centralized as in a traditional ledger). As such, NFTs cannot be copied, substituted, or subdivided. In specific embodiments, the NFT may include at least relationship layer, a token layer, a metadata layer(s), and a licensing layer. The relationship layer may include a map of various users that are associated with the NFT and their relationship to one another. For example, if the NFT is purchased by buyer B1 from a seller S1, the relationship between B1 and S1 as a buyer-seller is recorded in the relationship layer. In another example, if the NFT is owned by O1 and the resource itself is stored in a storage facility by storage provider SP1, then the relationship between O1 and SP1 as owner-file storage provider is recorded in the relationship layer. The token layer may include a smart contract that points to a series of metadata associated with the resource, and provides information about supply, authenticity, lineage, and provenance of the resource. The metadata layer(s) may include resource descriptors that provides information about the resource itself (e.g., resource information). These resource descriptors may be stored in the same metadata layer or grouped into multiple metadata layers. The licensing layer may include any restrictions and licensing rules associated with purchase, sale, and any other types of transfer of the resource from one person to another. Those skilled in the art will appreciate that various additional layers and combinations of layers can be configured as needed without departing from the scope and spirit of the invention. 
     The present invention provides a system for valuation and ownership management of resources within the metaverse. As metaverse systems rise in prominence, users may be interested in owning virtual real estate within one or more interactive virtual worlds. The ownership of such virtual real estate may be represented in the form of an NFT. The present invention provides the functional benefit of using a valuation engine to appraise digital real-estate to help users track the value of their metaverse properties. In addition, the present invention provides the functional benefit of implementing an access management module to allow users to control access to their metaverse properties. The access management module acts as a platform where users can offer licensing/rental terms for conditioned access to their metaverse properties. Valuation of metaverse properties may be analogous to valuation of real-property in the physical world. For example, proximity to other high value or popular metaverse areas may drive the value of certain metaverse property. In addition, the present invention provides the functional benefit of maintaining a record of users who access certain metaverse properties. This may also influence the value of a metaverse property. For instance, a well-known public figure or celebrity may have owned, rented, or visited a certain area within the metaverse, and this may drive the value of that area up. 
       FIG.  1    presents an exemplary block diagram of the system environment for implementing resource access protocols within a networked medium  100 , in accordance with an embodiment of the invention.  FIG.  1    provides a unique system that includes specialized servers and system communicably linked across a distributive network of nodes required to perform the functions of the process flows described herein in accordance with embodiments of the present invention. 
     As illustrated, the system environment  100  includes a network  110 , a system  130 , and a user input device  140 . In some embodiments, the system  130 , and the user input device  140  may be used to implement the processes described herein, in accordance with an embodiment of the present invention. In this regard, the system  130  and/or the user input device  140  may include one or more applications stored thereon that are configured to interact with one another to implement any one or more portions of the various user interfaces and/or process flow described herein. For example, the system  130  and/or the user input device  140  may include augmented and/or virtual reality applications configured to create immersive visual environments that make up the metaverse. These applications not only allow the user to access the metaverse, but also enable users to communicate with other users accessing the metaverse within the immersive visual environments. 
     In accordance with embodiments of the invention, the system  130  is intended to represent various forms of digital computers, such as laptops, desktops, video recorders, audio/video player, radio, workstations, servers, wearable devices, Internet-of-things devices, electronic kiosk devices, blade servers, mainframes, or any combination of the aforementioned capable of running applications required to execute the processes describe herein. In accordance with embodiments of the invention, the user input device  140  is intended to represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smartphones, augmented reality (AR) devices, virtual reality (VR) devices, extended reality (XR) devices, and other similar computing devices capable of running applications required to execute the processes describe herein. The components shown here, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed in this document. 
     In accordance with some embodiments, the system  130  may include a processor  102 , memory  104 , a storage device  106 , a high-speed interface  108  connecting to memory  104 , and a low-speed interface  112  connecting to low speed bus  114  and storage device  106 . Each of the components  102 ,  104 ,  106 ,  108 ,  111 , and  112  are interconnected using various buses, and may be mounted on a common motherboard or in other manners as appropriate. The processor  102  can process instructions for execution within the system  130 , including instructions stored in the memory  104  or on the storage device  106  to display graphical information for a GUI on an external input/output device, such as display  116  coupled to a high-speed interface  108 . In other implementations, multiple processors and/or multiple buses may be used, as appropriate, along with multiple memories and types of memory. Also, multiple systems, same or similar to system  130  may be connected, with each system providing portions of the necessary operations (e.g., as a server bank, a group of blade servers, or a multi-processor system). In some embodiments, the system  130  may be a server managed by the business. The system  130  may be located at the facility associated with the business or remotely from the facility associated with the business. 
     The memory  104  stores information within the system  130 . In one implementation, the memory  104  is a volatile memory unit or units, such as volatile random access memory (RAM) having a cache area for the temporary storage of information. In another implementation, the memory  104  is a non-volatile memory unit or units. The memory  104  may also be another form of computer-readable medium, such as a magnetic or optical disk, which may be embedded and/or may be removable. The non-volatile memory may additionally or alternatively include an EEPROM, flash memory, and/or the like. The memory  104  may store any one or more of pieces of information and data used by the system in which it resides to implement the functions of that system. In this regard, the system may dynamically utilize the volatile memory over the non-volatile memory by storing multiple pieces of information in the volatile memory, thereby reducing the load on the system and increasing the processing speed. 
     The storage device  106  is capable of providing mass storage for the system  130 . In one aspect, the storage device  106  may be or contain a computer-readable medium, such as a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory or other similar solid state memory device, or an array of devices, including devices in a storage area network or other configurations. A computer program product can be tangibly embodied in an information carrier. The computer program product may also contain instructions that, when executed, perform one or more methods, such as those described above. The information carrier may be a non-transitory computer- or machine-readable storage medium, such as the memory  104 , the storage device  104 , or memory on processor  102 . 
     In some embodiments, the system  130  may be configured to access, via the network  110 , a number of other computing devices (not shown) in addition to the user input device  140 . In this regard, the system  130  may be configured to access one or more storage devices and/or one or more memory devices associated with each of the other computing devices. In this way, the system  130  may implement dynamic allocation and de-allocation of local memory resources among multiple computing devices in a parallel or distributed system. Given a group of computing devices and a collection of interconnected local memory devices, the fragmentation of memory resources is rendered irrelevant by configuring the system  130  to dynamically allocate memory based on availability of memory either locally, or in any of the other computing devices accessible via the network. In effect, it appears as though the memory is being allocated from a central pool of memory, even though the space is distributed throughout the system. This method of dynamically allocating memory provides increased flexibility when the data size changes during the lifetime of an application and allows memory reuse for better utilization of the memory resources when the data sizes are large. 
     The high-speed interface  108  manages bandwidth-intensive operations for the system  130 , while the low speed controller  112  manages lower bandwidth-intensive operations. Such allocation of functions is exemplary only. In some embodiments, the high-speed interface  108  is coupled to memory  104 , display  116  (e.g., through a graphics processor or accelerator), and to high-speed expansion ports  111 , which may accept various expansion cards (not shown). In such an implementation, low-speed controller  112  is coupled to storage device  106  and low-speed expansion port  114 . The low-speed expansion port  114 , which may include various communication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet), may be coupled to one or more input/output devices, such as a keyboard, a pointing device, a scanner, or a networking device such as a switch or router, e.g., through a network adapter. 
     The system  130  may be implemented in a number of different forms, as shown in  FIG.  1   . For example, it may be implemented as a standard server, or multiple times in a group of such servers. Additionally, the system  130  may also be implemented as part of a rack server system or a personal computer such as a laptop computer. Alternatively, components from system  130  may be combined with one or more other same or similar systems and an entire system  130  may be made up of multiple computing devices communicating with each other. 
       FIG.  1    also illustrates a user input device  140 , in accordance with an embodiment of the invention. The user input device  140  includes a processor  152 , memory  154 , an input/output device such as a display  156 , a communication interface  158 , and a transceiver  160 , among other components. The user input device  140  may also be provided with a storage device, such as a microdrive or other device, to provide additional storage. Each of the components  152 ,  154 ,  158 , and  160 , are interconnected using various buses, and several of the components may be mounted on a common motherboard or in other manners as appropriate. 
     The processor  152  is configured to execute instructions within the user input device  140 , including instructions stored in the memory  154 . The processor may be implemented as a chipset of chips that include separate and multiple analog and digital processors. The processor may be configured to provide, for example, for coordination of the other components of the user input device  140 , such as control of user interfaces, applications run by user input device  140 , and wireless communication by user input device  140 . 
     The processor  152  may be configured to communicate with the user through control interface  164  and display interface  166  coupled to a display  156 . The display  156  may be, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display) or an OLED (Organic Light Emitting Diode) display, or other appropriate display technology. The display interface  156  may comprise appropriate circuitry and configured for driving the display  156  to present graphical and other information to a user. The control interface  164  may receive commands from a user and convert them for submission to the processor  152 . In addition, an external interface  168  may be provided in communication with processor  152 , so as to enable near area communication of user input device  140  with other devices. External interface  168  may provide, for example, for wired communication in some implementations, or for wireless communication in other implementations, and multiple interfaces may also be used. 
     The memory  154  stores information within the user input device  140 . The memory  154  can be implemented as one or more of a computer-readable medium or media, a volatile memory unit or units, or a non-volatile memory unit or units. Expansion memory may also be provided and connected to user input device  140  through an expansion interface (not shown), which may include, for example, a SIMM (Single In Line Memory Module) card interface. Such expansion memory may provide extra storage space for user input device  140  or may also store applications or other information therein. In some embodiments, expansion memory may include instructions to carry out or supplement the processes described above and may include secure information also. For example, expansion memory may be provided as a security module for user input device  140  and may be programmed with instructions that permit secure use of user input device  140 . In addition, secure applications may be provided via the SIMM cards, along with additional information, such as placing identifying information on the SIMM card in a non-hackable manner. In some embodiments, the user may use the applications to execute processes described with respect to the process flows described herein. Specifically, the application executes the process flows described herein. 
     The memory  154  may include, for example, flash memory and/or NVRAM memory. In one aspect, a computer program product is tangibly embodied in an information carrier. The computer program product contains instructions that, when executed, perform one or more methods, such as those described herein. The information carrier is a computer-or machine-readable medium, such as the memory  154 , expansion memory, memory on processor  152 , or a propagated signal that may be received, for example, over transceiver  160  or external interface  168 . 
     In some embodiments, the user may use the user input device  140  to transmit and/or receive information or commands to and from the system  130  via the network  110 . Any communication between the system  130  and the user input device  140  (or any other computing devices) may be subject to an authentication protocol allowing the system  130  to maintain security by permitting only authenticated users (or processes) to access the protected resources of the system  130 , which may include servers, databases, applications, and/or any of the components described herein. To this end, the system  130  may require the user (or process) to provide authentication credentials to determine whether the user (or process) is eligible to access the protected resources. Once the authentication credentials are validated and the user (or process) is authenticated, the system  130  may provide the user (or process) with permissioned access to the protected resources. Similarly, the user input device  140  (or any other computing devices) may provide the system  130  with permissioned to access the protected resources of the user input device  130  (or any other computing devices), which may include a GPS device, an image capturing component (e.g., camera), a microphone, a speaker, and/or any of the components described herein. 
     The user input device  140  may communicate with the system  130  (and one or more other devices) wirelessly through communication interface  158 , which may include digital signal processing circuitry where necessary. Communication interface  158  may provide for communications under various modes or protocols, such as GSM voice calls, SMS, EMS, or MMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others. Such communication may occur, for example, through radio-frequency transceiver  160 . In addition, short-range communication may occur, such as using a Bluetooth, Wi-Fi, or other such transceiver (not shown). In addition, GPS (Global Positioning System) receiver module  170  may provide additional navigation - and location-related wireless data to user input device  140 , which may be used as appropriate by applications running thereon, and in some embodiments, one or more applications operating on the system  130 . 
     The user input device  140  may also communicate audibly using audio codec  162 , which may receive spoken information from a user and convert it to usable digital information. Audio codec  162  may likewise generate audible sound for a user, such as through a speaker, e.g., in a handset of user input device  140 . Such sound may include sound from voice telephone calls, may include recorded sound (e.g., voice messages, music files, etc.) and may also include sound generated by one or more applications operating on the user input device  140 , and in some embodiments, one or more applications operating on the system  130 . 
     Various implementations of the systems and techniques described here can be realized in digital electronic circuitry, integrated circuitry, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and/or combinations thereof. These various implementations can include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. 
     These computer programs (also known as programs, software, software applications or code) include machine instructions for a programmable processor and can be implemented in a high-level procedural and/or object-oriented programming language, and/or in assembly/machine language. As used herein, the terms “machine-readable medium” “computer-readable medium” refers to any computer program product, apparatus and/or device (e.g., magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term “machine-readable signal” refers to any signal used to provide machine instructions and/or data to a programmable processor. 
     To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user and a keyboard and a pointing device (e.g., a mouse or a trackball) by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including acoustic, speech, or tactile input. 
     The systems and techniques described here can be implemented in a technical environment that includes a back end component (e.g., as a data server), that includes a middleware component (e.g., an application server), that includes a front end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back end, middleware, or front end components. 
     As shown in  FIG.  1   , the components of the system  130  and the user input device  140  are interconnected using the network  110 . The network  110 , which may be include one or more separate networks, be a form of digital communication network such as a telecommunication network, a local area network (“LAN”), a wide area network (“WAN”), a global area network (“GAN”), the Internet, or any combination of the foregoing. It will also be understood that the network  110  may be secure and/or unsecure and may also include wireless and/or wired and/or optical interconnection technology. 
     In accordance with an embodiments of the invention, the components of the system environment  100 , such as the system  130  and the user input device  140  may have a client-server relationship, where the user input device  130  makes a service request to the system  130 , the system  130  accepts the service request, processes the service request, and returns the requested information to the user input device  140 , and vice versa. This relationship of client and server typically arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. 
     It will be understood that the embodiment of the system environment  100  illustrated in  FIG.  1    is exemplary and that other embodiments may vary. As another example, in some embodiments, the system environment may include more, fewer, or different components. As another example, in some embodiments, some or all of the portions of the system environment  100  may be combined into a single portion. Likewise, in some embodiments, some, or all of the portions of the system  130  may be separated into two or more distinct portions. 
       FIG.  2    illustrates a process flow for implementing resource access protocols within a networked medium, in accordance with an embodiment of the invention. As shown in block  202 , the process flow includes electronically receiving, from a second user input device of a second user, a request to access a resource in the metaverse, wherein the resource is associated with a first user. As described herein, the metaverse may include resources such as virtual properties - such as virtual land parcels and estates for users to create and build-on, or structures that reflect real-life properties and/or completely original creations. In some embodiments, these resources may be represented by co-ordinates on the metaverse platform. Accordingly, the request to access the resource may include specific co-ordinates identifying the location of the resource, a description of the resource, and/or access description specifying the type of access requested. 
     Next, as shown in block  204 , the process flow includes retrieving, from a distributed ledger associated with the first user, a non-fungible token (NFT) of the resource in response to the request. In some embodiments, resources in the metaverse may be associated with a user having ownership interest over them. This ownership interest of the user may be represented and recorded in NFTs and stored in a distributed ledger associated with the user. As described herein, an NFT is a unique digital identifier for the resource that certifies ownership and authenticity of the resource in the metaverse. 
     Next, as shown in block  206 , the process flow includes retrieving, from a licensing layer associated with the NFT of the resource, one or more licensing rules associated with access to the resource. As described herein, the licensing layer may include one or more licensing rules that define one or more conditions for access (e.g., purchase, sale, and any other types of transfer of the resource) to the resource. In some embodiments, the licensing rules may be determined by the individual/entity that has an ownership interest in the resource (e.g., the first user). In one aspect, when the user attains ownership of a resource in the metaverse, the system may be configured to generate, using the NFT generator, an NFT for the resource as a way to record ownership of the resource. 
     Having ownership interest of the resource, the user may wish to allow other users (e.g., the second user) to access the resource within the metaverse for value. To this end, the first user may determine specific conditions for access to the resource. In some embodiments, the access may be tiered, and each tier of access may be associated with a specific set of conditions. For a user (e.g., the second user) to access a particular tier, the user will have to satisfy the conditions specific to that tier. Depending on the tier of access, the user may be allowed to execute a particular set of actions on the resource. In one example, a first tier of access may allow the user to merely experience the resource without having any rights to modify or edit the environment within the metaverse. In another example, a second tier of access may allow the user to experience the resource and allow temporary modifications to the resource in the metaverse that is capable of being experienced by other users simultaneously accessing the resource. In yet another example, a third tier of access may allow the user to experience the resource and allow permanent modifications to the resource in a limited capacity. In still other examples, a fourth tier of access may allow the user to use the resource to build their own virtual environment. 
     Next, as shown in block  208 , the process flow includes determining, using a valuation engine, a value associated with access to the resource based on at least the one or more licensing rules. In some embodiments, each tier of access may be associated with a particular value. The value associated with access to the resource may be affected by a number of factors such as, proximity to other high value or popular metaverse areas, number of users accessing the resource, number of interactive actions provided by the resource to users, types of activities provided by the resource, number of well-known public figures or celebrities that own, may have previously owned, rented, or accessed a certain area within or immediately around the resource, and/or the like. Each factor may provide a specific value to the resource based on its applicability to resource access. In some embodiments, the system may be configured to use the valuation engine to assign weights to each applicable resource when determining the value associated with access to the resource. Based on the specific value of the source and the assigned weight, the system may be configured to use the valuation engine to determine the value associated with the access to the resource (in each tier) using a weight average (or equivalent function) using the weights assigned and value provided by each factor to a specific tier of access. 
     Next, as shown in block  210 , the process flow includes transmitting control signals configured to cause the one or more licensing rules and the value associated with the access to the resource to be displayed on the second user input device. Next, as shown in block  212 , the process flow includes electronically receiving, from the second user input device, an indication acknowledging the one or more licensing rules and a digital transfer of an amount of funds corresponding to the value associated with the access to the resource. In some embodiments, the second user and the first user may execute the digital transfer of the amount of funds corresponding to the value associated with the access to the resource using any mutually acceptable and applicable electronic funds transfers, such as, direct deposit, direct debit, use of payment instruments, electronic bill payment, instant payment, payments by phone, and/or the like. In some embodiments, the second user and the first user may execute the digital transfer of the amount of funds corresponding to the value associated with the access within the metaverse using any of the above mentioned electronic funds transfers. 
     Next, as shown in block  214 , the process flow includes authorizing the second user input device to access the resource in the metaverse. In some embodiments, the system may be configured to authorize the second user input device to access the resource in the metaverse in response to determining that the second user has transferred an amount of funds corresponding to the value associated with the access to the resource. 
     In some embodiments, the system may be configured to maintain a record to each user input device that has accessed the resource in the metaverse. To this end, the system may be configured to electronically link the resource with each user input device that has accessed the resource. This may be achieved by generating an updated NFT for the resource and storing a unique device identifier for the second user input device in one of the many metadata layers of the updated NFT. The unique device identifier may be a unique combination of a sequence of strings, characters, and numerals that may be used to identify and/or refer to the second user input device such as hash values, hash codes, digests, and/or the like. In some embodiments, the value of the resource may be influenced each time a user (e.g., second user) accesses the resource. Therefore, each time a user accesses the resource, in addition to linking the resource with the user input device, the system may be configured to determine, using the valuation engine, an updated value of the resource. This updated value may then be stored in one of the many metadata layers of the updated NFT. 
     In some embodiments, the system may be configured to generate, using the NFT generator, an updated NFT for the resource. Having generated the updated NFT, the system may be configured to generate, using the NFT generator, a first metadata layer and a second metadata layer for the updated NFT. In the first metadata layer, the system may be configured to store the unique device identifier associated with the second user input device, thus linking the resource with the second user input device. In the second metadata layer, the system may be configured to store the updated value of the resource. 
     Having generated the updated NFT, the system may then be configured to record the updated NFT on the distributed ledger. In this regard, the system may be configured to generate a new transaction object (e.g., block) for the updated NFT. Each transaction object may include the NFT (e.g., updated NFT) for the resource, a nonce - a randomly generated 32-bit whole number when the transaction object is created, and a hash value wedded to that nonce. Once generated, the updated NFT for the resource is considered signed and forever tied to its nonce and hash. Then, the system may be configured to deploy the new transaction object for the updated NFT on the distributed ledger. In some embodiments, when new transaction object is deployed on the distributed ledger, a distributed ledger address is generated for that new transaction object, i.e., an indication of where it is located on the distributed ledger. This distributed ledger address is captured for recording purposes. In response, the system may be configured to generate a notification indicating that the new transaction object has been created for the updated NFT in the distributed ledger. In response to recording the updated NFT on the distributed ledger, the system may be configured to transmit control signals configured to cause the first user input device to display the notification indicating the recording. 
     As will be appreciated by one of ordinary skill in the art in view of this disclosure, the present invention may include and/or be embodied as an apparatus (including, for example, a system, machine, device, computer program product, and/or the like), as a method (including, for example, a business method, computer-implemented process, and/or the like), or as any combination of the foregoing. Accordingly, embodiments of the present invention may take the form of an entirely business method embodiment, an entirely software embodiment (including firmware, resident software, micro-code, stored procedures in a database, or the like), an entirely hardware embodiment, or an embodiment combining business method, software, and hardware aspects that may generally be referred to herein as a “system.” Furthermore, embodiments of the present invention may take the form of a computer program product that includes a computer-readable storage medium having one or more computer-executable program code portions stored therein. As used herein, a processor, which may include one or more processors, may be “configured to” perform a certain function in a variety of ways, including, for example, by having one or more general-purpose circuits perform the function by executing one or more computer-executable program code portions embodied in a computer-readable medium, and/or by having one or more application-specific circuits perform the function. 
     It will be understood that any suitable computer-readable medium may be utilized. The computer-readable medium may include, but is not limited to, a non-transitory computer-readable medium, such as a tangible electronic, magnetic, optical, electromagnetic, infrared, and/or semiconductor system, device, and/or other apparatus. For example, in some embodiments, the non-transitory computer-readable medium includes a tangible medium such as a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a compact disc read-only memory (CD-ROM), and/or some other tangible optical and/or magnetic storage device. In other embodiments of the present invention, however, the computer-readable medium may be transitory, such as, for example, a propagation signal including computer-executable program code portions embodied therein. 
     One or more computer-executable program code portions for carrying out operations of the present invention may include object-oriented, scripted, and/or unscripted programming languages, such as, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, Objective C, JavaScript, and/or the like. In some embodiments, the one or more computer-executable program code portions for carrying out operations of embodiments of the present invention are written in conventional procedural programming languages, such as the “C” programming languages and/or similar programming languages. The computer program code may alternatively or additionally be written in one or more multi-paradigm programming languages, such as, for example, F#. 
     Some embodiments of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of apparatus and/or methods. It will be understood that each block included in the flowchart illustrations and/or block diagrams, and/or combinations of blocks included in the flowchart illustrations and/or block diagrams, may be implemented by one or more computer-executable program code portions. These one or more computer-executable program code portions may be provided to a processor of a general purpose computer, special purpose computer, and/or some other programmable data processing apparatus in order to produce a particular machine, such that the one or more computer-executable program code portions, which execute via the processor of the computer and/or other programmable data processing apparatus, create mechanisms for implementing the steps and/or functions represented by the flowchart(s) and/or block diagram block(s). 
     The one or more computer-executable program code portions may be stored in a transitory and/or non-transitory computer-readable medium (e.g. a memory) that can direct, instruct, and/or cause a computer and/or other programmable data processing apparatus to function in a particular manner, such that the computer-executable program code portions stored in the computer-readable medium produce an article of manufacture including instruction mechanisms which implement the steps and/or functions specified in the flowchart(s) and/or block diagram block(s). 
     The one or more computer-executable program code portions may also be loaded onto a computer and/or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer and/or other programmable apparatus. In some embodiments, this produces a computer-implemented process such that the one or more computer-executable program code portions which execute on the computer and/or other programmable apparatus provide operational steps to implement the steps specified in the flowchart(s) and/or the functions specified in the block diagram block(s). Alternatively, computer-implemented steps may be combined with, and/or replaced with, operator- and/or human-implemented steps in order to carry out an embodiment of the present invention. 
     Although many embodiments of the present invention have just been described above, the present invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Also, it will be understood that, where possible, any of the advantages, features, functions, devices, and/or operational aspects of any of the embodiments of the present invention described and/or contemplated herein may be included in any of the other embodiments of the present invention described and/or contemplated herein, and/or vice versa. In addition, where possible, any terms expressed in the singular form herein are meant to also include the plural form and/or vice versa, unless explicitly stated otherwise. Accordingly, the terms “a” and/or “an” shall mean “one or more,” even though the phrase “one or more” is also used herein. Like numbers refer to like elements throughout. 
     While certain exemplary embodiments have been described and shown in the accompanying drawings, it is to be understood that such embodiments are merely illustrative of and not restrictive on the broad invention, and that this invention not be limited to the specific constructions and arrangements shown and described, since various other changes, combinations, omissions, modifications and substitutions, in addition to those set forth in the above paragraphs, are possible. Those skilled in the art will appreciate that various adaptations, modifications, and combinations of the just described embodiments can be configured without departing from the scope and spirit of the invention. Therefore, it is to be understood that, within the scope of the appended claims, the invention may be practiced other than as specifically described herein.