Systems, methods, and storage media for detecting a security intrusion of a network device are disclosed. Exemplary implementations may include a method involving, in the network device including a processor, monitor a light signal associated with a security enabled port of the network device; and in response to detecting a change in the light signal, initiate a security alert.
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for providing multiple egress points from a telecommunications network for a client of the network. In particular, the process and system allows for multiple provider edges of the network to utilize a route reflector server to provide a border gateway protocol (BGP) route to other provider edges in the network. Further, the multiple provider edges may each announce similar interior gateway protocol (IGP) routes through the network such that a provider edge receiving a packet intended for the customer network may select from the multiple IGP routes to provide the intended packet to the customer network. In this manner, the receiving provider edge may load balance among the various connections of the customer network to the telecommunications network.
Examples described herein relate to apparatuses and methods for associating a first account with a second account, the first account being hosted by a first server, the second account being hosted by a second server, including but not limited to, authenticating, by the first server, first login credentials associated with the first account, wherein the first login credentials are received from a user device, receiving, by the first server from the user device, second login credentials associated with the second account, sending, by the first server, the second login credentials to the second server for authentication, in response to determining that the second login credentials are authenticated by the second server, associating, by the first server, the first account with the second account, and connecting, by the first server to the second server, to allow the user device to access services commensurate with the second account without prompting the user device for the second login credentials.
This disclosure describes systems, methods, and devices related to processing Bank Administration Institute (BAI) files. A method may include identifying, by at least one processor of an integration server, copies of BAI files indicative of payment information; importing, by the at least one processor, data from the BAI files into a staging table; parsing, by the at least one processor, the data in the staging table using a hierarchy defining a file level, a group level, an account level, and a transaction level to generate hierarchized data; normalizing, by the at least one processor, the hierarchized data into tables; and copying, by the at least one processor, differences between the hierarchized data and previous hierarchized data to a workflow associated with identifying payment amounts in the hierarchized data.
Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.
A data network analysis system includes a computer-executable set of instructions that obtain service account information associated with a route provided to a customer through a data communication network having network elements. Using the service account information, the instructions identify a termination port that terminates the route to a customer premises equipment of the customer, and at least one target port of the route and those network elements that are assigned to convey the route through one or more of the network elements. The instructions then obtain the routing information for the route from each of the network elements that are assigned to convey the route.
H04L 43/045 - Traitement des données de surveillance capturées, p.ex. pour la génération de fichiers journaux pour la visualisation graphique des données de surveillance
H04L 43/08 - Surveillance ou test en fonction de métriques spécifiques, p.ex. la qualité du service [QoS], la consommation d’énergie ou les paramètres environnementaux
H04L 43/10 - Surveillance active, p.ex. battement de cœur, utilitaire Ping ou trace-route
Systems and methods are provided for distributing a domain name service (DNS) response cache in a DNS resolving system on a network. The systems and methods described herein may improve response times for client queries and also protect the DNS resolving system from DNS related cyber attacks
H04L 61/58 - Mise en antémémoire d'adresses ou de noms
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 61/5076 - Mécanismes de mise à jour ou de notification, p.ex. DynDNS
Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.
H04L 41/0604 - Gestion des fautes, des événements, des alarmes ou des notifications en utilisant du filtrage, p.ex. la réduction de l’information en utilisant la priorité, les types d’éléments, la position ou le temps
H04L 41/0631 - Gestion des fautes, des événements, des alarmes ou des notifications en utilisant l’analyse de la corrélation entre les notifications, les alarmes ou les événements en fonction de critères de décision, p.ex. la hiérarchie ou l’analyse temporelle ou arborescente
9.
Global Internet Protocol Management System (GIMS) For Monitoring Network Devices for Fault Management
Novel tools and techniques are provided for implementing global Internet Protocol management system (“GIMS”) for monitoring network devices for fault management. In various embodiments, a computing system may receive a first alert associated with a first device among layer 2 and/or layer 3 devices disposed in a plurality of networks; may collect first alert data and/or first device data; may store the first alert together with the collected first alert data and/or first device data as first consolidated alert data in a first database; may perform, using an enrichment system, enrichment of the first alert, by retrieving first enrichment data from one or more second databases and adding the first enrichment data to the first consolidated alert data in the first database; and may send the first consolidated alert data to a fault management system for display to a user to facilitate addressing of the first alert by the user.
Novel tools and techniques are provided for implementing software-based network probes for monitoring network devices for fault management. In various embodiments, a computing system may receive, from at least one software-based network probe, a first alert associated with a first device among layer 4 devices disposed in a plurality of networks; may parse and store first alert data from the received first alert in a database, in a standardized format; may perform, using an enrichment system, enrichment of the first alert data, by retrieving first enrichment data from one or more second databases and adding the first enrichment data to the parsed and formatted first alert data in the first database to form first consolidated alert data; and may send the first consolidated alert data to a fault management system for display to a user to facilitate addressing of the first alert by the user.
A content delivery network (CDN) includes a plurality of CDN components including at least one CDN rendezvous mechanism and at least one control core. The CDN components are controlled by control core data from the at least one control core. Some CDN components obtain CDN resources including control core data from at least some other CDN components. The CDN components use the CDN rendezvous mechanism to select one or more CDN components from which to obtain CDN resources.
H04L 67/60 - Ordonnancement ou organisation du service des demandes d'application, p.ex. demandes de transmission de données d'application en utilisant l'analyse et l'optimisation des ressources réseau requises
H04L 41/0853 - Récupération de la configuration du réseau; Suivi de l’historique de configuration du réseau en recueillant activement des informations de configuration ou en sauvegardant les informations de configuration
H04L 41/0893 - Affectation de groupes logiques aux éléments de réseau
H04L 41/50 - Gestion des services réseau, p.ex. en assurant une bonne réalisation du service conformément aux accords
H04L 41/5061 - Gestion des services réseau, p.ex. en assurant une bonne réalisation du service conformément aux accords caractérisée par l’interaction entre les fournisseurs de services et leurs clients réseau, p.ex. la gestion de la relation client
H04L 67/00 - Dispositions ou protocoles de réseau pour la prise en charge de services ou d'applications réseau
Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.
The present disclosure is directed to consolidation of STP pairs without deploying new STP pairs and without making changes at a Service Switching Point to reflect the consolidation. In one aspect, a method includes identifying a first pair of signal transfer point devices to be decommissioned from a telecommunication network; identifying a second pair of signal transfer point devices to assume, in part, functionalities of the first pair of signal transfer point devices, each signal transfer point device of the first pair and the second pair having at least one primary point code and at least one secondary point code assigning a temporary secondary point code to each signal transfer point device of the first pair; and modifying at least one secondary point code of each signal transfer point device of the second pair with a primary point code of at least one signal transfer point device of the first pair.
H04L 41/0816 - Réglages de configuration caractérisés par les conditions déclenchant un changement de paramètres la condition étant une adaptation, p.ex. en réponse aux événements dans le réseau
H04L 41/082 - Réglages de configuration caractérisés par les conditions déclenchant un changement de paramètres la condition étant des mises à jour ou des mises à niveau des fonctionnalités réseau
H04L 41/0826 - Réglages de configuration caractérisés par les objectifs d’un changement de paramètres, p.ex. l’optimisation de la configuration pour améliorer la fiabilité pour la réduction des coûts du réseau
H04W 24/02 - Dispositions pour optimiser l'état de fonctionnement
H04W 76/11 - Attribution ou utilisation d'identifiants de connexion
14.
DYNAMIC BINDING AND LOAD DETERMINATION IN A CONTENT DELIVERY NETWORK
A content provider has a plurality of content provider domain names, and a content delivery network (CDN) allocates a plurality of CDN domain names to the particular content provider. The content provider domain names are mapped to the CDN domain names. CDN domain names are bound to corresponding CDN clusters. The binding of the of CDN domain names to corresponding CDN clusters is modified.
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 61/25 - Correspondance entre adresses du même type
H04L 61/3015 - Enregistrement, génération ou allocation de nom
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for an orchestrator device associated with a scrubbing environment of a telecommunications network that receives one or more announced routing protocol advertisements from a customer device under an attack. In response to receiving the announcement, the orchestrator may configure one or more scrubbing devices of the network to begin providing the scrubbing service to packets matching the received routing announcement. A scrubbing service state for the customer may also be obtained or determined by the orchestrator. With the received route announcement and the customer profile and state information, the orchestrator may provide instructions to configure the scrubbing devices of the network based on the received information to dynamically automate scrubbing techniques without the need for a network administrator to manually configure the scrubbing environment or devices.
A computer-implemented method, operable with a content delivery network (CDN) uses late binding of caching policies; by a caching node in the CDN, in response to a request for content, determining if the content is cached locally. When it is determined that said content is cached locally, then: determining a current cache policy associated with the content; and then determining, based on said current cache policy associated with the content, whether it is acceptable to serve the content that is cached locally; based on said determining, when it is not acceptable to serve the content that is cached locally, obtaining a new version of the content and then serving the new version of the content, otherwise when it is acceptable to serve the content that is cached locally, serving the content that is cached locally.
Novel tools and techniques are provided for implementing intelligent alert automation (“IAA”). In various embodiments, IAA receives alert/event feeds from several different alerting and ticketing systems via input Redis queues, and uses a triage system to determine whether to process the alert/event or disregard it. If so, IAA may create a flow instance, assign a unique instance ID, and place the flow instance in one of a plurality of jobs queues based on alert/event type and/or or source. An abattoir system retrieves a flow instance from one of the jobs queues (in order of the queue's priority), and processes the next node or step in the flow instance. The flow instance is placed back into the jobs queue for subsequent processing by the same or different abattoir system until no additional nodes or steps remain in the flow, at which point the flow instance is considered complete.
This disclosure describes systems, methods, and devices related to automating and testing communication network topologies. A method may include identifying templates of respective communication network topologies defining network devices, connections between the network devices, roles for the network devices, and performance tests for the communication network topologies; selecting a first template; instantiating an instance to generate a first communication network topology by establishing first connections between first network devices based on the first communication network topology and first roles of first network devices of the first communication network topology; generating performance test results for the first communication network topology based on performance of first performance tests defined by the first template, wherein first test thresholds of the first performance tests are based on a machine learning model trained based on the communication network topologies and the performance tests; and modifying the first test thresholds based on the performance test results.
H04L 41/12 - Découverte ou gestion des topologies de réseau
H04L 41/16 - Dispositions pour la maintenance, l’administration ou la gestion des réseaux de commutation de données, p.ex. des réseaux de commutation de paquets en utilisant l'apprentissage automatique ou l'intelligence artificielle
Novel tools and techniques are provided for implementing real-time fault management or real-time fault management system (“RFM”). In various embodiments, RFM may receive alerts from or associated with network devices (e.g., layer 2, 3, and/or 4 devices, or the like) that are disposed in a plurality of disparate networks that may utilize different alert management protocols and/or different fault management protocols. RFM may collect, enrich, normalize, aggregate, and display the alerts in a user interface to facilitate addressing of the alerts by a user. To enable continuous and real-time functionality, RFM may be implemented in a plurality of siloed platforms in a primary data center, with processing of alerts being load balanced across the siloed platforms, with mirrored group of siloed platforms in a secondary data center located geographically distant from the primary data center and configured to be on “hot standby” and to completely take over RFM processing operations.
Novel tools and techniques are provided for implementing dashboard for alert storage and history (“DASH”). In various embodiments, DASH provides for consolidated tracking and monitoring of two or more of current (or active) alerts, cleared alerts, and/or transactional information for alerts that are stored within corresponding alert live database that mirrors current alert instance data in a real-time fault management system, alert history database that contains a snapshot of an alert history of each alert or corresponding network device, and/or alert log database that contains a full transaction record of every copy of an alert either over a first duration or having a total data size within a first total data size. DASH also cleans received alert data and/or enriches the alert data, and provides a user interface (“UI”) that enables a user to view, absorb, filter, manage, and/or organize alert data to facilitate addressing of alerts in the network(s).
A quality of service management system includes a rules engine that receives information associated with a communication path having an assigned quality of service (QoS) to be provided for a customer communication device, and identifies one or more network elements assigned to provide the communication path. Each network element having a plurality of queues configured to provide varying QoS levels relative to one another. For each of the network elements, the rules engine determines at least one queue that is configured to provide the communication path at the assigned quality of service, and transmits queue information associated with the determined queue to its respective network element, the network element conveying the communication path through the determined queue.
H04L 47/24 - Trafic caractérisé par des attributs spécifiques, p.ex. la priorité ou QoS
H04L 45/302 - Détermination de la route basée sur la qualité de service [QoS] demandée
H04L 47/62 - Ordonnancement des files d’attente caractérisé par des critères d’ordonnancement
H04L 47/2408 - Trafic caractérisé par des attributs spécifiques, p.ex. la priorité ou QoS pour la prise en charge de différents services, p.ex. services du type services différentiés [DiffServ]
22.
SYSTEMS AND METHODS FOR PROCESSING REQUESTS FOR CONTENT OF A CONTENT DISTRIBUTION NETWORK
Improved methods for retrieval of content from CDNs is provided that includes a rendezvous controller that receives information of an identification of content being requested and an estimated location of a content requesting device. Based on this information, the rendezvous system identifies a server within a CDN from which the requested content may be retrieved. The selected server may be based on a repeatable hash function such that the likelihood that the content being requested is cached at the selected server. Steering requests to a server of the CDN which may have the content cached may reduce the number of servers within the CDN with the same cached content, particularly for the highest requested content. The rendezvous system may then return a corresponding domain name associated with the selected server and that can be subsequently submitted to a DNS for resolution to the IP address of the identified server.
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 9/32 - Dispositions pour les communications secrètes ou protégées; Protocoles réseaux de sécurité comprenant des moyens pour vérifier l'identité ou l'autorisation d'un utilisateur du système
H04L 61/5007 - Adresses de protocole Internet [IP]
H04L 67/52 - Services réseau spécialement adaptés à l'emplacement du terminal utilisateur
H04L 67/568 - Stockage temporaire des données à un stade intermédiaire, p.ex. par mise en antémémoire
Systems and methods for dynamically mitigating a DDOS attack. In an aspect, the technology relates to a computer-implemented method for dynamically mitigating a distributed-denial-of-service (DDOS) attack. The computer-implemented method may include detecting a DDOS attack directing malicious traffic to a target, identifying one or more source locations of the malicious traffic, and in response to detecting the DDOS attack, activating one or more scrub clusters in the identified one or more source locations of the malicious traffic. The method may further include directing traffic intended for the target to the to the activated one or more scrub clusters, detecting an end of the DDOS attack, and in response to detecting the end of the DDOS attack, deactivating the one or more scrub clusters to release hardware resources.
Aspects of the present disclosure involve systems for providing multiple egress routes from a telecommunications network for a client of the network. In general, the system provides for a client of the network to receive intended packets of information through multiple connections to the network such that load balancing and failover services for traffic to the customer are provided. The process and system allow for telecommunications network to utilize a common next-hop value of announced border gateway protocol (BGP) routes to advertise multiple routes to reach a destination customer network or address. By utilizing a common next-hop value in the announced BGP information, the devices of the network may load balance communication packets to the destination customer or address among the multiple egress locations from the network, as well as providing fast failover to alternate routes when a failure at the network or customer occurs.
H04L 45/02 - Mise à jour ou découverte de topologie
H04L 45/122 - Routage ou recherche de routes de paquets dans les réseaux de commutation de données Évaluation de la route la plus courte en minimisant les distances, p.ex. en sélectionnant une route avec un nombre minimal de sauts
H04L 45/00 - Routage ou recherche de routes de paquets dans les réseaux de commutation de données
Examples of the present disclosure relate to the optical identification of telecommunications equipment. In examples, a user interacts with an application to capture image data relating to a device according to instructions presented to the user. The application may further generate metadata, such as user responses to one or more questions. The image data and/or metadata are evaluated using a machine learning model to generate an equipment classification for devices pictured therein. The data may also be used to generate an equipment configuration for the device, as well as an operational state (e.g., based on one or more indicators present on the device, log data, etc.). Accordingly, such information may be used to update a pre-existing inventory record for the device, or generate a new inventory record. In other examples, such information is used to generate one or more predicted issues and associated actions to troubleshoot the device.
G06Q 30/016 - Fourniture d’une assistance aux clients, p. ex pour assister un client dans un lieu commercial ou par un service d’assistance après-vente
H04L 41/069 - Gestion des fautes, des événements, des alarmes ou des notifications en utilisant des journaux de notifications; Post-traitement des notifications
H04L 41/0631 - Gestion des fautes, des événements, des alarmes ou des notifications en utilisant l’analyse de la corrélation entre les notifications, les alarmes ou les événements en fonction de critères de décision, p.ex. la hiérarchie ou l’analyse temporelle ou arborescente
G06K 7/10 - Méthodes ou dispositions pour la lecture de supports d'enregistrement par radiation corpusculaire
G06K 19/07 - Supports d'enregistrement avec des marques conductrices, des circuits imprimés ou des éléments de circuit à semi-conducteurs, p.ex. cartes d'identité ou cartes de crédit avec des puces à circuit intégré
G06Q 10/087 - Gestion d’inventaires ou de stocks, p.ex. exécution des commandes, approvisionnement ou régularisation par rapport aux commandes
G06F 18/21 - Conception ou mise en place de systèmes ou de techniques; Extraction de caractéristiques dans l'espace des caractéristiques; Séparation aveugle de sources
Aspects of the present disclosure involve a CDN utilizing a Direct Server Return (DSR) request command to create a tunnel from one content server to another content server of the CDN. Through the DSR tunnel, a request for content may be served from a content server that is more advantageous for the CDN for any number of reasons, such as from a content server that is logically closer to the content server. In determining when a DSR tunnel is created to provide the content, the CDN may access a database storing various information concerning the CDN, such as the location of egress gateways of the CDN in relation to one or more content servers, connecting network location information, the capabilities of one or more content servers, and/or load information of available content servers.
H04L 67/52 - Services réseau spécialement adaptés à l'emplacement du terminal utilisateur
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
27.
STREAMING SERVER STATISTICS AND PREDICTIVE MITIGATION
Aspects of the present disclosure involve systems and methods for improving the performance of a telecommunications network by monitoring the performance of one or more storage drives. Operational data is received from a plurality of storage drives of a storage server of a telecommunications network. A plurality of operational coefficients for each of the plurality of storage drives is derived based on the operational data, and a cluster plot is created from the plurality of operational coefficients for each of the plurality of storage drives. A distance is calculated between a subset of operational coefficients of the plurality of operational coefficients of the cluster plot, and a remedial action is initiated on a storage drive of the plurality of storage drives when a calculated distance of an operational coefficient associated with the storage drive exceeds a distance value from a cluster of the cluster plot.
G06F 11/07 - Réaction à l'apparition d'un défaut, p.ex. tolérance de certains défauts
H04L 41/16 - Dispositions pour la maintenance, l’administration ou la gestion des réseaux de commutation de données, p.ex. des réseaux de commutation de paquets en utilisant l'apprentissage automatique ou l'intelligence artificielle
H04L 41/142 - Analyse ou conception de réseau en utilisant des méthodes statistiques ou mathématiques
H04L 41/147 - Analyse ou conception de réseau pour prédire le comportement du réseau
G06F 3/06 - Entrée numérique à partir de, ou sortie numérique vers des supports d'enregistrement
28.
DYNAMIC OPTICAL SWITCHING IN A TELECOMMUNICATIONS NETWORK
Implementations described and claimed herein provide systems and methods for a configurable optical peering fabric to dynamically create a connection between participant sites without any physical site limitations or necessity of specialized client and network provider equipment being located within such a facility. Client sites to a network may connect to a configurable switching element to be interconnected to other client sites in response to a request to connect the first client site with a second site, also connected to network, via the switching element. A request may trigger verification of the requested and, upon validation, transmission of an instruction to the switching element to enable the cross connect within the switching element. The first site and the second site may thus be interconnected via the switching element in response to the request, without the need to co-locate equipment or to manually install a jumper between client equipment.
Systems and methods for receiving information on network firewall policy configurations are disclosed. Based on the received firewall configuration information, a configuration of a firewall and/or subnet of network devices is automatically provisioned and/or configured to control network traffic to and from the subnet.
Systems and methods are provided for generating a network ingress filter based on both a customer's route object and recent traffic data for the customer. In examples, even though a customer of a provider network may have many routing prefixes in its route object, the customer may genuinely generate traffic from only a very small percentage of such prefixes. Accordingly, a combination of a system to generate all the prefixes based on a route object, along with the results of collected traffic data, may be used to generate a much smaller ingress filter. In examples, this filter may comprise an intersection of the prefixes generated by the customer's route object and the prefixes that have been actively generating traffic on the inbound interface of the router (or other provider edge system). This results in a smaller ingress filter that can be reliably configured on the provider edge system.
Improved methods for retrieval of content from CDNs is provided that includes a rendezvous controller that receives information of an identification of content being requested and an estimated location of a content requesting device. Based on this information, the rendezvous system identifies a server within a CDN from which the requested content may be retrieved. The selected server may be based on a repeatable hash function such that the likelihood that the content being requested is cached at the selected server. Steering requests to a server of the CDN which may have the content cached may reduce the number of servers within the CDN with the same cached content, particularly for the highest requested content. The rendezvous system may then return a corresponding domain name associated with the selected server and that can be subsequently submitted to a DNS for resolution to the IP address of the identified server.
H04L 67/60 - Ordonnancement ou organisation du service des demandes d'application, p.ex. demandes de transmission de données d'application en utilisant l'analyse et l'optimisation des ressources réseau requises
G06F 16/22 - Indexation; Structures de données à cet effet; Structures de stockage
G06F 16/29 - Bases de données d’informations géographiques
H04L 67/10 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 67/52 - Services réseau spécialement adaptés à l'emplacement du terminal utilisateur
Novel tools and techniques are provided for implementing application programming interface (“API”)-based concurrent call path (“CCP”) provisioning. In various embodiments, in response to receiving a CCP provisioning request, a computing system may determine whether such a request would affect a set of trunk groups assigned to a customer based at least in part on network utilization data. If not, the computing system may cause the nodes in the network to increase or decrease, in near-real-time, the number of CCPs in at least one trunk group assigned to the customer based on the CCP provisioning request. If so, the computing system may cause the nodes in the network to increase or decrease, in near-real-time, the number of trunk groups assigned to the customer and may cause the nodes in the network to increase or decrease, in near-real-time, the number of CCPs in the updated number of trunk groups.
Apparatuses and methods are disclosed for managing network connections. A computing device accesses a request to provision a network connection associated with a first device. The request includes a plurality of connection parameters defining desired specifications for a network connection from the first device to a second device. The connection parameters are validated against information from a database and other predetermined rules. A network connection path is generated to connect the first device with the second device. The network connection path is generated by selecting network elements for the network connection that satisfy the connection parameters. Configuration information for the network elements of the network connection path is aggregated for a configuration system. The configuration information is used to provision the network connection.
Novel tools and techniques are provided for implementing wireless functionality, and, more particularly, to methods, systems, and apparatuses for implementing faceplate-based wireless device functionality and wireless extension functionality. In various embodiments, one or more antennas, a power adapter, and at least one processor may be attached to an inner surface of a faceplate configured to be attached to a wall. The one or more antennas may be electrically coupled to the power adapter and communicatively coupled to the at least one processor. Alternatively, a wireless functionality device might include one or more antennas, a power adapter, and at least one processor. The wireless functionality device may be attached to an inner surface of a faceplate configured to be attached to a wall. The one or more antennas of the wireless functionality device may be electrically coupled to the power adapter and communicatively coupled to the at least one processor.
A method is disclosed for testing network devices for networks with a large traffic load utilizing one or more traffic load amplifiers to amplify the traffic load. The load amplifiers connected to the device may receive packets of an initial traffic load, multiply or copy the received packet, alter the destination address information in the header of the copied packets to generate packets with different destination addresses, and transmit the altered packets back to the device for further routing. The altered or copied packets may then be routed via the device back to the load amplifier for further amplification. Through this amplification process, a small initial load of packets may be amplified over and over by the load amplifiers until a target traffic load is achieved at the device to test the device performance at a large traffic load.
H04L 43/0817 - Surveillance ou test en fonction de métriques spécifiques, p.ex. la qualité du service [QoS], la consommation d’énergie ou les paramètres environnementaux en vérifiant la disponibilité en vérifiant le fonctionnement
H04L 47/125 - Prévention de la congestion; Récupération de la congestion en équilibrant la charge, p.ex. par ingénierie de trafic
G06F 9/455 - Dispositions pour exécuter des programmes spécifiques Émulation; Interprétation; Simulation de logiciel, p.ex. virtualisation ou émulation des moteurs d’exécution d’applications ou de systèmes d’exploitation
Embodiments provide system and methods for a DDoS service using a mix of mitigation systems (also called scrubbing centers) and non-mitigation systems. The non-mitigation systems are less expensive and thus can be placed at or near a customer's network resource (e.g., a computer, cluster of computers, or entire network). Under normal conditions, traffic for a customer's resource can go through a mitigation system or a non-mitigation system. When an attack is detected, traffic that would have otherwise gone through a non-mitigation system is re-routed to a mitigation system. Thus, the non-mitigation systems can be used to reduce latency and provide more efficient access to the customer's network resource during normal conditions. Since the non-mitigation servers are not equipped to respond to an attack, the non-mitigation systems are not used during an attack, thereby still providing protection to the customer network resource using the mitigation systems.
In an embodiment, a computer implemented method receives flow data for one or more flows that correspond to a device-circuit pair. The method calculates a time difference for each flow that corresponds to a device-circuit pair. Based on the calculated time differences and the received flow data, the method updates a probability distribution model associated with the device-circuit pair. Then, the method determines whether a time bucket is complete or open based on the updated probability distribution model.
A dynamic SRMS (DSRMS) in a MPLS network generates unique segment identifiers for nodes of the network lacking segment identifiers (SIDs). The DSRMS receives network information from other nodes of the network that may include, for example, Internal Gateway Protocol (IGP) routing information, advertised prefix values for the nodes, and label values used in MPLS routing. The DSRMS analyzes the information and identifies nodes of the network that are not associated with a SID. For each identified node, the DSRMS generates a unique SID and then announces the SID to other nodes within the network. Generating the unique SID may include executing a hashing function using the IP address of the identified node as an input.
H04L 45/50 - Routage ou recherche de routes de paquets dans les réseaux de commutation de données utilisant l'échange d'étiquettes, p.ex. des commutateurs d'étiquette multi protocole [MPLS]
H04L 61/5007 - Adresses de protocole Internet [IP]
H04L 65/65 - Protocoles de diffusion en flux de paquets multimédias, p.ex. protocole de transport en temps réel [RTP] ou protocole de commande en temps réel [RTCP]
39.
METHOD AND SYSTEM FOR MANAGING ROUTING ACROSS MULTIPLE NETWORKS WITH SEPARATE ROUTING MASTERS
Novel tools and techniques are provided for implementing management of routing across multiple voice or data networks with separate routing masters. In various embodiments, in response to receiving a request to establish a call between a calling party in a first network and a called party in a second network, a computing system might receive a first set of network information from a first routing database(s) that is operated by a first service provider and a second set of network information from a second routing database(s) that is operated by a second service provider separate from the first service provider; might analyze the received first and second sets of network information to generate a unified routing model for optimizing routing of the call through the first and second networks; and might establish the call through a selected optimized route based on the generated unified routing model.
H04M 7/00 - Dispositions d'interconnexion entre centres de commutation
H04L 45/302 - Détermination de la route basée sur la qualité de service [QoS] demandée
H04M 7/12 - Dispositions d'interconnexion entre centres de commutation pour l'exploitation entre centraux comportant différents types d'équipement de commutation, p.ex. à entraînement mécanique et pas à pas ou décimal et non décimal
H04L 45/12 - Routage ou recherche de routes de paquets dans les réseaux de commutation de données Évaluation de la route la plus courte
40.
DYNAMIC BORDER GATEWAY PROTOCOL (BGP) HOST ROUTE GENERATION BASED ON DOMAIN NAME SYSTEM (DNS) RESOLUTION
Novel tools and techniques are provided for implementing dynamic border gateway protocol (“BGP”) host route generation based on domain name system (“DNS”) resolution. In various embodiments, a computing system may receive, from a user device via a first network, a request to establish a communications link with an external device via a second network that is separate from the first network, based on a first uniform resource identifier (“URI”) indicative of a network location of the external device. The computing system may query a DNS resolver for an Internet Protocol (“IP”) address corresponding to a valid current IP address, based on the first URI, and may advertise the IP address and/or a route based on the IP address. A communications link may be established between the user device and the external device based on the IP address and/or the route.
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 61/5046 - Résolution des conflits d'allocation d'adresses; Test des adresses
41.
SYSTEM AND METHOD FOR DETERMINING CAPACITY OF A TELECOMMUNICATIONS NETWORK
Aspects of the present disclosure involve systems, methods, computer program products, and the like, for determining an estimated capacity for providing data from a telecommunications network to a plurality of end users. In one implementation, the estimated capacity for delivering the data to the end users is per transmission path or per access network connected to the telecommunications network. This information may be aggregated into a traffic flow table that illustrates the traffic flow and available capacity to one or more end user networks. Through analysis of the traffic flow table, the system determines an estimated available capacity to provide the data to the end users. The traffic flow table thus provides a more accurate estimate of the capacity of the telecommunications network to provide the data to the end users over previous capacity estimates.
Examples described herein relate to apparatuses and methods for a node of a network to facilitate communication among two or more clients, including but not limited to determining, by the node, that the two or more clients are connected to the node for accessing data originating from an origin server, receiving, by the node, a message from a first client of the two or more clients, the message is to be routed to at least one second client of the two or more clients, and sending, by the node, the message to the at least one second client without routing the message to the origin server.
Methods and systems for reducing energy consumption. A method may include aggregating, for a prior time period, prior usage data from a plurality of computing nodes. Based on the aggregated prior usage data from the plurality of computing nodes, a usage threshold for decreasing cooling system output for the plurality of computing nodes and a local-time threshold for decreasing the cooling system output for the plurality of computing nodes are determined. Current usage data for the plurality of computing nodes is then received. When the current usage data reaches the usage threshold and the local time is after the local-time threshold, output of the cooling systems of the plurality of computing nodes is decreased.
G06F 1/324 - Gestion de l’alimentation, c. à d. passage en mode d’économie d’énergie amorcé par événements Économie d’énergie caractérisée par l'action entreprise par réduction de la fréquence d’horloge
G06F 1/3234 - Gestion de l’alimentation, c. à d. passage en mode d’économie d’énergie amorcé par événements Économie d’énergie caractérisée par l'action entreprise
44.
WEB SERVICE-BASED MONITORING AND DETECTION OF FRAUDULENT OR UNAUTHORIZED USE OF CALLING SERVICE
Novel tools and techniques are provided for implementing web-based monitoring and detection of fraudulent or unauthorized use of voice calling service. In various embodiments, a computing system might receive, from a user device associated with an originating party, a request to initiate a call session with a destination party, the request comprising user information associated with the originating party and a destination number associated with the destination party; might query a database with session data (including user information) to access permission data and configuration data; and might configure fraud logic using received configuration data from the database. The computing system might analyze the session data and permission data using the configured fraud logic to determine whether the originating party is permitted to establish the requested call session with the destination party; if so, might initiate one or more first actions; and, if not, might initiate one or more second actions.
A computer-implemented method on a device. The device has hardware including storage. The method includes obtaining log event data from at least one component or service on the device that is to be delivered to a component or service on a distinct device. Each log event data item has a priority. If a connection to an external location is lost, at least some of the log event data items are selectively stored in the storage, wherein the storing is based on priority of the log event data items. Otherwise, if the connection is not lost, at least some of the log event data items are sent to the at least one external location.
H04L 43/0811 - Surveillance ou test en fonction de métriques spécifiques, p.ex. la qualité du service [QoS], la consommation d’énergie ou les paramètres environnementaux en vérifiant la disponibilité en vérifiant la connectivité
46.
PREDICTIVE LOAD MITIGATION AND CONTROL IN A CONTENT DELIVERY NETWORK (CDN)
A computer-implemented method, in a content delivery (CD) network that delivers content on behalf of multiple content providers. The method includes, at a server in the CDN, wherein the server is currently processing at least one other request in at least one other session: receiving a connection request from a client, the connection request being associated with a corresponding content request; determining whether handling the content request will cause the server to become overloaded; and, based on the determining in (B) and on information about the content request, conditionally (i) accepting the content request, and (ii) terminating or throttling at least one session on the server.
H04L 67/1008 - Sélection du serveur pour la répartition de charge basée sur les paramètres des serveurs, p.ex. la mémoire disponible ou la charge de travail
H04L 67/1012 - Sélection du serveur pour la répartition de charge basée sur la conformité des exigences ou des conditions avec les ressources de serveur disponibles
H04L 67/1031 - Commande du fonctionnement des serveurs par un répartiteur de charge, p.ex. en ajoutant ou en supprimant de serveurs qui servent des requêtes
H04L 67/61 - Ordonnancement ou organisation du service des demandes d'application, p.ex. demandes de transmission de données d'application en utilisant l'analyse et l'optimisation des ressources réseau requises en tenant compte de la qualité de service [QoS] ou des exigences de priorité
47.
TIERED UPDATING OF CONFIGURATION DATA IN A CONTENT DELIVERY NETWORK
Examples described herein relate to systems and methods for tiered updating of configuration data. Updated configuration data is transmitted to different tiers of nodes. The nodes of a first tier are commanded to use the updated configuration data. After waiting to see if any nodes of the first tier communicate a fault after using the updated configuration data, for each of the additional tiers in the CDN it is sequentially repeated to: transmit a command to the nodes of that additional tier to use the updated configuration data; and after waiting to see if any nodes of any tier communicate a fault after using the updated configuration data, transmitting a command to the nodes of another additional tier to use the updated configuration data.
H04L 41/0816 - Réglages de configuration caractérisés par les conditions déclenchant un changement de paramètres la condition étant une adaptation, p.ex. en réponse aux événements dans le réseau
H04L 41/0893 - Affectation de groupes logiques aux éléments de réseau
H04L 41/0896 - Gestion de la bande passante ou de la capacité des réseaux, c. à d. augmentation ou diminution automatique des capacités
H04L 41/12 - Découverte ou gestion des topologies de réseau
48.
EFFICIENT PROVISIONING OF INTERNET CIRCUIT AND SECURE DOMAIN NAME SYSTEM
The present application describes systems and methods for automatically provisioning a domain name system (DNS) firewall service for an Internet circuit. In examples, customer premises equipment and a DNS firewall system are automatically configured to work with the Internet circuit without requiring technical knowledge or intervention by a customer.
H04L 41/00 - Dispositions pour la maintenance, l’administration ou la gestion des réseaux de commutation de données, p.ex. des réseaux de commutation de paquets
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
49.
SECURE NETWORK DEVICE MANAGEMENT IN A TELECOMMUNICATIONS NETWORK
A secure network device management system and method include monitoring and validating commands to network devices before such commands are executed. The security system accumulates inputs from a network device intended for display on a terminal and provided by the network device in response to inputs from the terminal and received by the network device. When a control input to execute the command is received from the terminal, the security system reproduces the command from the accumulated inputs and compares the reproduced command to a command list to determine whether the command is authorized. If so, the security system provides the control input to the network device such that the network device executes the command. Otherwise, the security system may delete the command and transmit an alert to the terminal.
H04L 41/069 - Gestion des fautes, des événements, des alarmes ou des notifications en utilisant des journaux de notifications; Post-traitement des notifications
Novel tools and techniques are provided for implementing network service ordering and provisioning of secure access service edge (“SASE”) software packages. In various embodiments, a computing system may provide a user experience (“UX”) platform for a customer portal, the UX platform being accessible by a user via a user device over a first network(s); may provide, via the UX platform, options to configure, via the customer portal, one or more SASE-based network services among a plurality of network services provided by a service provider; and may autonomously orchestrate deployment and configuration of the one or more SASE-based network services via one or more customer premises equipment (“CPE”) that are associated with the user or to an entity with which the user is associated, over a second network(s), based at least in part on user selection of at least one option to configure the one or more SASE-based network services.
The present application describes systems and methods for automatically provisioning a domain name system (DNS) firewall service for an Internet circuit. In examples, customer premises equipment and a DNS firewall system are automatically configured to work with the Internet circuit without requiring technical knowledge or intervention by a customer.
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
52.
CONTAINING A FAULTY STIMULUS IN A CONTENT DELIVERY NETWORK
Examples described herein relate to systems and methods for containing a faulty stimulus. A computer-implemented method may include listing in a suspect list every received stimulus including the faulty stimulus, and implicitly testing the stimuli by respectively acting upon those stimuli by a software application. Responsive to successfully acting upon each of the stimuli besides the faulty stimulus, each non-faulty stimulus is deleted from the suspect list and, responsive to such deletion, made available to a downstream node. Responsive to acting upon the faulty stimulus, the software application crashes which leaves the faulty stimulus listed in the suspect list. The software application then restarts and deems the faulty stimulus as being faulty based upon the faulty stimulus still being listed in the suspect list after the restart.
H04L 41/0695 - Gestion des fautes, des événements, des alarmes ou des notifications le dispositif défectueux étant le système de maintenance, d'administration ou de gestion
H04L 41/069 - Gestion des fautes, des événements, des alarmes ou des notifications en utilisant des journaux de notifications; Post-traitement des notifications
H04L 67/12 - Protocoles spécialement adaptés aux environnements propriétaires ou de mise en réseau pour un usage spécial, p.ex. les réseaux médicaux, les réseaux de capteurs, les réseaux dans les véhicules ou les réseaux de mesure à distance
H04L 69/40 - Dispositions, protocoles ou services de réseau indépendants de la charge utile de l'application et non couverts dans un des autres groupes de la présente sous-classe pour se remettre d'une défaillance d'une instance de protocole ou d'une entité, p.ex. protocoles de redondance de service, état de redondance de protocole ou redirection de service de protocole
53.
SYSTEMS AND METHODS FOR AUTOMATED VERIFICATION AND RECONFIGURATION OF DISCONNECTED NETWORK DEVICES
Systems and methods of disconnecting a network service provided over a network service path include using a computing device that obtains a service identifier assigned to network service and identifies a port of a network device included in a network service path associated with the service. The computing device transmits a request to the network device for port configuration data of the network device and based on the received port configuration data, determines whether the port is assigned to the network service. If so, the computing devices executes a remediation operation which includes transmitting a reconfiguration command to the network device that is adapted to cause the network device to update the port configuration data to free the port.
H04L 41/5054 - Déploiement automatique des services déclenchés par le gestionnaire de service, p.ex. la mise en œuvre du service par configuration automatique des composants réseau
H04L 41/0659 - Gestion des fautes, des événements, des alarmes ou des notifications en utilisant la reprise sur incident de réseau en isolant ou en reconfigurant les entités défectueuses
A content delivery method, and related apparatus, that involves the operations of receiving a request for a content resource including at least one embedded resource with a tag. Upon identification of the tag, using at least one delivery parameter to generate a modified embedded resource. Embedding the modified embedded resource in a content resource, such as an HTML document. Delivering, such as in response to request from a browser, the content resource with the modified embedded resource.
H04L 67/02 - Protocoles basés sur la technologie du Web, p.ex. protocole de transfert hypertexte [HTTP]
G06F 16/48 - Recherche caractérisée par l’utilisation de métadonnées, p.ex. de métadonnées ne provenant pas du contenu ou de métadonnées générées manuellement
G06F 16/955 - Recherche dans le Web utilisant des identifiants d’information, p.ex. des localisateurs uniformisés de ressources [uniform resource locators - URL]
H04L 67/1021 - Sélection du serveur pour la répartition de charge basée sur la localisation du client ou du serveur
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
55.
SYSTEMS AND METHODS FOR CONFIGURATION OF SEQUENCE HANDLERS
A method for registering a handler in a configured sequence of handlers includes: receiving, by a processor and memory implementing a sequencer infrastructure, a configuration script defining a sequence including one or more handler identifiers and corresponding one or more handler arguments; invoking a handler initialization entry point for a handler corresponding to a handler identifier, the invoking the handler initialization entry point including: selecting, based on the corresponding one or more handler arguments, a handler type from among two or more of: a configured instance of the handler; a configured alternate handler different from the handler; an alternate sequence of handlers; an expression; and a no-op handler; and initializing a configured handler based on the handler type selected and the corresponding one or more handler arguments; and adding the configured handler to a configured sequence of handlers.
An identity and access management system including: a processor; and memory including instructions that, when executed by the processor, cause the processor to: receive an API token request for an authorization token to authorize an application function associated with a target API of an application; determine identity information from the API token request; retrieve attributes associated with the identity information; identify the target API and an API function profile associated with the target API for the application function; filter the attributes associated with the identity information based on the API function profile; generate the authorization token according to the filtered attributes; and transmit the authorization token in response to the API token request.
An identity and access management system including: a processor; and memory including instructions that, when executed by the processor, cause the processor to: receive an API token request for an authorization token to authorize an application function associated with a target API of an application; determine identity information from the API token request; retrieve attributes associated with the identity information; identify the target API and an API function profile associated with the target API for the application function; filter the attributes associated with the identity information based on the API function profile; generate the authorization token according to the filtered attributes; and transmit the authorization token in response to the API token request.
Examples described herein relate to standardizing content requests and responses in a content delivery network (CDN). An edge node receives a control object including sets of instructions each implementing portions of a customer’s business logic. The edge node may receive, from a client, a content request identifying a content item, and may apply a set of the instructions which causes the edge node to (i) determine whether any changes are needed for the benefit of a cache server and whether any changes are need for the benefit of an origin server, and (ii) generate a processed client request identifying the content item and including, if needed, any changes for the benefit of the cache server and the origin server. The edge node transmits the processed client request to the cache server, receives a response from the cache server, and transmits a processed client response to the client.
A computer-implemented method, operable on a device in a content delivery network (CDN), wherein the CDN delivers content on behalf of at least one content provider, the device implementing a content delivery (CD) service, the method includes, by the service on the device: receiving a request for a particular resource from a client; determining whether the client includes an optimization support mechanism; when the client includes an optimization support mechanism, providing the client with a first version of the particular resource, optimized, at least in part, for the capabilities of the client in combination with the optimization support mechanism; otherwise providing the client with either (i) an un-optimized version of the particular resource, or (ii) a version of the particular resource optimized, at least in part, for the capabilities of the client without the capabilities of the optimization support mechanism.
H04L 67/02 - Protocoles basés sur la technologie du Web, p.ex. protocole de transfert hypertexte [HTTP]
H04L 67/1097 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour le stockage distribué de données dans des réseaux, p.ex. dispositions de transport pour le système de fichiers réseau [NFS], réseaux de stockage [SAN] ou stockage en réseau [NAS]
60.
STITCHING LABEL-SWITCHED PATHS BETWEEN AUTONOMOUS SYSTEMS WITH INTERNET PROTOCOL
Systems and methods for routing traffic through a network along Label-Switched Paths (LSPs) that may extend across multiple autonomous systems include performing Internet Protocol (IP) routing lookups as a packet is transmitted along the LSP. In one implementation, a packet having a predetermined value (which may be inserted by an upstream network device) is received at a network device after travelling along a first segment of an LSP. In response to identifying the predetermined label value of the packet, the network device may perform an IP routing lookup using IP routing information included in the packet to identify a next hop for the packet. The network device may then update a label of the packet such that the packet is routed along a second segment of the LSP and transmit the communication packet to the next hop.
H04L 45/50 - Routage ou recherche de routes de paquets dans les réseaux de commutation de données utilisant l'échange d'étiquettes, p.ex. des commutateurs d'étiquette multi protocole [MPLS]
H04L 45/02 - Mise à jour ou découverte de topologie
H04L 45/745 - Recherche de table d'adresses; Filtrage d'adresses
61.
SYSTEMS AND METHODS FOR COMMUNICATIONS NODE UPGRADE AND SELECTION
Implementations described and claimed herein provide systems and methods for intelligent node type selection in a telecommunications network. In one implementation, a customer set is obtained for a communications node in the telecommunications network. The customer set includes an existing customer set and a new customer set. A set of customer events is generated for a node type of the communications node using a simulator. The set of customer events is generated by simulating the customer set over time through a discrete event simulation. An impact of the customer events is modeled for the node type of the communications node. The node type is identified from a plurality of node types for a telecommunications build based on the impact of the customer events for the node type.
H04W 64/00 - Localisation d'utilisateurs ou de terminaux pour la gestion du réseau, p.ex. gestion de la mobilité
H04L 12/28 - Réseaux de données à commutation caractérisés par la configuration des liaisons, p.ex. réseaux locaux [LAN Local Area Networks] ou réseaux étendus [WAN Wide Area Networks]
H04L 41/16 - Dispositions pour la maintenance, l’administration ou la gestion des réseaux de commutation de données, p.ex. des réseaux de commutation de paquets en utilisant l'apprentissage automatique ou l'intelligence artificielle
G06Q 10/04 - Prévision ou optimisation spécialement adaptées à des fins administratives ou de gestion, p. ex. programmation linéaire ou "problème d’optimisation des stocks"
H04W 24/06 - Réalisation de tests en trafic simulé
A security platform of a data network is provided that includes security services for computing devices in communication with the data network. The security platform may apply a security policy to the computing devices when accessing the Internet via a home network (or other customer network) and when accessing the Internet via a public or third party network. To provide security services to computing devices via the home network, the security platform may communicate with a security agent application executed on the router (or other gateway device) of the home network. In addition, each of the devices identified by the security profile for the home network may be instructed or otherwise be provided a security agent application for execution on the computing devices. The security agent application may communicate with the security platform when the computing device connects to the Internet over a third party or public access point.
Aspects of the present disclosure involve systems, methods, for encoding a firewall ruleset into one or more bit arrays for fast determination of processing of a received communication packet by a firewall device associated with a network. Through this bitmap, a number of computation operations needed to determine a processing rule for a received packet is significantly reduced compared to the traditional approach of using a hash or a longest prefix match technique. Rather, determining a processing rule for a received packet may include determining a bit value within one or more arrays. In one implementation, a firewall rule may be encoded into a 64-bit array of bit values in which each bit of the array corresponds to a particular processing rule for a particular network address. The firewall rule may be encoded into a bitmap array of bit values by asserting a particular bit within the array.
Implementations described and claimed herein provide systems and methods for intelligent node type selection in a telecommunications network. In one implementation, a customer set is obtained for a communications node in the telecommunications network. The customer set includes an existing customer set and a new customer set. A set of customer events is generated for a node type of the communications node using a simulator. The set of customer events is generated by simulating the customer set over time through a discrete event simulation. An impact of the customer events is modeled for the node type of the communications node. The node type is identified from a plurality of node types for a telecommunications build based on the impact of the customer events for the node type.
H04W 24/02 - Dispositions pour optimiser l'état de fonctionnement
H04W 64/00 - Localisation d'utilisateurs ou de terminaux pour la gestion du réseau, p.ex. gestion de la mobilité
H04L 12/28 - Réseaux de données à commutation caractérisés par la configuration des liaisons, p.ex. réseaux locaux [LAN Local Area Networks] ou réseaux étendus [WAN Wide Area Networks]
H04L 41/12 - Découverte ou gestion des topologies de réseau
H04L 41/16 - Dispositions pour la maintenance, l’administration ou la gestion des réseaux de commutation de données, p.ex. des réseaux de commutation de paquets en utilisant l'apprentissage automatique ou l'intelligence artificielle
G06Q 10/04 - Prévision ou optimisation spécialement adaptées à des fins administratives ou de gestion, p. ex. programmation linéaire ou "problème d’optimisation des stocks"
65.
MONITORING AND DETECTION OF FRAUDULENT OR UNAUTHORIZED USE IN TELEPHONE CONFERENCING SYSTEMS OR VOICE NETWORKS
Novel tools and techniques are provided for implementing monitoring and detection of fraudulent or unauthorized use in telephone conferencing systems or voice networks. In various embodiments, a computing system might monitor call activity through telephone conferencing system or voice network. In response to detecting use of the telephone conferencing system or voice network by at least one party based on the monitored call activity, the computing system might identify incoming and/or outgoing associated with a call initiated by the at least one party. The computing system might analyze the identified incoming and/or outgoing call data to determine whether the call initiated by the at least one party constitutes at least one of fraudulent use or unauthorized use of the telephone conferencing system or voice network. If so, the computing system might initiate one or more first actions.
Novel tools and techniques are provided for implementing name-based routing through networks. In various embodiments, a broker manager in each of a plurality of networks may receive a subscription request for a network device from a client device, each device being locally accessible or disposed in an upstream or downstream network. The broker manager uses its client broker to communicate with a locally accessible client device, and uses its mediator broker (and, sometimes, an intermediate device(s)) to communicate with a locally accessible network device. The broker manager otherwise uses its messaging brokers to communicate with control channels of one or more networks. Once subscription with the network device has been established, any commands and responses between the client device and the network device may be routed over pub/sub channels via the broker managers and their brokers using name-based routing, without routing based on IP address of the network device.
Systems and methods for managing network devices include performing clustering operations for network devices based on attributes of the network devices. By comparing the results of subsequent clustering operations, changes in network device attributes can be readily identified and any network devices for which attributes have changed may be subject to further investigation or remedial action (e.g., blocking traffic to/from the network device). Clustering may also be used to conduct an inventory of network devices by identifying groups of network devices that have similar attributes.
H04L 41/142 - Analyse ou conception de réseau en utilisant des méthodes statistiques ou mathématiques
H04L 41/082 - Réglages de configuration caractérisés par les conditions déclenchant un changement de paramètres la condition étant des mises à jour ou des mises à niveau des fonctionnalités réseau
H04L 41/0893 - Affectation de groupes logiques aux éléments de réseau
H04L 41/069 - Gestion des fautes, des événements, des alarmes ou des notifications en utilisant des journaux de notifications; Post-traitement des notifications
H04L 41/0853 - Récupération de la configuration du réseau; Suivi de l’historique de configuration du réseau en recueillant activement des informations de configuration ou en sauvegardant les informations de configuration
H04L 41/0681 - Configuration des conditions de déclenchement
H04L 45/122 - Routage ou recherche de routes de paquets dans les réseaux de commutation de données Évaluation de la route la plus courte en minimisant les distances, p.ex. en sélectionnant une route avec un nombre minimal de sauts
External customer data (ECD) may be efficiently stored in a network. When ECD is received at an edge node, the node may determine if the ECD is subject to a compiling procedure. For example, if the ECD comprises a list of entries that all have the same data type, the ECD may be placed into an array, and the array may be sorted and stored. In other examples, if the ECD received at a node includes references to other ECD, the referenced ECD may be retrieved, and the received ECD and referenced ECD may be combined and stored. In other examples, the ECD received at the node may be script instructions that can then be compiled into, and stored as, a runtime version. Any compiled ECD stored at nodes may be subject to the same invalidation and expiration policies as the uncompiled ECD from which it was derived.
External customer data (ECD) may be efficiently stored in a network. When ECD is received at an edge node, the node may determine if the ECD is subject to a compiling procedure. For example, if the ECD comprises a list of entries that all have the same data type, the ECD may be placed into an array, and the array may be sorted and stored. In other examples, if the ECD received at a node includes references to other ECD, the referenced ECD may be retrieved, and the received ECD and referenced ECD may be combined and stored. In other examples, the ECD received at the node may be script instructions that can then be compiled into, and stored as, a runtime version. Any compiled ECD stored at nodes may be subject to the same invalidation and expiration policies as the uncompiled ECD from which it was derived.
The present application describes a system and method for passively collecting DNS traffic data as that data is passed between a recursive DNS resolver and an authoritative DNS server. The information contained in the collected DNS traffic data is used to generate a virtual authoritative DNS server, or a zone associated with the authoritative DNS server, when it is determined that the authoritative DNS server has been compromised.
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
Systems and methods for implementing filters within computer networks include obtaining blocklist data that includes blocklist entries for a network. Each of the blocklist entries includes one or more network traffic attributes for identifying traffic to be blocked. In response to receiving the blocklist data, a filter based on a common network traffic attribute shared between at least two of the plurality of blocklist entries is generated. The filter is then deployed to a network device within the network such that the filter may be implemented at the network device to block corresponding traffic.
H04L 43/028 - Capture des données de surveillance en filtrant
H04L 41/0816 - Réglages de configuration caractérisés par les conditions déclenchant un changement de paramètres la condition étant une adaptation, p.ex. en réponse aux événements dans le réseau
H04L 67/10 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 61/5007 - Adresses de protocole Internet [IP]
73.
Concurrent collaboration conference port management
Aspects of the present disclosure involve systems and methods for a collaboration conferencing system to track a total number of concurrently utilized ports across any number of conferencing bridges of the network for a particular customer and one or more billing actions may occur based on this tracking. This may result in an alternate billing option for the customer's use of the system. Further, a telecommunications network administrator may provide access to the collaboration conferencing system based on a total number of concurrently utilized ports rather than on a per conference or per minute basis. With the information of the number of purchased ports by the customer, the administrator may more accurately predict an available capacity for the collaboration conferencing system needed to support all of the users of the system and the potential collaboration conferences.
An automatic provisioning and configuration system for threat mitigation may be provided. Hardware and software resources may be automatically configured to designate a return path for forwarding clean data packets to a target network. A return path from a scrubbing center to the target network may be selected and configured, for example, based on the geographic location of the scrubbing center and information regarding available capacity of the return path to the target network, among other information. The system may also perform a set of dynamic checks to determine whether one or more scrubbing centers have capacity (and/or are likely to continue to have capacity) to provide an encapsulation tunnel between the scrubbing center and the target network for clean return traffic.
An automatic provisioning and configuration system for threat mitigation may be provided. Hardware and software resources may be automatically configured to designate a return path for forwarding clean data packets to a target network. A return path from a scrubbing center to the target network may be selected and configured, for example, based on the geographic location of the scrubbing center and information regarding available capacity of the return path to the target network, among other information. The system may provide for selection a list of Internet circuits already used by the customer. The system may also perform a set of dynamic checks to determine whether one or more of the Internet circuits are eligible for use for the return traffic.
Provided is a content delivery method and architecture for ways to improve the caching of content at one or more content providing devices of a Content Delivery Network (CDN). In particular, systems and methods are disclosed that vary the requirements to store resources or content within a caching device using a dynamic popularity threshold. This popularity threshold may be varied based on a measured fullness of the storage capacity of the cache device. In another example, the dynamic popularity threshold may be further varied based on a cache pressure, which is an indication of how often the cache replaces stored items with new items. The adjustment to the popularity threshold for caching particular content at the caching device may thus be based on a number of requests for content received at the device to tune the caching procedure for a particular region of the CDN.
H04L 67/5681 - Pré-extraction ou pré-livraison de données en fonction des caractéristiques du réseau
H04L 67/561 - Ajout de données fonctionnelles à l’application ou de données de commande de l’application, p.ex. métadonnées
H04L 67/564 - Amélioration de la commande des applications basée sur des données interceptées des applications
H04L 67/568 - Stockage temporaire des données à un stade intermédiaire, p.ex. par mise en antémémoire
H04L 67/289 - Traitement intermédiaire fonctionnellement situé à proximité de l'application consommatrice de données, p.ex. dans la même machine, dans le même domicile ou dans le même sous-réseau
77.
SYSTEMS, METHODS, AND STORAGE MEDIA FOR TESTING LOCAL LOOPS OF TELECOMMUNICATIONS NETWORKS
Automatic testing/analysis of local loops of telecommunications networks includes obtaining bits-per-tone data for a local loop of a telecommunications network and generating a bit value string from the bits-per-tone data. The bit value string is then analyzed to determine whether it includes a bit pattern indicative of an impairment of the local loop. Further approaches for automatically testing local loops of telecommunications networks include obtaining attenuation data for multiple tones carried by the local loop and determining whether the attenuation data falls below thresholds for providing a service using the local loop.
Implementations described and claimed herein provide systems and methods for serving content over a network. In one implementation, a method of serving content is provided. The method includes maintaining a first address record associated with serving a resource and a second address record associated with serving the same resource. The first address record is further associated with a first protocol for a first device capable of serving the resource. Similarly, the second address record is associated with a second protocol, different from the first protocol, for a second device, distinct from the first device, capable of serving the resource. The method further includes providing, in response to at least one resolution request for the resource, the first address record and the second address record.
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 69/18 - Gestionnaires multi-protocoles, p.ex. dispositifs uniques capables de gérer plusieurs protocoles
H04L 69/167 - Adaptation pour la transition entre deux versions IP, p.ex. entre IPv4 et IPv6
H04L 67/1001 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour accéder à un serveur parmi une pluralité de serveurs répliqués
79.
SERVICE AREA DETERMINATION IN A TELECOMMUNICATIONS NETWORK
Implementations described and claimed herein provide systems and methods for correlating one or more service areas of a network with one or more geolocation coordinates to determine available services for customers to the network. A service polygon may be generated that define an area in which a particular service offered by a communications network is available. The boundaries of the service polygons may be adjusted based on information corresponding to physical features of the initial area. The service polygons may aid a communications network in providing a list of available services to potential customers or devices connected to the network by determining one or more geolocation coordinate values of a potential connection site and comparing the values to the service polygons. A network management system may determine the available services, current or in the future, to offer such services to a customer to the network.
In an embodiment, a method monitors a plurality of data streams passing through a router in the connectivity service provider environment, and for each of the data streams, periodically samples packets at the router. The method further generates a stream signature based at least on the payload of the sampled packets. The method further includes, for each generated stream signature, attaching information to the stream signature. Such information may, for example, include time-stamp information for the stream signature, or an identification of the router. The method may further comprise storing the stream signatures corresponding to the data streams in a database. The stored stream signatures may be compared to determine matching stream signatures. Matching signatures may identify data streams that carry identical or similar content.
Examples of the present disclosure describe systems and methods relating to adaptive virtual services. In an example, a user specifies a device configuration for a platform device. As a result, a service provider installs selected virtual-network functions and defines network connections as specified by the device configuration. Management software may also be installed, thereby enabling the service provider to communicate with and remotely manage the platform device. The installed virtual-network functions are activated on the platform device once it is delivered to the user. In some instances, the user changes the device configuration. For example, the user may install new virtual-network functions, reconfigure or remove existing virtual-network functions, or change defined network connections. As a result, the service provider reconfigures the platform device accordingly. Thus, the user need not purchase new specialized hardware in order to change the available functions of the computer network.
G06F 9/455 - Dispositions pour exécuter des programmes spécifiques Émulation; Interprétation; Simulation de logiciel, p.ex. virtualisation ou émulation des moteurs d’exécution d’applications ou de systèmes d’exploitation
82.
Dynamic border gateway protocol (BGP) host route generation based on domain name system (DNS) resolution
Novel tools and techniques are provided for implementing dynamic border gateway protocol (“BGP”) host route generation based on domain name system (“DNS”) resolution. In various embodiments, a computing system may receive, from a user device via a first network, a request to establish a communications link with an external device via a second network that is separate from the first network, based on a first uniform resource identifier (“URI”) indicative of a network location of the external device. The computing system may query a DNS resolver for an Internet Protocol (“IP”) address corresponding to a valid current IP address, based on the first URI, and may advertise the IP address and/or a route based on the IP address. A communications link may be established between the user device and the external device based on the IP address and/or the route.
H04L 61/5046 - Résolution des conflits d'allocation d'adresses; Test des adresses
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
83.
Intent-based orchestration using network parsimony trees
Novel tools and techniques are provided for implementing intent-based orchestration using network parsimony trees. In various embodiments, in response to receiving a request for network services that comprises desired characteristics and performance parameters for the requested network services without information regarding specific hardware, hardware type, location, or network, a computing system might generate a request-based parsimony tree based on the desired characteristics and performance parameters. The computing system might access, from a datastore, a plurality of network-based parsimony trees that are each generated based on measured network metrics, might compare the request-based parsimony tree with each of one or more network-based parsimony trees to determine a fitness score for each network-based parsimony tree, and might identify a best-fit network-based parsimony tree based on the fitness scores. The computing system might identify and might allocate network resources based on the identified best-fit network-based parsimony tree, for providing the requested network services.
H04L 41/0816 - Réglages de configuration caractérisés par les conditions déclenchant un changement de paramètres la condition étant une adaptation, p.ex. en réponse aux événements dans le réseau
H04L 41/5009 - Détermination des paramètres de rendement du niveau de service ou violations des contrats de niveau de service, p.ex. violations du temps de réponse convenu ou du temps moyen entre l’échec [MTBF]
H04L 41/5019 - Pratiques de respect de l’accord du niveau de service
H04L 47/762 - Contrôle d'admission; Allocation des ressources en utilisant l'allocation dynamique des ressources, p.ex. renégociation en cours d'appel sur requête de l'utilisateur ou sur requête du réseau en réponse à des changements dans les conditions du réseau déclenchée par le réseau
H04L 47/70 - Contrôle d'admission; Allocation des ressources
H04L 43/045 - Traitement des données de surveillance capturées, p.ex. pour la génération de fichiers journaux pour la visualisation graphique des données de surveillance
H04L 41/5054 - Déploiement automatique des services déclenchés par le gestionnaire de service, p.ex. la mise en œuvre du service par configuration automatique des composants réseau
H04L 67/51 - Découverte ou gestion de ceux-ci, p.ex. protocole de localisation de service [SLP] ou services du Web
84.
SYSTEM AND METHOD FOR MANAGING VIRTUAL LOCAL AREA NETWORKS
A method for identifying VLANs associated with a network includes gathering actual network element configuration data from a plurality of network elements in the network, wherein the actual network element configuration data identifies one or more VLANs that at least some of the plurality of network elements are actually allocated to; correlating the actual network element configuration data with administrative VLAN data; and determining one or more VLANs that are not commonly identified in both the actual network element configuration data and the administrative VLAN data. A system includes a network monitoring system operable to gather actual network element configuration data from a plurality of network elements at one or more logical network sites, wherein the actual network element configuration data identifies one or more VLANs that at least some of the plurality of network elements are actually allocated to; and a VLAN services module operable to correlate the actual network element configuration data with administrative VLAN data, and further operable to determine one or more VLANs that are not commonly identified in both the actual network element configuration data and the administrative VLAN data.
H04L 41/0853 - Récupération de la configuration du réseau; Suivi de l’historique de configuration du réseau en recueillant activement des informations de configuration ou en sauvegardant les informations de configuration
H04L 41/0859 - Récupération de la configuration du réseau; Suivi de l’historique de configuration du réseau en conservant l'historique des différentes générations de configuration ou en revenant aux versions de configuration précédentes
H04L 41/12 - Découverte ou gestion des topologies de réseau
An optical network including a plurality of gateway nodes interconnected with a plurality of intermediate nodes with segments of fiber. The network includes a plurality of devices, such as reconfigurable optical add drop multiplexers, optimally placed at various nodes throughout the network. The device placement is optimized with an integer linear programming analysis considering span definition such that any given span involves some number of segments not exceeding a number of segments that would require wavelength regeneration, cost of placement of a device at a given node, cost of wavelength regeneration, and various parameters and constraints.
H04L 41/22 - Dispositions pour la maintenance, l’administration ou la gestion des réseaux de commutation de données, p.ex. des réseaux de commutation de paquets comprenant des interfaces utilisateur graphiques spécialement adaptées [GUI]
G06Q 10/063 - Recherche, analyse ou gestion opérationnelles
H04J 14/02 - Systèmes multiplex à division de longueur d'onde
86.
Intelligent attestation of traffic using a routing engine
The present application describes providing an attestation level to a received communication. The attestation level may be used to communicate a level of security to a network or a called party that receives the communication. The attestation level associated with the communication may indicate to a destination network and/or recipient that the phone number associated with the communication is secure and/or the telephone number has not been spoofed.
Examples described herein relate to apparatuses and methods for managing communications within a supercluster or across superclusters, including a first supercluster having a plurality of first machines and a publish-subscribe (Pub-Sub) channel to which each of the plurality of first machines is subscribed. A second supercluster has a plurality of second machines and a bridge between the first supercluster and the second supercluster. A first machine is configured to receive, via the bridge, an availability status and resource allocation information of each second machine and publish, on the Pub-Sub channel of the first supercluster, the availability status and the resource allocation information.
H04L 67/1008 - Sélection du serveur pour la répartition de charge basée sur les paramètres des serveurs, p.ex. la mémoire disponible ou la charge de travail
H04L 67/1014 - Sélection du serveur pour la répartition de charge basée sur le contenu d'une demande
H04L 67/1021 - Sélection du serveur pour la répartition de charge basée sur la localisation du client ou du serveur
H04L 49/201 - Opération de multidiffusion; Opération de diffusion
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 67/562 - Courtage des services de mandataires
H04L 67/563 - Redirection de flux de réseau de données
H04L 67/568 - Stockage temporaire des données à un stade intermédiaire, p.ex. par mise en antémémoire
88.
SYSTEMS AND METHODS FOR PROTECTING COMPUTING SYSTEMS USING DECLARED CONSTRAINTS
Systems and methods for managing configuration changes to a network are provided. In examples, the configuration rules are received and stored in a staging directory. If the configuration rules are validated, the rules are moved to a running directory. Thereafter a request to make a change to a configuration parameter is received. The request may comprise a configuration change object, and the configuration change object may be stored in the staging directory. The configuration change object may be evaluated against the rule (and other rules of the network), and it may be moved to the running directory only after satisfying all applicable rules. In some examples, applying the rule(s) may include determining whether the configuration change exceeds a network limit on changes of a particular type with a preset time period.
Systems, methods, and non-transitory computer-readable storage media which have instructions stored for execution on a processor, for automating the commissioning of a transport network element within a network. A system configured according to this disclosure can be an Automated Commissioning Tool which can initiate communications with a network element on the network. The Automated Commissioning Tool can then retrieve updated firmware corresponding to the network element and configure the network element to have the updated firmware. Finally, the Automated Commissioning Tool can determine, from a network plan, a first port on the network element which is to be connected via a cross-connect to a second port on the network element and establish the cross-connect on the network element. At this point the network element may be commissioned to operate as a transport network element within the network.
H04L 41/08 - Gestion de la configuration des réseaux ou des éléments de réseau
H04L 41/0806 - Réglages de configuration pour la configuration initiale ou l’approvisionnement, p.ex. prêt à l’emploi [plug-and-play]
H04L 41/082 - Réglages de configuration caractérisés par les conditions déclenchant un changement de paramètres la condition étant des mises à jour ou des mises à niveau des fonctionnalités réseau
H04L 67/06 - Protocoles spécialement adaptés au transfert de fichiers, p.ex. protocole de transfert de fichier [FTP]
H04L 41/22 - Dispositions pour la maintenance, l’administration ou la gestion des réseaux de commutation de données, p.ex. des réseaux de commutation de paquets comprenant des interfaces utilisateur graphiques spécialement adaptées [GUI]
H04L 67/10 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau
H04M 3/24 - Dispositions de supervision, de contrôle ou de test avec vérification du fonctionnement normal
A content delivery method including the operations of receiving a uniform resource locator resolution request at an authoritative name server for a domain where the uniform resource resolution request is received based, at least in part, on a host name of the uniform resource resolution request where the host name is uniquely related to a resource associated with the uniform resource resolution request. The method further including the operation of tracking a popularity of the resource based on the host name uniquely related to the resource and providing a location within a network capable of delivering the resource where the provided location is based on the popularity of the resource.
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 47/70 - Contrôle d'admission; Allocation des ressources
H04L 61/30 - Gestion des noms de réseau, p.ex. utilisation d'alias ou de surnoms
H04L 67/02 - Protocoles basés sur la technologie du Web, p.ex. protocole de transfert hypertexte [HTTP]
H04L 67/60 - Ordonnancement ou organisation du service des demandes d'application, p.ex. demandes de transmission de données d'application en utilisant l'analyse et l'optimisation des ressources réseau requises
A node in a content delivery network (CDN) receives a request for content and determines information about the request. When sufficient information about the content is determined, the request is assigned to an appropriate CD service to process the request; and when insufficient information about the content is determined, the request is assigned to a generic CD service to process the request. The generic CD service processes the request; and provides updated information about the content to be used for processing future requests. An appropriate CD service processing a request may also provide updated information about the content to be used for processing future requests.
H04L 67/63 - Ordonnancement ou organisation du service des demandes d'application, p.ex. demandes de transmission de données d'application en utilisant l'analyse et l'optimisation des ressources réseau requises en acheminant une demande de service en fonction du contenu ou du contexte de la demande
H04L 67/02 - Protocoles basés sur la technologie du Web, p.ex. protocole de transfert hypertexte [HTTP]
H04L 67/1097 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour le stockage distribué de données dans des réseaux, p.ex. dispositions de transport pour le système de fichiers réseau [NFS], réseaux de stockage [SAN] ou stockage en réseau [NAS]
In an embodiment, a computer implemented method receives flow data for a network flows. The method extracts a tuple from the flow data and calculates long-term and short-term trends based at least in part on the tuple. The long-term and short-term trends are compared to determine whether a potential network anomaly exists. If a potential network anomaly does exist, the method initiates a heavy hitter detection algorithm. The method forms a low-complexity intermediate stage of processing that enables a high-complexity heavy hitter detection algorithm to execute when heavy hitters are likely to be detected.
H04L 43/062 - Génération de rapports liés au trafic du réseau
H04L 41/147 - Analyse ou conception de réseau pour prédire le comportement du réseau
G06F 21/57 - Certification ou préservation de plates-formes informatiques fiables, p.ex. démarrages ou arrêts sécurisés, suivis de version, contrôles de logiciel système, mises à jour sécurisées ou évaluation de vulnérabilité
H04L 43/026 - Capture des données de surveillance en utilisant l’identification du flux
H04L 41/142 - Analyse ou conception de réseau en utilisant des méthodes statistiques ou mathématiques
93.
METHOD AND APPARATUS FOR TIMEOUT SETTING PROPAGATION
A method and apparatus for managing requests in a computer network. A request for a resource from a first node is received by a second node. The request for a resource comprises a header with a timeout indication corresponding to an amount of time the first node will wait for a response to its request for the resource. The second node sends to the first node a response to the request for the resource prior to the end of the amount of time indicated in the timeout indication. The response to the request comprises either the resource or an error message.
A routing system can provide a Dynamic-Hybrid Forwarding Information Base (DHFIB). A control component of the routing system can build a routing table that includes routing information (e.g., prefixes, addresses, etc.) for use by a first routing component. The routing table can be ordered or ranked based on traffic information from the first routing component. Then, the control component can create the DHFIB from the routing table, wherein the DHFIB is a portion of the routing table and related to the first routing component. As such, the portion of the routing table selected for the DHFIB can be the set of prefixes in the routing table that represent the most frequently routed or most important prefixes in the routing table. Finally, the control component can forward the DHFIB to the first routing component to allow the routing component to route communications.
Systems and methods for network quality testing are provided. Synthetic traffic may be sent through a first flow path and a second flow path. The second flow path includes a portion apportionable to the first flow path, internal to a server, and a portion apportionable to an external flow path, external to the server. Durations of traffic traveling through the first flow path and the second flow path are compared to determine the portion of the second flow path apportionable to the external flow path. In an example, time stamping may be performed by component(s) of the server, such as a kernel, to determine the durations of the traffic traveling through the first flow path and the second flow path.
H04L 43/0817 - Surveillance ou test en fonction de métriques spécifiques, p.ex. la qualité du service [QoS], la consommation d’énergie ou les paramètres environnementaux en vérifiant la disponibilité en vérifiant le fonctionnement
H04L 43/106 - Surveillance active, p.ex. battement de cœur, utilitaire Ping ou trace-route en utilisant des informations liées au temps dans des paquets, p.ex. en ajoutant des horodatages
H04L 43/091 - Surveillance ou test en fonction de métriques spécifiques, p.ex. la qualité du service [QoS], la consommation d’énergie ou les paramètres environnementaux en mesurant la contribution de chaque composant du réseau au niveau du service réel
96.
Packet processing of streaming content in a communications network
Aspects of present disclosure include devices within a transmission path of streamed content forwarding received data packets of the stream to the next device or “hop” in the path prior to buffering the data packet at the device. In this method, typical buffering of the data stream may therefore occur at the destination device for presentation at a consuming device, while the devices along the transmission path may transmit a received packet before buffering. Further, devices along the path may also buffer the content stream after forwarding to fill subsequent requests for dropped data packets of the content stream. Also, in response to receiving the request for the content stream, a device may first transmit a portion of the contents of the gateway buffer to the requesting device to fill a respective buffer at the receiving device.
H04L 41/0806 - Réglages de configuration pour la configuration initiale ou l’approvisionnement, p.ex. prêt à l’emploi [plug-and-play]
H04W 48/08 - Distribution d'informations relatives aux restrictions d'accès ou aux accès, p.ex. distribution de données d'exploration
H04L 67/12 - Protocoles spécialement adaptés aux environnements propriétaires ou de mise en réseau pour un usage spécial, p.ex. les réseaux médicaux, les réseaux de capteurs, les réseaux dans les véhicules ou les réseaux de mesure à distance
H04L 67/5682 - Politiques ou règles de mise à jour, de suppression ou de remplacement des données stockées
H04L 49/25 - Routage ou recherche de route dans une matrice de commutation
H04L 49/9005 - Dispositions de mémoires tampon en utilisant une allocation dynamique de l'espace des mémoires tampon
H04N 21/232 - Opération de récupération de contenu au sein d'un serveur, p.ex. lecture de flux vidéo du réseau de disques
H04N 21/44 - Traitement de flux élémentaires vidéo, p.ex. raccordement d'un clip vidéo récupéré d'un stockage local avec un flux vidéo en entrée ou rendu de scènes selon des graphes de scène MPEG-4
H04N 21/231 - Opération de stockage de contenu, p.ex. mise en mémoire cache de films pour stockage à court terme, réplication de données sur plusieurs serveurs, ou établissement de priorité des données pour l'effacement
H04L 49/9057 - Dispositions facilitant le réassemblage ou le reséquençage des paquets
97.
EXTERNAL INJECTION OF CLOUD BASED NETWORK FUNCTIONS INTO NETWORK SERVICES
Disclosed herein are system, method, and computer program product embodiments for providing an API description of an external network service and using the API to integrate the external service into a network. An embodiment operates by receiving, from a service provider, a description of an application programming interface (API), transmitting a call to the service provider using the API for creating a new instance of a service and transmitting to the service provider a traffic flow upon which the service will be applied.
H04L 67/1095 - Réplication ou mise en miroir des données, p.ex. l’ordonnancement ou le transport pour la synchronisation des données entre les nœuds du réseau
H04L 47/33 - Commande de flux; Commande de la congestion en utilisant le transfert de la notification
H04L 67/53 - Services réseau en utilisant des fournisseurs tiers de services
H04L 67/1001 - Protocoles dans lesquels une application est distribuée parmi les nœuds du réseau pour accéder à un serveur parmi une pluralité de serveurs répliqués
H04L 67/133 - Protocoles pour les appels de procédure à distance [RPC]
H04L 47/24 - Trafic caractérisé par des attributs spécifiques, p.ex. la priorité ou QoS
In an alien wave system, one or more transponders connected to a line system may be owned and operated by a different entity from the entity that owns and operates the line system. In such a situation, diagnosing and correcting faults, and achieving good performance, may be challenging. As such, a system and methods for interoperability in an alien wave system are provided.
H04B 10/079 - Dispositions pour la surveillance ou le test de systèmes de transmission; Dispositions pour la mesure des défauts de systèmes de transmission utilisant un signal en service utilisant des mesures du signal de données
Aspects of the present disclosure involve a CDN utilizing a Direct Server Return (DSR) request command to create a tunnel from one content server to another content server of the CDN. Through the DSR tunnel, a request for content may be served from a content server that is more advantageous for the CDN for any number of reasons, such as from a content server that is logically closer to the content server. In determining when a DSR tunnel is created to provide the content, the CDN may access a database storing various information concerning the CDN, such as the location of egress gateways of the CDN in relation to one or more content servers, connecting network location information, the capabilities of one or more content servers, and/or load information of available content servers.
H04L 67/52 - Services réseau spécialement adaptés à l'emplacement du terminal utilisateur
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 101/69 - Types d'adresses de réseau utilisant des informations géographiques, p.ex. le numéro de la chambre
100.
Systems and methods for processing requests for content of a content distribution network
Improved methods for retrieval of content from CDNs is provided that includes a rendezvous controller that receives information of an identification of content being requested and an estimated location of a content requesting device. Based on this information, the rendezvous system identifies a server within a CDN from which the requested content may be retrieved. The selected server may be based on a repeatable hash function such that the likelihood that the content being requested is cached at the selected server. Steering requests to a server of the CDN which may have the content cached may reduce the number of servers within the CDN with the same cached content, particularly for the highest requested content. The rendezvous system may then return a corresponding domain name associated with the selected server and that can be subsequently submitted to a DNS for resolution to the IP address of the identified server.
H04L 61/4511 - Répertoires de réseau; Correspondance nom-adresse en utilisant des protocoles normalisés d'accès aux répertoires en utilisant le système de noms de domaine [DNS]
H04L 61/5007 - Adresses de protocole Internet [IP]
H04L 67/52 - Services réseau spécialement adaptés à l'emplacement du terminal utilisateur
H04L 67/568 - Stockage temporaire des données à un stade intermédiaire, p.ex. par mise en antémémoire
H04L 9/32 - Dispositions pour les communications secrètes ou protégées; Protocoles réseaux de sécurité comprenant des moyens pour vérifier l'identité ou l'autorisation d'un utilisateur du système