A proxy server receives, from multiple visitors of multiple client devices, a plurality of requests for actions to be performed on identified network resources belonging to a plurality of origin servers. At least some of the origin servers belong to different domains and are owned by different entities. The proxy server and the origin servers are also owned by different entities. The proxy server analyzes each request it receives to determine whether that request poses a threat and whether the visitor belonging to the request poses a threat. The proxy server blocks those requests from visitors that pose a threat or in which the request itself poses a threat. The proxy server transmits the requests that are not a threat and is from a visitor that is not a threat to the appropriate origin server.

A domain name is received from a customer. DNS is queried for multiple possible subdomains of the domain. For each subdomain that resolves, information about that subdomain's corresponding resource record is stored in a zone file that also includes a resource record for the domain name. The zone file is presented to the customer. A designation from the customer of which of the resource records are to point to an IP address of a proxy server is received. The resource records are modified according to the input of the customer and the zone file is propagated including the modified resource records.

An event clustering system has an extraction engine in communication with a managed infrastructure. A signalizer engine includes one or more of an NMF engine, a k-means clustering engine and a topology proximity engine. The signalizer engine determines one or more common characteristics or features from events, the signalizer engine using the common features of events to produce clusters of events relating to the failure or errors in the managed infrastructure. Membership in a cluster indicates a common factor of the events that is a failure or an actionable problem in the physical hardware managed infrastructure directed to supporting the flow and processing of information. The system is configured to group two or more situations, where a situation is a collection of one or more events or alerts representative of a problem in the managed infrastructure.

Disclosed is a method for wireless typology discovery for train backbone networks. The method comprises steps of: receiving a data from a neighboring backbone node (BN), by a BN in a train backbone network through one directional antenna of at least one pair of directional antennas provided thereon; recording a receiving direction of said data, and determining said data to be a hello frame or a typology frame; performing neighbor discovery or topology discovery based on the type of said data; in neighbor discovery phase, performing a pair consistency check with respect to all the data received by the BN from a same direction, so as to identify a neighboring BN of the BN, and at the same time, stopping receiving hello frames from said direction by the BN; in typology discovery phase, updating a local typology table of the current BN based on the received typology frames; and performing a topology convergence check to see if any change occurs to the local typology table of the current BN, and if no change occurs, reporting on the status of the typology discovery phase to an up-level application.

One embodiment is directed to a system to provide wireless service to user equipment. The system comprising a controller communicatively coupled to a core network and a plurality of radio points to transmit and receive radio frequency signals to and from the user equipment. Each of the radio points is associated with at least one antenna and is located remote from the controller. The plurality of radio points is communicatively coupled to the controller. The controller comprises at least one baseband modem to perform Layer-3, Layer-2, and Layer-1 processing for the air interface. The controller is configured to automatically control transmit power for the radio points based on operational measurements (OMs) for each radio point, wherein the OMs are based on radio resource control (RRC) messages received at the controller. In some implementations, the radio points are configured to perform at least some Layer-1 processing for the air interface.

A computer implemented method, apparatus, and computer usable program code for processing data packets. A set of data fragments are received at the data processing system to form a set of received data fragments. Assembly of the set of data fragments is initiated into a data packet, and a determination as to whether the data packet is an incomplete data packet. Responsive to a determination that the data packet is an incomplete data packet, the incomplete data packet is filled with at least one character to form a final data packet. The final data packet is forwarded to the target.

A distributed node service management system utilizes multiple existing processor nodes of a distributed computing system, in support of the primary data processing functions of the distributed computing system. The distributed node service management system coordinates and manages service functions on behalf of processor nodes of the distributed computing system. Other features and aspects may be realized, depending upon the particular application.

Systems and methods herein provide for a clustered content management comprising at least two computing nodes. A first node comprises an instance of the content repository. The first computing node may perform content management operations on its instance of the content repository. Changes to the instance of the content repository of the first computing node are synchronized with the content repository by way of a second computing node. The second computing node is communicatively coupled to the first computing node through a network and is operable to synchronize the change with the content repository. The second computing node also determines that synchronization of the change is blocked due to an error. The second computing node identifies the error, determines that the error is correctable, and corrects the error to synchronize the change with the content repository.

A data center failure management system and method in a Software Defined Networking (SDN) deployment. In one embodiment, an SDN controller associated with the data center is configured to learn new flows entering the data center and determine which flows require flow stickiness. Responsive to the determination, the SDN controller generates commands to one or more switching nodes and/or one or more border gateway nodes to redirect the sticky flows arriving at the switching nodes via ECMP routes from the gateway nodes or avoid the ECMP routes by the gateway nodes in order to overcome certain failure conditions encountered in the data center, an external network, or both.

To ensure that there is an elected manager among storage nodes of an erasure coding group (“ECG”), an ECG manager (“ECGM”) election process is periodically performed among available storage nodes that are configured with the software to perform the services of an ECGM. When a storage node is activated, an ECGM process of the storage node begins executing and is assigned a process identifier (“PID”). A storage node can utilize a service query framework to identify other available storage nodes and retrieve their ECGM PIDs. The storage node then selects a PID according to a criterion and elects the storage node corresponding to the selected PID to be the acting ECGM. This process is performed periodically, so even if the acting ECGM storage node fails, a new ECGM is eventually selected from the available storage nodes.