Patent ID: 12197565

DETAILED DESCRIPTION

The concepts and technologies disclosed herein are directed to a split ledger for securing XR environments. More particularly, the concepts and technologies disclosed herein provide a novel method through which a system can, on behalf of each user in an XR environment, quickly verify each object and person in the XR environment. The system can determine what is sharing information with the outside world and with whom. In this manner, the concepts and technologies disclosed herein can ensure the XR environment is secure.

When a user enters an XR environment, the user would like to assume that the XR environment is a secure place where only the people around the user will be able to listen to what the user says. A problem is that the user does not know who the people in the XR environment actually are, since the user can only see avatars of the actual people in the XR environment. Further complicating things is determining who are the real users and where are the real users, since a person's avatar may take any form that may not look like a person. An object in the XR environment may be an object that belongs to somebody, may be a person's avatar, or may be a malicious object recording activity in the XR environment. Regardless of who is who and what objects are in the XR environment, a problem is that if the user wants to be in a secure space, they need to know who is with them, what they own in the space, and what each other's object is doing in the space.

In an effort to solve the aforementioned problems, a modified version of a split ledger can be used. In addition, the use of smart contracts can be used to define security parameters for the secure XR environment. In this use case, when a server creates a secure XR environment with nothing in it, the server creates both a passed ledger and a hash ledger. Each person can add a block to the passed ledger and share it with the other people in the XR environment. Each person's entry will have information about their identity and the IP traffic information needed to ensure that they are still themselves. Any person in the room may introduce objects into the room such as non-fungible tokens (“NFTs”) and common items that may be used to facilitate the reason for the room in the first place. Each object can have a smart contract written to the passed ledger that would describe what the object is, who owns the object, and what communications are allowed.

Each participant and potentially the server (depending on implementation) can have a full copy of the passed ledger and can share any additional blocks with other people in the room. Each person can routinely request the hash ledger from the server to verify their version of the passed ledger remains up to date. If it is out of date, they can request an update from their peers. If the peers fail to produce a valid passed ledger then the room would cease to exist and the participants would reconvene in a new room. If the security parameters of the room defined by the smart contract are violated, the room would be ended or the peers would be sent a warning and have the choice to leave.

While the subject matter described herein may be presented, at times, in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, computer-executable instructions, and/or other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, mobile devices, wireless devices, multiprocessor systems, distributed computing systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, routers, switches, other computing devices described herein, and the like.

Referring now toFIG.1, aspects of an operating environment100in which various embodiments presented herein may be implemented will be described, according to an illustrative embodiment. The illustrated operating environment100includes an XR server computer102that can provide an XR service to a plurality of user devices106A-106N (hereafter referred to collectively as “user devices106” or individually as “user device106”) associated with a plurality of users108A-108N, respectively (hereafter referred to collectively as “users108” or individually as “user108”). The XR service can be a virtual reality (“VR”) service, an augmented reality (“AR”) service, a mixed reality service, or any combination thereof. The XR service can create secure XR environments110in which the users108can interact with each other and/or with other entities (not shown) such as businesses.

The XR server computer102can execute an XR server operating system (“OS”)112and one or more application programs such as an XR server application114. The XR server OS112is a computer program for controlling the operation of the XR server computer102. The XR server application114is an executable program configured to execute on top of the XR server OS112to provide various functions described herein.

“Virtual reality” or “VR” is used herein to describe a concept that provides a computer-generated environment (also referred to herein as a “virtual environment”) that the users108can explore via the user devices106. A virtual environment can include a gathering of many individual objects that represent small parts of the overall environment. A virtual environment may be a single room, a house, a city, a world, or any other virtualization of a real-world environment. The virtual environment may be a completely imaginary environment that does not have a real-world analog. The virtual environment may be a combination of real-world and imaginary environments. A virtual object can represent any real-world object, such as furniture, individual avatars (i.e., representations of real-world users), animals (e.g., virtual pets and wildlife), vehicles, electronics, and the like. Each virtual object may belong to a virtual environment. A virtual object may be something that was created as part of the virtual environment. Alternatively, a virtual object may be something that was added at a later point by either the environment owner or another user.

A VR environment can be generated by any software framework designed for the creation and development of graphics. Some example software frameworks include, but are not limited to, UNREAL ENGINE (available from Epic Games, Inc.), UNITY (available from Unity Technologies), CRYENGINE (available from Crytek), HAVOK VISION ENGINE (available from Havok), and open source software frameworks. In some embodiments, the software frameworks utilize graphics assets, such as textures, that include or are derived from photographs of the real-world environment that is to be virtualized. Those skilled in the art will appreciate the wide range of graphical fidelity, visual styles, and other attributes a particular VR environment may have, and as such, further details in this regard are not provided herein.

“Augmented reality” or “AR” is used herein to describe a concept in which at least a portion of a physical, real-world environment is augmented to include computer-generated data. The computer-generated data can include virtual objects that are presented over and/or spatially integrated with real-world objects of the physical, real-world environment. The virtual objects can include text, colors, patterns, gradients, graphics, other images, videos, animations, combinations thereof, and the like. Computer-generated data that augments in some manner a view of a physical, real-world environment and/or elements thereof is referred to herein generally as an “augmentation.”

The AR service can provide a live view of a physical, real-world environment. In these embodiments, the AR service may utilize a camera component (best shown inFIG.6) of the user device106to provide a live view of the physical, real-world environment to be augmented. In other embodiments, the AR service can provide a non-live view of a physical, real-world environment. In these embodiments, the non-live view can present a physical, real-world environment as a static image. Accordingly, a reality that is to be augmented need not be a present reality and can instead be a past reality, encapsulated in a photograph that is augmented at a later time such as the present, for example.

“Mixed reality” is used herein to describe a concept in which elements of VR and elements of AR are used together. The term “XR” is used herein to refer to VR-only, AR-only, or mixed reality.

In the illustrated example, the XR server computer102provides the secure XR environment(s)110(hereafter referred to collectively as “secure XR environments110” or individually as “secure XR environment110”) in which one or more user avatars116(hereafter referred to collectively as “user avatars116” or individually as “user avatar116”), which are digital representations of one or more of the users108, can interact with each other and/or one or more objects118(hereafter referred to collectively as “objects118” or individually as “object118”). The objects118can include any XR object represented in the secure XR environment110. Generally, the secure XR environment110may provide a space in which the users108, via the user avatars116, can interact with each other, and possibly one or more of the objects118, through chat, interactive games, and/or other activities. In some embodiments, a meeting can be scheduled by one or more of the users108, one of whom can be the meeting organizer/leader. The meeting can include a specific date, time, duration, invitees (e.g., other users108), and other information to identify the user avatar(s)116and the object(s)118invited to the meeting.

The XR server computer102can interact with a logging system120via one or more networks121(best shown inFIG.5). The logging system120can, on behalf of each of the users108in the secure XR environment110, verify each object118and user avatar116in the secure XR environment110. The logging system120can determine what is sharing information with the outside world and with whom. In this manner, the XR server computer102and the logging system120can together ensure that the secure XR environment110is and remains secure. Although the XR server computer102and the logging system120are shown as separate systems, the functionality of the logging system120can be provided by the XR server computer102. As such, the XR server computer102and the logging system120can be combined. Alternatively, the XR server computer102and the logging system120can operate independently, such as shown in the illustrated embodiment.

The illustrated logging system120utilizes a split ledger122. When the XR server computer102creates a new secure XR environment110, such as to facilitate a meeting among two or more of the users108, the XR server computer102instructs the logging system120to create the split ledger122for that secure XR environment110. The split ledger122includes a hash ledger124and a passed ledger126. A copy of the passed ledger126′ can be stored on the user devices106and the XR server computer102such as in the illustrated example.

The passed ledger126can contain user-created blocks128created by each of the users108who plan to enter, via respective user avatars116, into the secure XR environment110. Each of the user-created blocks128can include a user ID130and IP data132. The user IDs130can uniquely identify the users108. The user IDs130can be a user name, a real name, or any combination of numbers, letters, and/or symbols. The IP data132can include an IP address of the user device106, a geographic location associated with the IP address, other IP data, or a combination thereof. The user-created blocks128can be shared with the other users108via the passed ledger126.

The passed ledger126also can include object blocks134. Any user108can introduce one or more of the objects118into the secure XR environment110. The objects118can be governed by smart contracts136in the object blocks134. The smart contracts136can be used to define security parameters for the secure XR environment110. The smart contracts136can describe what the object118is, who owns the object118, and what data communications the object118is allowed. In some embodiments, the objects118can be non-fungible tokens (“NFTs”). The objects118can be other, common items that may be used to facilitate the reason the secure XR environment110was created. For example, the objects118may be virtual furniture used to conduct a meeting within the secure XR environment110.

Each user108can routinely request the hash ledger124from the logging system120to verify that their version of the passed ledger126′ remains up to date. If the passed ledger126′ is out of date, the user108can request an update from their peers (i.e., other users108). If the peers fail to produce a valid passed ledger126, then the secure XR environment110can be shut down and the participants can reconvene in a new secure XR environment110. If the security parameters of the secure XR environment110defined by the smart contract136are violated, the secure XR environment110can be shut down or the peers can be sent a warning and have the choice to stay or leave.

The illustrated user devices106can be or can include one or more mobile telephones, smartphones, tablet computers, slate computers, smart watches, fitness devices, smart glasses (e.g., the GOOGLE GLASS family of products), a dedicated AR device, a dedicated VR device, a dedicated mixed reality device, a wearable device, mobile media playback devices, laptop computers, notebook computers, ultrabook computers, netbook computers, computers of other form factors, computing devices of other form factors, other computing systems, other computing devices, and/or the like. It should be understood that the functionality of the user devices106can be provided by a single device, by two or more similar devices, and/or by two or more dissimilar devices. For purposes of describing the concepts and technologies disclosed herein, the user devices106are described herein as a smartphone. It should be understood that this embodiment is illustrative, and should not be construed as being limiting in any way.

In the illustrated example, a first user device106A includes a device OS138, an XR app140, and an XR component142. The other user devices106B-106N can be configured the same as or similar to the first user device106A. It should be understood, however, that the user devices106can include other components. Illustrative example architectures of the user devices106are described in greater detail herein with reference toFIGS.4and6.

The device OS138can control the operation of the user device106. In some embodiments, the device OS138includes the functionality of the XR app140. The device OS138can be executed by one or more processors (best shown inFIGS.4and6) to cause the user device106to perform various operations. The device OS138can include a member of the IOS family of operating systems from APPLE INC., a member of the ANDROID OS family of operating systems from GOOGLE INC., and/or other operating systems. These operating systems are merely illustrative of some contemplated operating systems that may be used in accordance with various embodiments of the concepts and technologies described herein and therefore should not be construed as being limiting in any way.

The XR app140can execute on top of the device OS138. The XR app140can be executed by one or more processors (best shown inFIGS.4and6) to cause the user device106to perform various operations described herein. The XR app140can be a client-side application that communicates, via the network(s)121, with the XR server application114executing on the XR server computer102to provide, at least in part, an XR service to the user108of the user device106. The XR app140can be a client-side application that communicates, via the network(s)121, with the XR server application114executing on the XR server computer102to provide, at least in part, an XR service to the user108of the user device106. The XR app140, in some embodiments, can utilize the XR component142to provide, at least in part, an XR service to the user108of the user device106. The illustrated embodiment of the XR component142represents the XR component142as an internal component of the user device106. It should be understood that the XR component142alternatively may be an external component that is in communication with the user device106via a wired or wireless connection.

The XR component142, in some embodiments, is or includes a camera (e.g., a still camera and/or video camera), a sensor (e.g., an accelerometer, a global positioning system sensor, a solid state compass, or the like), a display (e.g., an integrated display, a head-mounted display, an eyeglasses display, a head-up display, an external monitor, a projection system, or a holographic display), an input device, or the like. The XR component142, in other embodiments, is or includes a display (e.g., an integrated display, a head-mounted display, an eyeglasses display, a head-up display, an external monitor, a projection system, or a holographic display), an input device, a combination thereof, or the like. In some embodiments, the XR component142is META QUEST (available from META), PLAYSTATION VR (available from SONY), HTC VIVE (available from HTC and VALVE), MICROSOFT HOLOLENS (available from MICROSOFT), or the like. The XR app140can provide an interface, using the XR component142, through which the user108can interact with the secure XR environment110provided, at least in part, by the XR server computer102.

Turning now toFIG.2A, a block diagram illustrating the passed ledger126and the hash ledger124during an XR environment110creation process will be described, according to an illustrative embodiment. When the XR server computer102creates a new secure XR environment110(e.g., an empty virtual meeting room), the passed ledger126can be populated with an environment ID200(e.g., “secure_room_123”), meeting information202(e.g., meeting start time, meeting end time, meeting invitees, meeting objects, and/or the like), owner name204(e.g., the user108that owns the secure_room_123), and an owner ID206that uniquely identifies the owner. The hash ledger124contains “hash_0”208that is calculated based on the data including the block(s) (e.g., the user-created block(s)128and/or the object block(s)134) that contain(s) the environment ID200, the meeting information202, the owner name204, and the owner ID206. A hash is a forward-only function that can be used to quickly verify that the contents have not been changed. The specific function for calculating the hash can be chosen based upon the needs of a given implementation. By way of example, and not limitation, the hash function can be SHA-256, SHA-512, sorting hash function, MD-5, or the like.

Turning now toFIG.2B, a block diagram illustrating the passed ledger126and the hash ledger124during a registration process will be described, according to an illustrative embodiment. The passed ledger126includes the environment ID200and the meeting information202that forms, in part, the room hash208(shown as “hash_0”). The passed ledger126also includes a first user-created block128A associated with a first user108A and a second user-created block128B associated with a second user108B. Each of the user-created blocks128A,128B includes a user_name210A,210B (e.g., a user ID130), an employer_name212A,212B (if applicable), an avatar_nft_hash214A,214B (e.g., a user avatar116as an NFT), and an IP_geo_location216A,216B. In the illustrated example, the hash ledger124contains a hash_1224of the first user-created block128A and a hash_2226of the second user-created block128B. The passed ledger126can include any number of user-created blocks128. The hash ledger124can include a number of hashes equal to the number of blocks in the passed ledger126.

The passed ledger126also includes an object block134associated with an object118. The object block134includes an object_name218, an nft_hash220, and an owner_ID222. In the illustrated example, the hash ledger124contains a hash_3228of the object block134. The passed ledger126can include any number of object blocks134. The hash ledger124can include any number hashes associated with the object blocks134.

Turning now toFIG.2C, a block diagram illustrating the passed ledger126and the hash ledger124during a user/object joining process will be described, according to an illustrative embodiment. The hash ledger124is not aware of the contents of the passed ledger126. Each user device106, having a full copy of the passed ledger126′ can calculate a hash of each block and can compare those hashes to the hashes recorded in the hash ledger124. The mechanism for a block to be written to the passed ledger126may depend on the use case, but regardless, a block that has been accepted (i.e., accepted by the creator, by an AI, by the room and its governing smart contract136, etc.) will submit the hash to the hash ledger124. The hash ledger124has a permission set to allow a specific user or super user (e.g., a host of a meeting in the secure XR environment110) to write to the hash ledger124. Other interactions include user requests for a specific block hash and the hash ledger124provides it. It is up to the user108then to verify that the passed ledger126stored on their respective device106is correct.

In the illustrated example, the passed ledger126includes a third user-created block128C and a seventh user-created block128G. A third user device106C associated with the third user108C can calculate a hash_3228and request the hash_3228from the hash ledger124via a hash request230directed to the hash ledger124. The hash ledger124, in turn, can respond with a hash response232including the hash_3228stored in the hash ledger124. In the illustrated example, the hash_3228received in the hash response232from the hash ledger124matches the hash_3228stored in the passed ledger126.

A seventh user device106G associated with a seventh user108G can calculate a hash_7234and request the hash_7234from the hash ledger124via another hash request230. The hash ledger124, in turn, can respond with another hash response232. In the illustrated example, the hash ledger124does not include the hash_7234.

When a user108is in a room (e.g., the secure XR environment110), the user108can quickly determine the number of unique elements in the room. Each item, be it an avatar, a device, or furniture, will be recorded in a block. Each block will set out what is allowed for that element. If someone tries to add an item, then it would only appear if it is in the passed ledger126. If the users108do not see the passed ledger126agreeing with the hash ledger124(such as in the example above with the hash_7234), then the users108can either work to fix the ledgers or leave the room. If an element's block is altered to allow it more freedom, then the hash of the block would change, again setting it at odds with the hash ledger124. The hash ledger124is not aware of what the blocks contain, only the correct hash of those contents.

Turning now toFIG.3, aspects of a method300for providing a split ledger122for securing XR environments110will be described, according to an illustrative embodiment. It should be understood that the operations of the methods disclosed herein are not necessarily presented in any particular order and that performance of some or all of the operations in an alternative order(s) is possible and is contemplated. The operations have been presented in the demonstrated order for ease of description and illustration. Operations may be added, omitted, and/or performed simultaneously, without departing from the scope of the concepts and technologies disclosed herein.

It also should be understood that the method disclosed herein can be ended at any time and need not be performed in their respective entireties. Some or all operations of the method, and/or substantially equivalent operations, can be performed by execution of computer-readable instructions included on a computer storage media, as defined herein. The term “computer-readable instructions,” and variants thereof, as used herein, is used expansively to include routines, applications, application modules, program modules, programs, components, data structures, algorithms, and the like. Computer-readable instructions can be implemented on various system configurations including the XR server computer102, the user device106, the logging system120, single-processor or multiprocessor systems, minicomputers, mainframe computers, personal computers, hand-held computing devices, microprocessor-based, programmable consumer electronics, combinations thereof, and the like.

Thus, it should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states, operations, structural devices, acts, or modules. These states, operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. As used herein, the phrase “cause a processor to perform operations” and variants thereof refers to causing a processor of a computing system or device, such as the XR server computer102, the user device106, or the logging system120, to perform one or more operations and/or causing the processor to direct other components of the computing system or device to perform one or more of the operations.

For purposes of illustrating and describing some of the concepts of the present disclosure, the methods disclosed herein are described as being performed, at least in part, by the XR server computer102, the user device106, the logging system120, or some combination thereof, via execution of one or more software modules and/or software applications. It should be understood that additional and/or alternative devices and/or network nodes can provide the functionality described herein via execution of one or more modules, applications, and/or other software. Thus, the illustrated embodiments are illustrative, and should not be viewed as being limiting in any way.

The method300begins and proceeds to operation302. At operation302, the XR server computer102creates an empty XR environment, such as the secure XR environment110, without any user avatars116and/or objects118. As part of this creation process, the passed ledger126can be populated with room information (best shown inFIG.2A). A hash of this information (shown as “hash_0208”) can be created and stored in the hash ledger124.

From operation302, the method300proceeds to operation304. At operation304, the XR server computer102registers the users108and the objects118(if applicable) for a meeting within the secure XR environment110. As part of this registration process, the passed ledger126can be populated with the user-created blocks128for each of the users108and the object blocks134for each of the objects118(best shown inFIG.2B). A hash of this information can be created and stored in the hash ledger124. For example, the hash_1224for the first user-created block128A, the hash_2226for the second user-created block128B, and the hash_3228for the object block134.

From304, the method300proceeds to operation306. At operation306, the users108and/or objects118, registered at operation304, join the secure XR environment110. The method300assumes that all users108and objects118joining the secure XR environment110are legit—that is, have the correct hash. If, however, a particular user108or object118does not have the correct hash, then the users108can either work to fix the ledgers or leave the secure XR environment110. From operation306, the method300proceeds to operation308. At operation308, the XR server computer102monitors data traffic incoming into the secure XR environment110and data traffic outgoing from the secure XR environment110. From operation308, the method300proceeds to operation310. At operation310, the XR server computer102determines whether the data traffic is in violation. In some embodiments, the type and amount of data traffic incoming into the secure XR environment and the type and amount of data traffic outgoing from the secure XR environment can be defined in one or more smart contracts136. If so, the method proceeds to operation312. At operation312, the XR server computer102evicts the offending user108and/or object118from the secure XR environment110. From operation312, the method300proceeds to operation314. If, however, the XR server computer102determines that the data traffic is not in violation, the method300proceeds directly to operation314.

At operation314, the XR server computer102determines whether the meeting should be ended. For example, the meeting, and therefore the use of the secure XR environment110, may be ended based on a specified end time. Alternatively, one or more of the users108may suggest that the meeting be ended, in which case the other users may vote to end the meeting. A meeting leader (e.g., a meeting creator or elected leader) may end the meeting without a vote. If the XR server computer102determines, at operation314, that the meeting should be ended, the method300proceeds to operation316. The method300can end at operation316. If, however, the XR server computer102determines, at operation314, that the meeting should continue, the method300returns to operation308, and the method300proceeds as described above.

FIG.4is a block diagram illustrating a computer system400configured to provide the functionality in accordance with various embodiments of the concepts and technologies disclosed herein. In some implementations, the untrusted XR server computer102, the XR server computer102, the user device106, and/or the logging system120utilize an architecture that is the same as or similar to the architecture of the computer system400. It should be understood, however, that modification to the architecture may be made to facilitate certain interactions among elements described herein.

The computer system400includes a processing unit402, a memory404, one or more user interface devices406, one or more input/output (“I/O”) devices408, and one or more network devices410, each of which is operatively connected to a system bus412. The bus412enables bi-directional communication between the processing unit402, the memory404, the user interface devices406, the I/O devices408, and the network devices410.

The processing unit402may be a standard central processor that performs arithmetic and logical operations, a more specific purpose programmable logic controller (“PLC”), a programmable gate array, a system-on-a-chip, or other type of processor known to those skilled in the art and suitable for controlling the operation of the server computer. Processing units are generally known, and therefore are not described in further detail herein.

The memory404communicates with the processing unit402via the system bus412. In some embodiments, the memory404is operatively connected to a memory controller (not shown) that enables communication with the processing unit402via the system bus412. The memory404includes an operating system414and one or more program modules416. The operating system414can include, but is not limited to, members of the WINDOWS, WINDOWS CE, and/or WINDOWS MOBILE families of operating systems from MICROSOFT CORPORATION, the LINUX family of operating systems, the MAC OSX and/or iOS families of operating systems from APPLE CORPORATION, other operating systems, and the like. The operating system414can be the XR server OS112or the device OS138as illustrated and described with reference toFIG.1.

The program modules416may include various software and/or program modules to perform the various operations described herein. The program modules416for the computer system400embodied as the XR server computer102can include the XR server application114. The program modules416for the computer system400embodied as the user device106can include the XR app140. The program modules416and/or other programs can be embodied in computer-readable media containing instructions that, when executed by the processing unit402, perform one or more operations, such as the operations described herein above with reference to the method300illustrated inFIG.3. According to embodiments, the program modules416may be embodied in hardware, software, firmware, or any combination thereof.

By way of example, and not limitation, computer-readable media may include any available computer storage media or communication media that can be accessed by the computer system400. Communication media includes computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics changed or set in a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.

Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, Erasable Programmable ROM (“EPROM”), Electrically Erasable Programmable ROM (“EEPROM”), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer system400. In the claims, the phrase “computer storage medium,” “computer-readable storage medium,” and variations thereof does not include waves or signals per se and/or communication media, and therefore should be construed as being directed to “non-transitory” media only.

The user interface devices406may include one or more devices with which a user accesses the computer system400. The user interface devices406may include, but are not limited to, computers, servers, personal digital assistants, cellular phones, or any suitable computing devices. The I/O devices408enable a user to interface with the program modules416. In one embodiment, the I/O devices408are operatively connected to an I/O controller (not shown) that enables communication with the processing unit402via the system bus412. The I/O devices408may include one or more input devices, such as, but not limited to, a keyboard, a mouse, or an electronic stylus. Further, the I/O devices408may include one or more output devices, such as, but not limited to, a display screen or a printer.

The network devices410enable the computer system400to communicate with other networks or remote systems via a network418, such as the network(s)121/500(best shown inFIGS.1and4). Examples of the network devices410include, but are not limited to, a modem, a radio frequency (“RF”) or infrared (“IR”) transceiver, a telephonic interface, a bridge, a router, or a network card. The network418may include a wireless network such as, but not limited to, a wireless local area network (“WLAN”), a wireless wide area network (“WWAN”), a wireless personal area network (“WPAN”) such as provided via BLUETOOTH technology, a wireless metropolitan area network (“WMAN”) such as a WiMAX network or metropolitan cellular network. Alternatively, the network418may be a wired network such as, but not limited to, a wide area network (“WAN”), a wired LAN such as provided via Ethernet, a wired personal area network n (“PAN”), or a wired metropolitan area network (“MAN”).

Turning now toFIG.5, additional details of a network500, such as the network(s)121/418, are illustrated, according to an illustrative embodiment. The network500includes a cellular network502, a packet data network504, for example, the Internet, and a circuit switched network506, for example, a publicly switched telephone network (“PSTN”). The cellular network502includes various components such as, but not limited to, base transceiver stations (“BTSs”), Node-B's or e-Node-B's, base station controllers (“BSCs”), radio network controllers (“RNCs”), mobile switching centers (“MSCs”), mobile management entities (“MMEs”), short message service centers (“SMSCs”), multimedia messaging service centers (“MMSCs”), home location registers (“HLRs”), home subscriber servers (“HSSs”), visitor location registers (“VLRs”), charging platforms, billing platforms, voicemail platforms, GPRS core network components, location service nodes, an IP Multimedia Subsystem (“IMS”), and the like. The cellular network502also includes radios and nodes for receiving and transmitting voice, data, and combinations thereof to and from radio transceivers, networks, the packet data network504, and the circuit switched network506.

A mobile communications device508, such as, for example, the user device106, a cellular telephone, a user equipment, a mobile terminal, a PDA, a laptop computer, a handheld computer, and combinations thereof, can be operatively connected to the cellular network502. The cellular network502can be configured as a 2G Global System for Mobile communications (“GSM”) network and can provide data communications via General Packet Radio Service (“GPRS”) and/or Enhanced Data rates for GSM Evolution (“EDGE”). Additionally, or alternatively, the cellular network502can be configured as a 3G Universal Mobile Telecommunications System (“UMTS”) network and can provide data communications via the High-Speed Packet Access (“HSPA”) protocol family, for example, High-Speed Downlink Packet Access (“HSDPA”), Enhanced UpLink (“EUL”) (also referred to as High-Speed Uplink Packet Access (“HSUPA”)), and HSPA+. The cellular network502also is compatible with 4G mobile communications standards such as Long-Term Evolution (“LTE”), or the like, as well as evolved and future mobile standards.

The packet data network504includes various devices, for example, servers, computers, databases, and other devices in communication with one another, as is generally known. The packet data network504devices are accessible via one or more network links. The servers often store various files that are provided to a requesting device such as, for example, a computer, a terminal, a smartphone, or the like. Typically, the requesting device includes software (a “browser”) for executing a web page in a format readable by the browser or other software. Other files and/or data may be accessible via “links” in the retrieved files, as is generally known. In some embodiments, the packet data network504includes or is in communication with the Internet. The circuit switched network506includes various hardware and software for providing circuit switched communications. The circuit switched network506may include, or may be, what is often referred to as a plain old telephone system (“POTS”). The functionality of a circuit switched network506or other circuit-switched network are generally known and will not be described herein in detail.

The illustrated cellular network502is shown in communication with the packet data network504and a circuit switched network506, though it should be appreciated that this is not necessarily the case. One or more Internet-capable devices510, for example, the user device106, a PC, a laptop, a portable device, or another suitable device, can communicate with one or more cellular networks502, and devices connected thereto, through the packet data network504. It also should be appreciated that the Internet-capable device510can communicate with the packet data network504through the circuit switched network506, the cellular network502, and/or via other networks (not illustrated).

As illustrated, a communications device512, for example, a telephone, facsimile machine, modem, computer, or the like, can be in communication with the circuit switched network506, and therethrough to the packet data network504and/or the cellular network502. It should be appreciated that the communications device512can be an Internet-capable device, and can be substantially similar to the Internet-capable device510. In the specification, the network500is used to refer broadly to any combination of the networks502,504,506. It should be appreciated that substantially all of the functionality described with reference to the network500can be performed by the cellular network502, the packet data network504, and/or the circuit switched network506, alone or in combination with other networks, network elements, and the like.

Turning now toFIG.6, an illustrative mobile device600and components thereof will be described. In some embodiments, the user device106described above with reference toFIG.1can be configured as and/or can have an architecture similar or identical to the mobile device600described herein inFIG.6. It should be understood, however, that the user device106may or may not include the functionality described herein with reference toFIG.6. While connections are not shown between the various components illustrated inFIG.6, it should be understood that some, none, or all of the components illustrated inFIG.6can be configured to interact with one other to carry out various device functions. In some embodiments, the components are arranged so as to communicate via one or more busses (not shown). Thus, it should be understood thatFIG.6and the following description are intended to provide a general understanding of a suitable environment in which various aspects of embodiments can be implemented, and should not be construed as being limiting in any way.

As illustrated inFIG.6, the mobile device600can include a display602for displaying data. According to various embodiments, the display602can be configured to display various graphical user interface (“GUI”) elements, text, images, video, advertisements, prompts, virtual keypads and/or keyboards, messaging data, notification messages, metadata, internet content, device status, time, date, calendar data, device preferences, map and location data, combinations thereof, and the like. The mobile device600also can include a processor604and a memory or other data storage device (“memory”)606. The processor604can be configured to process data and/or can execute computer-executable instructions stored in the memory606. The computer-executable instructions executed by the processor604can include, for example, an operating system608(e.g., the device OS138), one or more applications610(e.g., the XR app140), other computer-executable instructions stored in a memory606, or the like. In some embodiments, the applications610also can include a UI application (not illustrated inFIG.6).

The UI application can interface with the operating system608to facilitate user interaction with functionality and/or data stored at the mobile device600and/or stored elsewhere. In some embodiments, the operating system608can include a member of the IOS family of operating systems from APPLE INC., a member of the ANDROID OS family of operating systems from GOOGLE INC., and/or other operating systems. These operating systems are merely illustrative of some contemplated operating systems that may be used in accordance with various embodiments of the concepts and technologies described herein and therefore should not be construed as being limiting in any way.

The UI application can be executed by the processor604to aid a user in entering content, viewing account information, answering/initiating calls, entering/deleting data, entering and setting user IDs and passwords for device access, configuring settings, manipulating address book content and/or settings, multimode interaction, interacting with other applications610, and otherwise facilitating user interaction with the operating system608, the applications610, and/or other types or instances of data612that can be stored at the mobile device600.

According to various embodiments, the applications610can include, for example, presence applications, visual voice mail applications, messaging applications, text-to-speech and speech-to-text applications, add-ons, plug-ins, email applications, music applications, video applications, camera applications, location-based service applications, power conservation applications, game applications, productivity applications, entertainment applications, enterprise applications, combinations thereof, and the like. The applications610, the data612, and/or portions thereof can be stored in the memory606and/or in a firmware614, and can be executed by the processor604. The firmware614also can store code for execution during device power up and power down operations. It can be appreciated that the firmware614can be stored in a volatile or non-volatile data storage device including, but not limited to, the memory606and/or a portion thereof.

The mobile device600also can include an input/output (“I/O”) interface616. The I/O interface616can be configured to support the input/output of data such as location information, user information, organization information, presence status information, user IDs, passwords, and application initiation (start-up) requests. In some embodiments, the I/O interface616can include a hardwire connection such as USB port, a mini-USB port, a micro-USB port, an audio jack, a PS2 port, an IEEE 1394 (“FIREWIRE”) port, a serial port, a parallel port, an Ethernet (RJ46) port, an RJ11 port, a proprietary port, combinations thereof, or the like. In some embodiments, the mobile device600can be configured to synchronize with another device to transfer content to and/or from the mobile device600. In some embodiments, the mobile device600can be configured to receive updates to one or more of the applications610via the I/O interface616, though this is not necessarily the case. In some embodiments, the I/O interface616accepts I/O devices such as keyboards, keypads, mice, interface tethers, printers, plotters, external storage, touch/multi-touch screens, touch pads, trackballs, joysticks, microphones, remote control devices, displays, projectors, medical equipment (e.g., stethoscopes, heart monitors, and other health metric monitors), modems, routers, external power sources, docking stations, the XR component142, combinations thereof, and the like. It should be appreciated that the I/O interface616may be used for communications between the mobile device600and a network device or local device.

The mobile device600also can include a communications component616. The communications component618can be configured to interface with the processor604to facilitate wired and/or wireless communications with one or more networks described above herein. In some embodiments, other networks include networks that utilize non-cellular wireless technologies such as WI-FI or WIMAX. In some embodiments, the communications component618includes a multimode communications subsystem for facilitating communications via the cellular network and one or more other networks.

The communications component618, in some embodiments, includes one or more transceivers. The one or more transceivers, if included, can be configured to communicate over the same and/or different wireless technology standards with respect to one another. For example, in some embodiments one or more of the transceivers of the communications component618may be configured to communicate using GSM, CDMA, CDMAONE, CDMA2000, LTE, and various other 2G, 2.5G, 3G, 4G, 5G, and greater generation technology standards. Moreover, the communications component618may facilitate communications over various channel access methods (which may or may not be used by the aforementioned standards) including, but not limited to, TDMA, FDMA, W-CDMA, OFDM, SDMA, and the like.

In addition, the communications component618may facilitate data communications using GPRS, EDGE, the HSPA protocol family, including HSDPA, EUL, or otherwise termed HSUPA, HSPA+, and various other current and future wireless data access standards. In the illustrated embodiment, the communications component618can include a first transceiver (“TxRx”)620A that can operate in a first communications mode (e.g., GSM). The communications component618also can include an Nthtransceiver (“TxRx”)620N that can operate in a second communications mode relative to the first transceiver620A (e.g., UMTS). While two transceivers620A-620N (hereinafter collectively and/or generically referred to as “transceivers620”) are shown inFIG.6, it should be appreciated that less than two, two, and/or more than two transceivers620can be included in the communications component618.

The communications component618also can include an alternative transceiver (“Alt TxRx”)622for supporting other types and/or standards of communications. According to various contemplated embodiments, the alternative transceiver622can communicate using various communications technologies such as, for example, WI-FI, WIMAX, BLUETOOTH, infrared, infrared data association (“IRDA”), near-field communications (“NFC”), other radio frequency (“RF”) technologies, combinations thereof, and the like.

In some embodiments, the communications component618also can facilitate reception from terrestrial radio networks, digital satellite radio networks, internet-based radio service networks, combinations thereof, and the like. The communications component618can process data from a network such as the Internet, an intranet, a broadband network, a WI-FI hotspot, an Internet service provider (“ISP”), a digital subscriber line (“DSL”) provider, a broadband provider, combinations thereof, or the like.

The mobile device600also can include one or more sensors624. The sensors624can include temperature sensors, light sensors, air quality sensors, movement sensors, orientation sensors, noise sensors, proximity sensors, or the like. As such, it should be understood that the sensors624can include, but are not limited to, accelerometers, magnetometers, gyroscopes, infrared sensors, noise sensors, microphones, combinations thereof, or the like. Additionally, audio capabilities for the mobile device600may be provided by an audio I/O component626. The audio I/O component626of the mobile device600can include one or more speakers for the output of audio signals, one or more microphones for the collection and/or input of audio signals, and/or other audio input and/or output devices.

The illustrated mobile device600also can include a subscriber identity module (“SIM”) system628. The SIM system628can include a universal SIM (“USIM”), a universal integrated circuit card (“UICC”) and/or other identity devices. The SIM system628can include and/or can be connected to or inserted into an interface such as a slot interface630. In some embodiments, the slot interface630can be configured to accept insertion of other identity cards or modules for accessing various types of networks. Additionally, or alternatively, the slot interface630can be configured to accept multiple subscriber identity cards. Because other devices and/or modules for identifying users and/or the mobile device600are contemplated, it should be understood that these embodiments are illustrative, and should not be construed as being limiting in any way.

The mobile device600also can include an image capture and processing system632(“image system”). The image system632can be configured to capture or otherwise obtain photos, videos, and/or other visual information. As such, the image system632can include cameras, lenses, charge-coupled devices (“CCDs”), combinations thereof, or the like. The mobile device600may also include a video system634. The video system634can be configured to capture, process, record, modify, and/or store video content. Photos and videos obtained using the image system632and the video system634, respectively, may be added as message content to a multimedia message service (“MIMS”) message, email message, and sent to another mobile device. The video and/or photo content also can be shared with other devices via various types of data transfers via wired and/or wireless communication devices as described herein.

The mobile device600also can include one or more location components636. The location components636can be configured to send and/or receive signals to determine a geographic location of the mobile device600. According to various embodiments, the location components636can send and/or receive signals from GPS devices, A-GPS devices, WI-FI/WIMAX and/or cellular network triangulation data, combinations thereof, and the like. The location component636also can be configured to communicate with the communications component618to retrieve triangulation data for determining a location of the mobile device600. In some embodiments, the location component636can interface with cellular network nodes, telephone lines, satellites, location transmitters and/or beacons, wireless network transmitters and receivers, combinations thereof, and the like. In some embodiments, the location component636can include and/or can communicate with one or more of the sensors624such as a compass, an accelerometer, and/or a gyroscope to determine the orientation of the mobile device600. Using the location component636, the mobile device600can generate and/or receive data to identify its geographic location, or to transmit data used by other devices to determine the location of the mobile device600. The location component636may include multiple components for determining the location and/or orientation of the mobile device600.

The illustrated mobile device600also can include a power source638. The power source638can include one or more batteries, power supplies, power cells, and/or other power subsystems including alternating current (“AC”) and/or direct current (“DC”) power devices. The power source638also can interface with an external power system or charging equipment via a power I/O component640. Because the mobile device600can include additional and/or alternative components, the above embodiment should be understood as being illustrative of one possible operating environment for various embodiments of the concepts and technologies described herein. The described embodiment of the mobile device600is illustrative, and should not be construed as being limiting in any way.

As used herein, communication media includes computer-executable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics changed or set in a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, UV, and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.

By way of example, and not limitation, computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-executable instructions, data structures, program modules, or other data. For example, computer media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the mobile device600or other devices or computers described herein, such as the computer system400described above with reference toFIG.4. In the claims, the phrase “computer storage medium,” “computer-readable storage medium,” and variations thereof does not include waves or signals per se and/or communication media, and therefore should be construed as being directed to “non-transitory” media only.

Encoding the software modules presented herein also may transform the physical structure of the computer-readable media presented herein. The specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to, the technology used to implement the computer-readable media, whether the computer-readable media is characterized as primary or secondary storage, and the like. For example, if the computer-readable media is implemented as semiconductor-based memory, the software disclosed herein may be encoded on the computer-readable media by transforming the physical state of the semiconductor memory. For example, the software may transform the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory. The software also may transform the physical state of such components in order to store data thereupon.

As another example, the computer-readable media disclosed herein may be implemented using magnetic or optical technology. In such implementations, the software presented herein may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations also may include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.

In light of the above, it should be appreciated that many types of physical transformations may take place in the mobile device600in order to store and execute the software components presented herein. It is also contemplated that the mobile device600may not include all of the components shown inFIG.6, may include other components that are not explicitly shown inFIG.6, or may utilize an architecture completely different than that shown inFIG.6.

Turning now toFIG.7, a block diagram illustrating an example virtualized cloud architecture700and components thereof will be described, according to an exemplary embodiment. In some embodiments, the virtualized cloud architecture700can be utilized to implement, at least in part, the XR server computer102, the logging system120, aspects of the network(s)121/500, portions thereof, and/or combinations thereof. The virtualized cloud architecture700is a shared infrastructure that can support multiple services and network applications. The illustrated virtualized cloud architecture700includes a hardware resource layer702, a control layer704, a virtual resource layer706, and an application layer708that work together to perform operations as will be described in detail herein.

The hardware resource layer702provides hardware resources, which, in the illustrated embodiment, include one or more compute resources710, one or more memory resources712, and one or more other resources714. The compute resource(s)710can include one or more hardware components that perform computations to process data, and/or to execute computer-executable instructions of one or more application programs, operating systems, and/or other software. The compute resources710can include one or more central processing units (“CPUs”) configured with one or more processing cores. The compute resources710can include one or more graphics processing unit (“GPU”) configured to accelerate operations performed by one or more CPUs, and/or to perform computations to process data, and/or to execute computer-executable instructions of one or more application programs, operating systems, and/or other software that may or may not include instructions particular to graphics computations. In some embodiments, the compute resources710can include one or more discrete GPUs. In some other embodiments, the compute resources710can include CPU and GPU components that are configured in accordance with a co-processing CPU/GPU computing model, wherein the sequential part of an application executes on the CPU and the computationally-intensive part is accelerated by the GPU. The compute resources710can include one or more system-on-chip (“SoC”) components along with one or more other components, including, for example, one or more of the memory resources712, and/or one or more of the other resources714. In some embodiments, the compute resources710can be or can include one or more SNAPDRAGON SoCs, available from QUALCOMM; one or more TEGRA SoCs, available from NVIDIA; one or more HUMMINGBIRD SoCs, available from SAMSUNG; one or more Open Multimedia Application Platform (“OMAP”) SoCs, available from TEXAS INSTRUMENTS; one or more customized versions of any of the above SoCs; and/or one or more proprietary SoCs. The compute resources710can be or can include one or more hardware components architected in accordance with an advanced reduced instruction set computing (“RISC”) machine (“ARM”) architecture, available for license from ARM HOLDINGS. Alternatively, the compute resources710can be or can include one or more hardware components architected in accordance with an x86 architecture, such an architecture available from INTEL CORPORATION of Mountain View, California, and others. Those skilled in the art will appreciate the implementation of the compute resources710can utilize various computation architectures, and as such, the compute resources710should not be construed as being limited to any particular computation architecture or combination of computation architectures, including those explicitly disclosed herein.

The memory resource(s)712can include one or more hardware components that perform storage operations, including temporary or permanent storage operations. In some embodiments, the memory resource(s)712include volatile and/or non-volatile memory implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data disclosed herein.

Computer storage media includes, but is not limited to, random access memory (“RAM”), read-only memory (“ROM”), Erasable Programmable ROM (“EPROM”), Electrically Erasable Programmable ROM (“EEPROM”), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store data and which can be accessed by the compute resources710.

The other resource(s)714can include any other hardware resources that can be utilized by the compute resources(s)710and/or the memory resource(s)712to perform operations described herein. The other resource(s)714can include one or more input and/or output processors (e.g., network interface controller or wireless radio), one or more modems, one or more codec chipset, one or more pipeline processors, one or more fast Fourier transform (“FFT”) processors, one or more digital signal processors (“DSPs”), one or more speech synthesizers, and/or the like.

The hardware resources operating within the hardware resource layer702can be virtualized by one or more virtual machine monitors (“VMMs”)716A-716N (also known as “hypervisors;” hereinafter “VMMs716”) operating within the control layer704to manage one or more virtual resources that reside in the virtual resource layer706. The VMMs716can be or can include software, firmware, and/or hardware that alone or in combination with other software, firmware, and/or hardware, manages one or more virtual resources operating within the virtual resource layer706.

The virtual resources operating within the virtual resource layer706can include abstractions of at least a portion of the compute resources710, the memory resources712, the other resources714, or any combination thereof. These abstractions are referred to herein as virtual machines (“VMs”). In the illustrated embodiment, the virtual resource layer706includes VMs718A-718N (hereinafter “VMs718”). Each of the VMs718can execute one or more applications720A-720N in the application layer708. The applications720A-720N can include the XR server OS122and/or the XR server application114.

Based on the foregoing, it should be appreciated that concepts and technologies directed to split ledger for securing XR environments have been disclosed herein. Although the subject matter presented herein has been described in language specific to computer structural features, methodological and transformative acts, specific computing machinery, and computer-readable media, it is to be understood that the concepts and technologies disclosed herein are not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts and mediums are disclosed as example forms of implementing the concepts and technologies disclosed herein.

The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the embodiments of the concepts and technologies disclosed herein.