Sophos Limited

Cisco Technology, Inc.

Synamedia Limited

Sanjeev Maheve

Andrew James Thomas

Venkata Suresh Reddy Obulareddy

Biju Ramachandra Kaimal

Reuven Wachtfogel

Nikhil Bhandari

Thiyagu Rajendran

Prashil Rakeshkumar Gupta

Amit Katyal

Neha Parshottam Patel

Laurent Bertrand

Avni Bhupendrakumar Wala

Sanjay Viswanatha Chamarajanagar

Madan Mohan Nayak

Srisakthi Subramaniam

Georgekutty Thekkel Jose

Mayur Premi

Matthew Charles Setzer

Robert W Cook

Ramesh Kamath

A cluster of nodes are sequentially updated with new network configuration settings in order to maintain availability of the cluster during the update. In the sequential update, each node conditionally updates network configuration settings, tests connectivity, and retains an update to the configuration only if the node is able to restore connectivity suitable for operation in the cluster.

Network configuration update

A cloud computing platform provides zero trust network access as a service to a customer that maintains an application on-premises. In this context, the customer may be required to demonstrate ownership of a domain before the cloud computing platform will provide access to the on-premises application via the domain.

Domain ownership verification for a ZTNA service platform

Certain edge networking devices such as application gateways may report status to a cloud-based threat management platform using a persistent network connection between the gateway and the cloud platform. Where a cloud computing platform for an edge networking device or the treat management platform imposes periodic timeouts, the threat management platform may monitor connects and disconnects for edge devices and asynchronously evaluate connection status of edge devices independently of a heartbeat or other signal through the persistent connection in order to distinguish periodic timeouts imposed by the cloud computing platform from networking devices that are compromised or malfunctioning.

Cloud management of connectivity for edge networking devices

Techniques for dynamic data center load balancing using Border Gateway Protocol (BGP) are described. In one embodiment, a method includes monitoring a load on a first data center by a Domain Name System (DNS) server, where the first data center shares a same Internet Protocol (IP) address with at least a second data center. Upon determining that the load on the first data center exceeds a threshold, the method includes changing weights associated with BGP routes to servers of the first data center to be smaller than weights associated with BGP routes to servers of the second data center. The method also includes advertising, by an edge router, the BGP routes to servers of the second data center and, upon receiving a new connection request from a user, connecting the user to a server of the second data center based on an advertised BGP route.

Dynamic data center load balancing using border gateway protocol

There are instances of a content item having synchronization information, one being an instance of a reference content item, another being a candidate content item. A synchronizing processor determines a synchronization point between the reference content item and the candidate content item, on the basis of matching the synchronization information of the reference content item and the candidate content item. A timeline metadata transmitter transmits stored timeline metadata to a device on which the reference content item is playing, the transmission of the stored timeline metadata beginning from the synchronization point. The stored timeline metadata includes timeline metadata that has been previously aggregated from earlier broadcasts of instances of the reference content item. Related systems, apparatus, and methods are also described.

Synchronizing broadcast timeline metadata

Growing community of inventors

Bengaluru, India

Sanjeev Maheve