Cisco Technology, Inc.

Karen Cadora

Patrice Brissette

Jiri Chaloupka

Thierry Couture

Clarence Filsfils

Pablo Camarillo Garvia

Ahmed Mohamed Ahmed Abdelsalam

Jason Pfeifer

Suresh Doddagaddavalli Basavarajappa

Massimo Ramella-Pezza

Suresh Basavarajappa

Techniques for a head-end node in one or more network autonomous systems to utilize a protocol to instantiate services on tail-end nodes. The head-end node can use a service request mechanism that is enabled by the protocol to request service instantiation on the tail-end node without a network operator having to manually configure the tail-end node, or even having access to the tail-end node. Additionally, the protocol may provide mechanisms to define handling attributes for traffic of the service (e.g., quality of service (QoS) attributes, Maximum Transmission Unit (MTU) settings, etc.), service acknowledgement mechanisms for the head-end node to determine that the service was instantiated on the tail-end node, and so forth. In this way, a head-end node can be used to instantiate a service on a tail-end node without a network operator having to have direct access to the tail-end node to manually configure the tail-end node.

Source-provisioned services infrastructure

Disclosed are systems, apparatuses, methods, and computer-readable media to measure performance of distinct paths of a network. A method includes determining a collection of hashes of a network based on a network probe event, each hash in the collection of hashes corresponding to a distinct path from a first edge device to a second edge device through the network; transmitting a collection of probes from the first edge device in the network, wherein each probe in the collection of probes is assigned a hash selected from the collection of hashes; receiving probes from the collection of probes at the second edge device; and determining a network performance of each distinct path through the network.

Path assurance in shared transport

System, method, and computer program product to route data communications based on non-routing criteria, by receiving, by a network element, a data packet, identifying, in a routing table of the network element, a first route for routing the data packet, computing, by an application executing on the network element, a routing score for the first route based on one or more non-routing criteria, computing, by the application, a routing score for a second route for routing the data packet based on the one or more non-routing criteria, and upon determining that the routing score for the second route is less than the routing score of the first route, updating the routing table to cause the network element to route the data packet according to the second route.

Supporting arbitrary routing criteria in software defined networks

A method for managing communication requests includes receiving tag information from a user of a communication device, and associating the tag with a communication device. The tag information includes criteria for determining whether the tag applies to an incoming communication request and one or more actions to be taken in response to the communication request after determining that the tag applies. The method further includes receiving a request from a caller for a communication session with the communication device, determining whether criteria for the tag have been met by the communication request, and if the criteria for the tag have been met, taking the specified actions in response to the communication request.

Status messaging using associated phone tags

Growing community of inventors

Boulder, CO, United States of America

Karen Cadora