Abstract: In various embodiments, a computer-implemented method for processing requests for media content segments in a live streaming system includes receiving, from an endpoint device, a request for a segment of media content. An expected generation time associated with the segment is used to establish a first timing threshold and a second timing threshold. If the request is received between the first and second thresholds, then a request for the segment is transmitted to a preferred pipeline among multiple pipelines, and the segment is returned if available from the preferred pipeline or an error is returned if the segment is unavailable. If the request is received after the second threshold, a request for the segment is transmitted to at least one pipeline among the multiple pipelines, and the segment is returned if available from any pipeline or an error is returned if the segment is unavailable from all pipelines.

Abstract: In various embodiments, domain name system (DNS) servers are implemented on a content distribution network (CDN) infrastructure in order to facilitate centralized control of traffic steering. Each server appliance in the CDN infrastructure acts as both an authoritative DNS nameserver and a dynamic request proxy, and each such server appliance is assigned to one of multiple cloud computing system regions. The assignment of server appliances to cloud regions is based on latency measurements collected via client application probes and an optimization that minimizes an overall latency experienced by the client applications subject to constraints that the maximum traffic to each cloud region is less than a capacity constraint for that region, the maximum deviation of traffic to each cloud regions at any point in time is less than a given percentage, and the maximum deviation of traffic between direct and indirect paths is less than a given percentage.

Abstract: A rollback protection method for preventing message equivocation in a consensus system is provided. The consensus system includes distributed computational nodes connected by a network and configured to run a TEE-based consensus protocol.

Abstract: A rollback protection method for preventing message equivocation in a consensus system is provided. The consensus system includes distributed computational nodes connected by a network and configured to run a TEE-based consensus protocol.

Abstract: In various embodiments, domain name system (DNS) servers are implemented on a content distribution network (CDN) infrastructure in order to facilitate centralized control of traffic steering. Each server appliance in the CDN infrastructure acts as both an authoritative DNS nameserver and a dynamic request proxy, and each such server appliance is assigned to one of multiple cloud computing system regions. The assignment of server appliances to cloud regions is based on latency measurements collected via client application probes and an optimization that minimizes an overall latency experienced by the client applications subject to constraints that the maximum traffic to each cloud region is less than a capacity constraint for that region, the maximum deviation of traffic to each cloud regions at any point in time is less than a given percentage, and the maximum deviation of traffic between direct and indirect paths is less than a given percentage.

Abstract: Systems and methods for validation of transaction policy compliance are provided. Code is implemented, including a transaction policy compliance check, in a form of a trusted application to be executed in a trusted execution environment (TEE). A secret is attested and provisioned to a trusted application instance in the TEE. The trusted application instance is executed on a client transaction request to generate a policy compliance result. A transaction object is generated, including the policy compliance result and a proof of the execution. The transaction object is proposed to a distributed ledger system. The policy compliance result and a proof of the execution during transaction validation in the distributed ledger system is verified.

Abstract: In a method for validation of a finality proof in a distributed ledger system network a support node collects a required number of confirmations from the distributed ledger system network indicating that a requested transaction is finalized. The support node generates the finality proof based on the collected confirmations. The support node transmits the finality proof to a trusted agent for verification.

Abstract: In various embodiments, domain name system (DNS) servers are implemented on a content distribution network (CDN) infrastructure in order to facilitate centralized control of traffic steering. Each server appliance in the CDN infrastructure acts as both an authoritative DNS nameserver and a dynamic request proxy, and each such server appliance is assigned to one of multiple cloud computing system regions. The assignment of server appliances to cloud regions is based on latency measurements collected via client application probes and an optimization that minimizes an overall latency experienced by the client applications subject to constraints that the maximum traffic to each cloud region is less than a capacity constraint for that region, the maximum deviation of traffic to each cloud regions at any point in time is less than a given percentage, and the maximum deviation of traffic between direct and indirect paths is less than a given percentage.

Abstract: A method for establishing consensus between distributed nodes connected via a data communication network is executed by a leader node. The distributed nodes include active nodes which include the leader node. The method comprises preparing a proposal, constructing a first communication topology and propagating the proposal to the active nodes according to the first communication topology. In case of receiving a sufficient set of vote aggregations from the active nodes, a proposal commitment is created using the vote aggregations and the proposal is accepted. In case of determining that the first communication topology is not reliable to reach consensus on the proposal due to active node faults, an updated communication topology different from the first communication topology is created and the same proposal is continued to be propagated down to the active nodes according to the updated communication topology.

Abstract: Systems and methods for validation of transaction policy compliance are provided. Code is implemented, including a transaction policy compliance check, in a form of a trusted application to be executed in a trusted execution environment (TEE). A secret is attested and provisioned to a trusted application instance in the TEE. The trusted application instance is executed on a client transaction request to generate a policy compliance result. A transaction object is generated, including the policy compliance result and a proof of the execution. The transaction object is proposed to a distributed ledger system. The policy compliance result and a proof of the execution during transaction validation in the distributed ledger system is verified.

Abstract: Systems and methods for validation of transaction policy compliance are provided. Code is implemented, including a transaction policy compliance check, in a form of a trusted application to be executed in a trusted execution environment (TEE). A secret is attested and provisioned to a trusted application instance in the TEE. The trusted application instance is executed on a client transaction request to generate a policy compliance result. A transaction object is generated, including the policy compliance result and a proof of the execution. The transaction object is proposed to a distributed ledger system. The policy compliance result and a proof of the execution during transaction validation in the distributed ledger system is verified.

Abstract: In various embodiments, domain name system (DNS) servers are implemented on a content distribution network (CDN) infrastructure in order to facilitate centralized control of traffic steering. Each server appliance in the CDN infrastructure acts as both an authoritative DNS nameserver and a dynamic request proxy, and each such server appliance is assigned to one of multiple cloud computing system regions. The assignment of server appliances to cloud regions is based on latency measurements collected via client application probes and an optimization that minimizes an overall latency experienced by the client applications subject to constraints that the maximum traffic to each cloud region is less than a capacity constraint for that region, the maximum deviation of traffic to each cloud regions at any point in time is less than a given percentage, and the maximum deviation of traffic between direct and indirect paths is less than a given percentage.

Abstract: In various embodiments, domain name system (DNS) servers are implemented on a content distribution network (CDN) infrastructure in order to facilitate centralized control of traffic steering. Each server appliance in the CDN infrastructure acts as both an authoritative DNS nameserver and a dynamic request proxy, and each such server appliance is assigned to one of multiple cloud computing system regions. The assignment of server appliances to cloud regions is based on latency measurements collected via client application probes and an optimization that minimizes an overall latency experienced by the client applications subject to constraints that the maximum traffic to each cloud region is less than a capacity constraint for that region, the maximum deviation of traffic to each cloud regions at any point in time is less than a given percentage, and the maximum deviation of traffic between direct and indirect paths is less than a given percentage.

Abstract: A trust network has at least one transmission medium supporting transmission of data, wherein data transmitted is in at least some instances transmitted in discrete portions, two or more nodes terminating discrete legs in the transmission medium, and trust software executing from a machine-readable medium by a processor on one or more of the two or more nodes. The one or more nodes executing trust software apply trust logic to transmission of the discrete data portions.

Abstract: A system is provided for routing transactions to individual ones of a group of agents, comprising, a queue wherein transactions to be routed are placed, a transmission facility sending invitations to interact with a transaction from the queue to agents, and a router routing transactions from the queue to individual agents who accept the invitation.

Abstract: In a method for validation of a finality proof in a distributed ledger system network a support node collects a required number of confirmations from the distributed ledger system network indicating that a requested transaction is finalized. The support node generates the finality proof based on the collected confirmations. The support node transmits the finality proof to a trusted agent for verification.

Abstract: In one embodiment of the present invention, a content delivery network (CDN) monitoring system manages a CDN. The CDN monitoring system includes finite state machines (FSMs), and the current states of the FSMs reflect characteristics and/or behaviors associated with the CDN. In operation, the CDN monitoring system computes actions based on current states and/or metrics associated with the CDN. The actions may cause one or more of the FSMs execute state transitions. As part of a state transition, the current state of the FSM changes and an event is generated. The event triggers an event handler that may perform any type of management operations, such as generating performance reports and rerouting client requests. Notably, because each current state may be an aggregation of other current states, the CDN monitoring system may be configured to compute current states that accurately represent complex interactions between components within the CDN.

Abstract: Systems and methods for validation of transaction policy compliance are provided. Code is implemented, including a transaction policy compliance check, in a form of a trusted application to be executed in a trusted execution environment (TEE). A secret is attested and provisioned to a trusted application instance in the TEE. The trusted application instance is executed on a client transaction request to generate a policy compliance result. A transaction object is generated, including the policy compliance result and a proof of the execution. The transaction object is proposed to a distributed ledger system. The policy compliance result and a proof of the execution during transaction validation in the distributed ledger system is verified.

Abstract: A method for providing continuity over a series of transactions is provided, comprising the steps of (a) creating a Portable Continuity Object (PCO) as a defined digital package by an instance of PCO software executing on a computerized appliance also capable of communication transaction; (b) providing identity of a person, an address of a communication device and a continuity context in the PCO; (c) sharing the PCO in related transactions, with the PCO updated with information concerning individual transactions by digital equipment enhanced with an instance of PCO software; and (d) providing context continuity in succeeding transactions by accessing the PCO by one or both parties to a transaction.

Abstract: A method for providing inbound call reservations to a communication center has steps for monitoring service access points into the communication center by reservation software executing from a machine-readable medium, evaluating communicators and potential communicators, and issuing invitations for reserved communication sessions to qualified communicators and potential communicators, the reserved times coordinated according to data pertaining to predicted communication load and resource availability statistics.