SYSTEM AND METHOD FOR MANAGEMENT OF CLOUD-BASED SYSTEMS

• US 20160043956A1
• Filed: 10/26/2015
• Published: 02/11/2016
• Est. Priority Date: 02/06/2012
• Status: Active Grant

• Current Assignee: Deepfield Networks, Deepfield Networks Inc. (Nokia Corporation)
• Original Assignee: Deepfield Networks
• Inventors: Eggleston, Joseph E., Labovitz, Craig H.
• Granted Patent: US 9,680,757 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5009 Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
• CPC Class Codes: H04L 41/508 based on type of value added network service under agreement
• CPC Class Codes: H04L 43/026 using flow identification
• CPC Class Codes: H04L 43/062 related to network traffic
• CPC Class Codes: H04L 43/0882 Utilisation of link capacity
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

System and method for reporting usage of a network infrastructure includes obtaining a map that includes at least one flow-mapping that correlates a flow feature with a service and that correlates a flow feature with an endpoint type, wherein the endpoint types include at least a subscriber type and a service type; at a first computer, receiving flow telemetry of a network infrastructure, the flow telemetry representing at least the destination and source attributes for network traffic in the flow telemetry; categorizing the flow telemetry into at least a subscriber flow category based on the source and destination endpoint types of the traffic; for subscriber flow telemetry of a subscriber, processing the subscriber flow telemetry into at least one flow feature; identifying at least one service to attribute to at least a portion of the subscriber flow telemetry, the service identified through the processed flow feature and a flow-mapping.

Claims

1. A method for reporting usage of a network infrastructure comprising:

performing by one or more computers;

obtaining a map of a plurality of flow-mappings that each correlates a flow feature with an endpoint type, wherein the endpoint type is a subscriber or a service, wherein a first flow-mapping includes a content delivery network (CDN) component as a flow feature that correlates to a first service, and a second flow-mapping includes a shared CDN component as a flow feature that correlates to at least the first and a second service;

receiving flow telemetry comprising a plurality of destination and source attributes for network traffic of a network infrastructure;

categorizing the flow telemetry into one or more subscriber flows using the map;

selecting the subscriber flow of a subscriber;

attributing at least one of the services to at least a portion of the selected subscriber flow;

identifying the first service to attribute to a first portion of selected subscriber flow; and

if a second portion of the subscriber flow is associated with the first portion of subscriber flow telemetry, identifying the first service to attribute to the second portion of the subscriber flow telemetry.

2. The method of claim 1, wherein the map includes at least one flow-mapping that correlates a domain name to a service and wherein categorizing the flow telemetry comprises:

identifying domain name service (DNS) recursive responses sent to the subscriber in the flow telemetry, a recursive response including at least a domain name query and component address; and

identifying a third portion of the flow telemetry from the subscriber to the component address.

3. The method of claim 2, wherein attributing at least one of the services to at least a portion of the selected subscriber flow comprises:

identifying a service for the third portion of flow telemetry that correlates a domain name of the component address to a service in the selected subscriber flow.

4. The method of claim 1, wherein attributing at least one of the services to the selected subscriber flow telemetry comprises:

tracking combinations of component use as a flow feature.

5. The method of claim 4, wherein possible services are limited through one flow feature and a flow-mapping.

6. The method of claim 4, wherein tracking combinations of component use comprises:

tracking substantially simultaneous component usage by the subscriber, and wherein the identified service is identified through a flow-mapping correlating at least two components of simultaneous usage to a service.

7. The method of claim 4, wherein tracking combinations of component use comprises:

tracking a sequence of component usage by the subscriber, and wherein the identified service is identified through a flow-mapping correlating a sequence of at least two components to a service.

8. The method of claim 4, wherein tracking combinations of component use comprises:

tracking proportions of component usage the subscriber, and wherein the identified service is identified through a flow-mapping correlating a usage proportion ranges of at least two components to a service.

9. The method of claim 4, wherein tracking combinations of component use comprises:

tracking a traffic profile of a component accessed by the subscriber, and limiting possible identified services to services correlated with flow feature of the traffic profile.

10. The method of claim 1, further comprising:

compiling data on services attributed to portions of the flow telemetry; and

rendering the data in service analytics interface.

11. The method of claim 10, wherein obtaining a map comprises:

retrieving component addresses of services, and adding the component addresses to the map as flow features correlated to a service, and at a first client, automating traffic of a first service and adding service components identified in traffic of the first client as flow features correlated to the first service in the map.

12. The method of claim 1, wherein a particular flow feature in the map is one or more Internet Protocol (IP) addresses.

13. The method of claim 1, further comprising:

consolidating duplicate flow telemetry of the subscriber.

14. A system comprising:

one or more computers programmed to perform operations comprising;

obtaining a map of a plurality of flow-mappings that each correlates a flow feature with an endpoint type, wherein the endpoint type is a subscriber or a service, wherein a first flow-mapping includes a content delivery network (CDN) component as a flow feature that correlates to a first service, and a second flow-mapping includes a shared CDN component as a flow feature that correlates to at least the first and a second service;

receiving flow telemetry comprising a plurality of destination and source attributes for network traffic of a network infrastructure;

categorizing the flow telemetry into one or more subscriber flows using the map;

selecting the subscriber flow of a subscriber;

attributing at least one of the services to at least a portion of the selected subscriber flow;

identifying the first service to attribute to a first portion of selected subscriber flow; and

if a second portion of the subscriber flow is associated with the first portion of subscriber flow telemetry, identifying the first service to attribute to the second portion of the subscriber flow telemetry.

15. The system of claim 14, wherein the map includes at least one flow-mapping that correlates a domain name to a service and wherein categorizing the flow telemetry comprises:

identifying domain name service (DNS) recursive responses sent to the subscriber in the flow telemetry, a recursive response including at least a domain name query and component address; and

identifying a third portion of the flow telemetry from the subscriber to the component address.

16. The system of claim 15, wherein attributing at least one of the services to at least a portion of the selected subscriber flow comprises:

identifying a service for the third portion of flow telemetry that correlates a domain name of the component address to a service in the selected subscriber flow.

17. The system of claim 14, wherein attributing at least one of the services to the selected subscriber flow telemetry comprises:

tracking combinations of component use as a flow feature.

18. The system of claim 17, wherein possible services are limited through one flow feature and a flow-mapping.

19. The system of claim 17, wherein tracking combinations of component use comprises:

tracking substantially simultaneous component usage by the subscriber, and wherein the identified service is identified through a flow-mapping correlating at least two components of simultaneous usage to a service.

20. The system of claim 17, wherein tracking combinations of component use comprises:

tracking a sequence of component usage by the subscriber, and wherein the identified service is identified through a flow-mapping correlating a sequence of at least two components to a service.