Patent classifications
H04L41/0627
Fault recovery method and apparatus, and storage medium
A fault recovery method and apparatus, and a storage medium are provided, and belong to the field of Internet technologies. In the method, network composition information and abnormal event information of a target network are obtained, where the network composition information includes a network topology of the target network and device information of a plurality of network devices on the target network, and the device information includes one or more of interface configuration information, protocol configuration information, and service configuration information; and then a possible root cause of a fault of the target network is determined based on the network composition information and the abnormal event information, where the possible root cause of the fault is used to determine a corresponding fault recovery plan.
Auto switching for enterprise federated network slice
A method in which an enterprise switches its devices to various federated network slices across operators based on cost, time, quality, and/or availability parameters defined in flexible rules managed by the enterprise. The method includes obtaining, by a controller of an enterprise, one or more parameters of a device served by a network slice of a core network. The method further includes, based on the one or more parameters of the device and one or more rules, determining, by the controller, whether a triggering event associated with a slice reselection occurred and based on the triggering event and the one or more rules, selecting, by the controller, a federated network slice from among a plurality of network slices provided by a plurality of core networks. The method further includes the controller causing the device to switch from the network slice to the federated network slice.
Anti-fragile network
Implementations are directed to improving network anti-fragility. In some aspects, a method includes receiving parameter data from a network of nodes, the parameter data comprising attributes, policies, and action spaces for each node in the network of nodes; configuring one or more interruptive events on one or more nodes included in the network of nodes; determining a first action of each node in the network of nodes in response to the one or more interruptive events; determining a first performance metric, for each node, that corresponds to the first action, wherein the first performance matric is determined based on at least a first reward value associated with the first action; continuously updating the first action in an iterative process to obtain a final action, wherein a performance metric corresponding to the final action satisfies a performance threshold, and transmitting the final action for each node to the network of nodes.
Electronic system for dynamic latency reduction through edge computation based on a multi-layered mechanism
Embodiments of the invention are directed to a system, method, or computer program product for dynamic latency reduction through edge computation based on a multi-layered mechanism. In this regard, the invention is structured for proactive de-centralized monitoring and resolution of network issue events and cross-pollination of resolutions of network issue events between network components and dynamic reallocation of technology resources therebetween for load balancing. In some embodiments, the invention comprises an entity communication network comprising a plurality of network device groups, one or more edge nodes, and a central server system. The invention determines, via an edge node, a first resolution vector for a first network issue event. The invention is configured to implement, via a micro edge adaptor of a first component system, the first resolution vector at a component system.
Identifying root causes of network service degradation
Systems and methods are provided for analyzing one or more root causes of service degradation events in a network or other environment. A method, according to one implementation, includes a step of monitoring a plurality of overlying services offered in an underlying infrastructure having a plurality of resources arranged with a specific topology. In response to detecting a negative impact on the overlying services during a predetermined time window and based on an understanding of the specific topology, the method further includes the step of identifying suspect components from the plurality of resources in the underlying infrastructure. The method also includes the step of obtaining status information with respect to the suspect components to determine a root cause of the negative impact on the overlying services.
Connecting and resetting devices
A computer implemented method for managing a connection between a device and a server resource, the method comprising: establishing the connection between the device and a first server of the server resource; registering a connection identifier relating to the connection between the device and the first server in a first database entry of a database arrangement; pre-computing, at the first server, an encrypted alert for the device, the alert being provided with a pre-defined future communication sequence number; and transmitting the alert from the first server to the database arrangement for storage in association with the first database entry of the database arrangement.
FILE SERVER ARRAY AND ENHANCED PIPELINE TRANSMISSION
In an approach for building file server arrays with stable and unstable nodes for enhanced pipeline transmission, a processor builds an array from a plurality of stable nodes, wherein each stable node of the plurality of stable nodes is linked to two other stable nodes of the plurality of stable nodes forming a line. A processor divides a plurality of unstable nodes into one or more groups of unstable nodes. A processor links each group of unstable nodes to two neighboring stable nodes within the array. A processor sends data through the array and the one or more groups of unstable nodes in two opposite directions. A processor monitors a node status for each node of the plurality of stable nodes and the plurality of unstable nodes.
Detection block sending and receiving method, and network device and system
This application provides example detection block sending and receiving methods, and network devices and systems. One example detection block sending method includes obtaining, by a network device, an original bit block data flow. At least one detection block is generated, and the at least one detection block is inserted into a position of at least one idle block in the original bit block data flow. The bit block data flow including the at least one detection block is then sent.
LIKELIHOOD ASSESSMENT FOR SECURITY INCIDENT ALERTS
The principles described herein relate to the training and implementation of a model designed to estimate the probability of new security incidents being true incidents. This occurs in an environment where a service such as a SIEM monitors a network of computing systems and other resources and detects a variety of incidents that could be security threats. These incidents are reported to the SOC for investigation and the SOC will take appropriate action to mitigate potential threats of true security breaches. As part of the investigation process, the SOC can label whether a security incident is true, false or benign. After labeling enough security incidents a model can be produced to estimate the probability that new security incidents are true incidents. This would help the SOC filter through security incidents more efficiently and allow for quicker response of the most likely security breaches.
IN-NETWORK FAILURE INDICATION AND RECOVERY
A programmable switch includes a plurality of ports for communicating with a plurality of network devices. A packet for a distributed system is received via a port and at least one indicator is identified in the received packet. Reliability metadata associated with a network device used for the distributed system is generated using the at least one indicator. The generated reliability metadata is sent to a controller for the distributed system for predicting or determining a reliability of at least one of the network device and a communication link for the network device and the programmable switch.