H04L67/1089

Reconciliation of data stored on permissioned database storage across independent computing nodes

Reconciliation and subscription-model permissions of data stored across independent ledger instances of a database. A system includes a resource manager coupled to a plurality of client accounts. The system includes an execution platform and a shared permissioned ledger comprising independent processing and storage nodes for executing data operations for the plurality of client accounts. The resource manager defines a settlement group comprising one or more client accounts and authenticates an observer node associated with the settlement group. The resource manager assigns ingested data an encryption level on a key hierarchy based on content of the ingested data.

NETWORK FORMATION FOR A LOAD CONTROL SYSTEM

A control device may be configured to delay an attachment procedure while attachment messages are being transmitted over the network. The control device may be configured to initiate an attachment procedure with a router device on a network at the end a back-off period of time. The attachment procedure may include transmitting attachment messages (e.g., parent request messages) that enable the control device to transmit and receive messages over the network through the router device. During the back-off period of time, the control device may determine an attachment message is received from another control device on the network. And, if an attachment message (e.g., a parent request messages and/or a link request message) is received from another control device, the control device may increase the back-off period of time (e.g., delaying when the control device initiates its attachment procedure).

Cascading payload replication

Cascading payload replication to target compute nodes is disclosed. Cascading payload replication can be accomplished using a two-stage operation for a replication operation. In the first stage, a plan is generated and distributed for the replication operation. The plan includes an assignment of compute nodes to tree nodes in a tree hierarchy. In the second phase, the payload is distributed according to the plan. The plan is different for at least two replication operations. Thus, the cascading payload replication is adaptable to changing target compute nodes and provides for load balancing.

Multi-tenant marketplace architectures

A method for managing entities in a multi-tenant marketplace architecture system is discussed. The method includes determining that a merchant is represented as a first representation in a first hierarchical data structure and as a second representation in a second hierarchical data structure, where both the first and second hierarchical data structures are managed by a first service provider. The merchant is being managed via a full representation in an original hierarchical data structure by a marketplace service provider. The first and second representations provide outbound services via the first hierarchical data structure and via the second hierarchical data structure, respectively. The method also includes linking the first representation with the second representation to configure the first and second representations for propagating results of an inbound service applied to one of the first and second representations to a remaining one of the first and second representations.

HIGH AVAILABILITY MANAGEMENT FOR A HIERARCHY OF RESOURCES IN AN SDDC
20230109219 · 2023-04-06 ·

Some embodiments provide a hierarchical data service (HDS) that manages many resource clusters that are in a resource cluster hierarchy. In some embodiments, each resource cluster has its own cluster manager, and the cluster managers are in a cluster manager hierarchy that mimics the hierarchy of the resource clusters. In some embodiments, both the resource cluster hierarchy and the cluster manager hierarchy are tree structures, e.g., a directed acyclic graph (DAG) structure that has one root node with multiple other nodes in a hierarchy, with each other node having only one parent node and one or more possible child nodes.

Executable Objects in a Distributed Storage System
20230105531 · 2023-04-06 ·

Systems, methods, and machine-readable media are disclosed for running an executable object on an object storage system. An executable object including executable code is stored on a first storage node of an object storage system. The first storage node receives a request to run the executable object. The first storage node identifies the physical location of one or more data objects of interest to be processed by the executable object. The first storage node runs the executable object to process the identified one or more data objects. The first storage node receives a request from a second storage node of the object storage system for the executable object in response to one or more data objects of interest being located at the second storage node. The first storage node sends a copy of the executable object to the second storage node.

Method and system for providing augmented reality displays

When providing augmented reality display to users in an environment, two or more electronic devices operable to analyse the environment for augmented reality display purposes that are near to each other share data and/or processing relating to the analysis of the environment for augmented reality display purposes, with each device then using the data it receives from the other device when providing an augmented reality display to a user.

TECHNIQUES FOR OPERATING A DISTRIBUTED COMMUNICATION NETWORK
20170374516 · 2017-12-28 · ·

A distributed network of communication nodes is organized in a hierarchy of clusters. Upon deployment, nodes exchange messages to form an upper layer cluster and multiple lower layer clusters. Each lower layer cluster may be in communication with one upper layer cluster node, which may function to communicate messages to/from the nodes in the lower layer cluster to the upper layer nodes. Cluster formations may be achieved by exchanging messages among member nodes. The communication between nodes during the operation of the distributed network is based on a consensus protocol such as a modified Paxos protocol, as described herein.

Network device and information sharing system

In a network system without a server, a network device and a system that can share information in all devices efficiently and surely are provided. CPUs of a plurality of devices connected to a network determine a host device based on device numbers and network strengths of each of the devices. When transmitting share information stored in a memory to the host device, the CPUs of the client devices merge share information transmitted from the other client devices with the share information stored in the memories so as to transmit the merged information to the host device. The CPU of the host device generates share information about all the devices so as to distribute the information to all the client devices. When the share information is changed, the CPU of the host device generates finite difference information with respect to previous share information so as to distribute the information to all the client devices. When the share information is successively changed, the CPU of the host device merges the respective pieces of finite difference information so as to distribute the information to the client devices.

Network formation for a load control system

A control device may be configured to delay an attachment procedure while attachment messages are being transmitted over the network. The control device may be configured to initiate an attachment procedure with a router device on a network at the end a back-off period of time. The attachment procedure may include transmitting attachment messages (e.g., parent request messages) that enable the control device to transmit and receive messages over the network through the router device. During the back-off period of time, the control device may determine an attachment message is received from another control device on the network. And, if an attachment message (e.g., a parent request messages and/or a link request message) is received from another control device, the control device may increase the back-off period of time (e.g., delaying when the control device initiates its attachment procedure).