Patent classifications
H04L41/0631
Causality determination of upgrade regressions via comparisons of telemetry data
Disclosed herein is a system for automating the causality detection process when upgrades are deployed to different resources that provide a service. The resources can include physical and/or virtual resources (e.g., processing, storage, and/or networking resources) that are divided into different, geographically dispersed, resource units. To determine whether a root cause of a problem is associated with an upgrade event that has recently been deployed, a system is configured to use telemetry data to compute an upgrade-to-upgrade score that represents differences between two different upgrade events that are deployed to the same resource unit. The system is further configured to use telemetry data to compute an upgrade unit-to-unit score that represents differences between the same upgrade event being deployed to two different resource units. The scores can be used to output an alert, for an analyst, that signals whether a recently deployed upgrade event is the cause of a problem.
VIDEO-BASED MAINTENANCE METHOD, MAINTENANCE TERMINAL, SERVER, SYSTEM AND STORAGE MEDIUM
A video based maintenance method, a maintenance terminal, a server, a system, and a storage medium. The method includes: receiving, by a maintenance terminal, a maintenance order sent by a server, wherein the maintenance order is generated according to a maintenance request sent by a client, and the maintenance order comprises customer information, faulty product information and fault information; and wherein the fault information comprises one or more troubleshooting points; receiving, by the maintenance terminal, a video stream sent by the client; and recording, by the maintenance terminal, troubleshooting information of the troubleshooting points, and sending the troubleshooting information to the server.
VIDEO-BASED MAINTENANCE METHOD, MAINTENANCE TERMINAL, SERVER, SYSTEM AND STORAGE MEDIUM
A video based maintenance method, a maintenance terminal, a server, a system, and a storage medium. The method includes: receiving, by a maintenance terminal, a maintenance order sent by a server, wherein the maintenance order is generated according to a maintenance request sent by a client, and the maintenance order comprises customer information, faulty product information and fault information; and wherein the fault information comprises one or more troubleshooting points; receiving, by the maintenance terminal, a video stream sent by the client; and recording, by the maintenance terminal, troubleshooting information of the troubleshooting points, and sending the troubleshooting information to the server.
NETWORK MANAGEMENT APPARATUS, METHOD, AND PROGRAM
A network management apparatus according to an embodiment includes: a storage device configured to store information indicating a correspondence relationship between information objects related to a logical layer, information objects related to a physical layer in a network configuration, and information objects related to a facility layer which are objects in which the information objects related to the physical layer are housed; an acquisition unit configured to acquire an information object related to an occurrence path of a failure in the logical layer of the network configuration, from the storage device; and a search unit configured to search for, among the information objects related to the facility layer stored in the storage device, an information object related to the facility layer and the physical layer associated with the information object related to the occurrence path of the failure acquired from the acquisition unit, as a candidate for a facility that causes the failure.
NETWORK MANAGEMENT APPARATUS, METHOD, AND PROGRAM
A network management apparatus according to an embodiment includes: a storage device configured to store information indicating a correspondence relationship between information objects related to a logical layer, information objects related to a physical layer in a network configuration, and information objects related to a facility layer which are objects in which the information objects related to the physical layer are housed; an acquisition unit configured to acquire an information object related to an occurrence path of a failure in the logical layer of the network configuration, from the storage device; and a search unit configured to search for, among the information objects related to the facility layer stored in the storage device, an information object related to the facility layer and the physical layer associated with the information object related to the occurrence path of the failure acquired from the acquisition unit, as a candidate for a facility that causes the failure.
Wireless access network element status reporting
A wireless communication network manages a wireless access node. The wireless access node wirelessly exchanges user data with wireless User Equipment (UEs) and exchanges the user data with one or more network elements. The wireless access node generates status indicators that characterize wireless access node operation during the user data exchanges. An Element Management System (EMS) determines EMS load based on EMS operation and transfers load data that indicates the EMS load for delivery to the wireless access node. The wireless access node receives the load data transferred by the EMS. The wireless access node identifies individual priorities for individual ones of the status indicators. The wireless access node determines individual reporting times for the individual ones of the status indicators based on the load data and the individual priorities. The wireless access node transfers the individual ones of the status indicators to the EMS per the individual reporting times.
ROOT-CAUSING USER EXPERIENCE ANOMALIES TO COORDINATE REACTIVE POLICIES IN APPLICATION-AWARE ROUTING
In one embodiment, a device obtains user experience metrics for a plurality of sessions with an online application. The device detects a plurality of anomalies from among the user experience metrics. The device determines, based on a correlation between the plurality of anomalies, that a particular path entity is a root cause of the plurality of anomalies. The particular path entity comprises an egress service provider or data center of the online application. The device provides an indication of the particular path entity being the root cause of the plurality of anomalies.
ROOT-CAUSING USER EXPERIENCE ANOMALIES TO COORDINATE REACTIVE POLICIES IN APPLICATION-AWARE ROUTING
In one embodiment, a device obtains user experience metrics for a plurality of sessions with an online application. The device detects a plurality of anomalies from among the user experience metrics. The device determines, based on a correlation between the plurality of anomalies, that a particular path entity is a root cause of the plurality of anomalies. The particular path entity comprises an egress service provider or data center of the online application. The device provides an indication of the particular path entity being the root cause of the plurality of anomalies.
Method and Apparatus for Determining Fault Root Cause and Related Device
A method for determining a fault root cause includes obtaining first fault information, where the first fault information includes M alarms, and M is an integer greater than or equal to 1; determining, from N pieces of known fault information based on the M alarms, at least one piece of known fault information that matches the first fault information, where each of the N pieces of known fault information includes a plurality of alarms; and determining, based on a fault root cause of the at least one piece of known fault information, information related to a root cause of the first fault information. The root cause of the first fault information is determined by using the known fault information that matches the first fault information.
Method and Apparatus for Determining Fault Root Cause and Related Device
A method for determining a fault root cause includes obtaining first fault information, where the first fault information includes M alarms, and M is an integer greater than or equal to 1; determining, from N pieces of known fault information based on the M alarms, at least one piece of known fault information that matches the first fault information, where each of the N pieces of known fault information includes a plurality of alarms; and determining, based on a fault root cause of the at least one piece of known fault information, information related to a root cause of the first fault information. The root cause of the first fault information is determined by using the known fault information that matches the first fault information.