Patent classifications
H04L45/742
Data packet retransmission processing
Systems and computer program products for performing retransmission of data packets over a network. A node receives a data packet with a source and a destination address. The data packet is sent along a network path to the destination address, and information associated with the data packet is sent to a controller node that is independent of the network path. A controller receives information associated with a data packet from any forwarder node within a plurality of forwarder nodes each monitoring communications along separate communications paths. An indication of a receipt acknowledgement for the data packet is received from a second forwarder node that is separate from the first forwarder node and the controller node. The receipt acknowledgement is correlated with the data packet and based on the correlating, data associated with retransmission processing of the data packet is deleted.
Multicast data packet processing method, and apparatus
A multicast data packet processing method in a point-to-multipoint (P2MP)-based bit index explicit replication (BIER) multicast tree, which includes an intermediate node configured to use P2MP to forward a BIER packet, includes receiving a first multicast data packet with a BIER header having a first label. The method further includes obtaining a first forwarding entry based on the first label. The first forwarding entry includes the first label, a first identifier identifying the multicast tree, and a second identifier instructing to perform P2MP forwarding. The method further includes obtaining, based on the first identifier, a second forwarding entry including the first identifier and a second label. The method further includes obtaining a second multicast data packet based on the second identifier, the second forwarding entry, and the first multicast data packet, and sending the second multicast data packet. The second multicast data packet includes the second label.
SOFTWARE DEFINED NETWORKING WITH EN-ROUTE COMPUTING
Various aspects of methods, systems, and use cases include en-route computing coordination. A method may include receiving a packet including a compute task and context information, identifying a destination node for the packet, and determining a route for the packet to the destination node. The route may include an intermediary node determined based on the context information and available resources at the intermediary node to execute the compute task of the packet at the intermediary node. The method may include forwarding the packet to a next device along the route.
Detection of latency, packet drops, and network hops through a TCP tunnel using ICMP and UDP probes
Techniques for using traceroute with tunnels and cloud-based systems for determining measures of network performance are presented. Systems and methods include receiving a request from a client to perform a reverse trace; requesting a trace to an endpoint that is one of an egress router and a tunnel client, wherein there is a tunnel between i) the destination and ii) the one of the egress router and the tunnel client; receiving a response to the trace; and sending details associated with the response to the client so that the client aggregates these details with details from one or more additional legs to provide an overall view of a service path between the client and the destination.
INFORMATION CENTRIC NETWORK TUNNELING
System and techniques for information centric network tunneling are described herein. At an ICN router, a data handle for data—that includes an indication of security metadata—is received. The security metadata is obtained based on the data handle and the data is cached based on the security metadata. An ICN node at an interface of the ICN router is tested for compatibility with the security metadata and a version of the data is transmitted to the ICN node based on the compatibility of the ICN node with the security metadata.
COMMUNICATION OF POLICY CHANGES IN LISP-BASED SOFTWARE DEFINED NETWORKS
Systems, methods, and computer-readable media for communicating policy changes in a Locator/ID Separation Protocol (LISP) based network deployment include receiving, at a first routing device, a first notification from a map server, the first notification indicating a change in a policy for LISP based communication between at least a first endpoint device and at least a second endpoint device, the first endpoint device being connected to a network fabric through the first routing device and the second endpoint device being connected to the network fabric through a second routing device. The first routing device forwards a second notification to the second routing device if one or more entries of a first map cache implemented by the first routing device are affected by the policy change, the second notification indicating a set of one or more endpoints connected to the second routing device that are affected by the policy change.
Mesh routing of sleepy sensor data
HVAC components having improved efficiency are described. In one embodiment, excessive sleep current draw in a battery-powered device having a microcontroller is detected by measuring a voltage drop across a MOSFET device coupled in a forward-conducting orientation in series between the battery and the microcontroller, causing a transistor to conduct when the voltage drop exceeds a predetermined threshold to generate a first trigger signal, integrating the first trigger signal to generate a second trigger signal, and generating an interrupt to the microcontroller. In another embodiment, a battery-saving method of operating an HVAC component includes maintaining the HVAC device in the sleep mode, receiving a user input to wake the device, transmitting a data request and returning the HVAC component to the sleep mode, waking up the HVAC device to poll an adjacent network node storing a cached response, displaying the response, and returning the HVAC device to sleep.
FLOW CACHE MANAGEMENT
Packet-processing circuitry including one or more flow caches whose contents are managed using a cache-entry replacement policy that is implemented based on one or more updatable counters maintained for each of the cache entries. In an example embodiment, the implemented policy enables the flow cache to effectively catch and keep elephant flows by giving to the caught elephant flows appropriate preference in terms of the cache dwell time, which can beneficially improve the overall cache-hit ratio and/or packet-processing throughput. Some embodiments can be used to implement an Open Virtual Switch (OVS). Some embodiments are advantageously capable of implementing the cache-entry replacement policy with very limited additional memory allocation.
Dynamic inspection of networking dependencies to enhance anomaly detection models in a network assurance service
In one embodiment, a network assurance service that monitors a network detects, using a machine learning-based anomaly detector, network anomalies associated with source nodes in the monitored network. The network assurance service identifies, for each of the detected anomalies, a set of network paths between the source nodes associated with the anomaly and one or more potential destinations of traffic for that source node. The network assurance service correlates networking devices along the network paths in the identified sets of network paths with the detected network anomalies. The network assurance service adjusts the machine learning-based anomaly detector to use a performance measurement for a particular one of the networking devices as an input feature, based on the correlation between the particular networking device and the detected network anomalies.
Facilitating user privacy in communications involving semantic-bearing IPv6 addresses
A message is received which indicates a request for a client-specific service address for service or content provided by a service provider. In response to the request, a client-specific service address may be generated and sent to the client. The address may be used as a destination address in one or more subsequent client requests for service or content. A first portion of the address comprises an IPv6 service prefix assigned to a service network of the service provider. A second portion of the address comprises semantic information having a first portion of encrypted private information and a second portion of unencrypted service information. The encrypted private information may be generated by encrypting private information based on a cryptographic key, where the cryptographic key is derived based on a secret key associated with the service provider and an IP client prefix assigned to the client.