Network device trace correlation

Abstract

The techniques described herein present opportunities for service providers and/or network providers to optimize the Quality of User Experience (QoE) for data services by determining, using a broader network-based approach, the root cause of problems causing a service degradation. To determine the root cause of the problems, the techniques may collect different trace files from multiple different nodes in the telecommunications network. Each trace file includes a log of trace identifiers for numerous different data packets that have been generated, received, transmitted, relayed, and/or routed via the node in the telecommunications network, and each trace file log entry may be associated with a timestamp. Once collected, the techniques may correlate the different trace files from the multiple different nodes to identify, using a broader network-based analysis, service optimization opportunities.

Description

BACKGROUND

Modern telecommunication systems include heterogeneous mixtures of second, third, and fourth generation (2G, 3G, and 4G) cellular-wireless access technologies, which may be cross-compatible and may operate collectively to provide data communication services. Global Systems for Mobile (GSM) is an example of 2G telecommunications technologies; Universal Mobile Telecommunications System (UMTS) is an example of 3G telecommunications technologies; and Long Term Evolution (LTE), including LTE Advanced, and Evolved High-Speed Packet Access (HSPA+) are examples of 4G telecommunications technologies.

The infrastructure that makes up the modern telecommunications networks comprises multiple different components or devices (herein referred to as nodes) that are configured to generate, transmit, receive, relay, and/or route data packets so that data services can be requested by, and provided to, user equipment (UE) subscribed to a plan offered by one or more service providers or network communication providers that implement the telecommunications networks.

However, the data services and/or data communications provided via the nodes may often experience problems causing service degradation due to the vast amount of users and UEs accessing and requesting data via the telecommunications networks. For example, problems causing service degradation may be associated with data traffic congestion due to a high transfer demand for digital content (i.e., data transfer overload), and this may lead to data packet loss, packet queuing delay, an inability to establish a connection and other data communication and connection problems. These problems, if not addressed by a service provider or a network communication provider, degrade a network's Quality of Service (QoS) and an end user's Quality of User Experience (QoE) at the UE.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanying figures, in which the left-most digit of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.

FIG. 1 depicts an example environment where trace files can be collected from a plurality of nodes and correlated to identify network optimization opportunities, in accordance with embodiments of the disclosure.

FIG. 2 depicts example components of a client device configured to initiate data communications and log trace file entries in a trace file, in accordance with embodiments of the disclosure.

FIG. 3A depicts an example data packet that may be logged in a trace file, in accordance with embodiments of the disclosure.

FIG. 3B depicts an example trace file, in accordance with embodiments of the disclosure.

FIG. 4 depicts example components of a device configured to collect and correlate the trace file, as well as perform network analysis, in accordance with embodiments of the disclosure.

FIG. 5 is an example data packet communication diagram that is transmitted over a network and that represents horizontal correlation, in accordance with embodiments of the disclosure.

FIG. 6 is an example model that represents vertical correlation, in accordance with embodiments of the disclosure.

FIG. 7 is a flow chart of an example process for logging trace entries in a trace file, in accordance with embodiments of the disclosure.

FIG. 8 is a flow chart of an example process for collecting and correlating the trace files so that network analysis can be performed, in accordance with embodiments of the disclosure.

FIG. 9 is a flow chart of another example process for collecting and correlating the trace files so that network analysis can be performed, in accordance with embodiments of the disclosure.

DETAILED DESCRIPTION

The techniques described herein present opportunities for service providers and/or network providers to optimize the Quality of User Experience (QoE) for data services by determining, using a broader network-based approach, the root cause of problems causing a service degradation (e.g., what problem is occurring, why the problem is occurring, where in the telecommunications network the problem is occurring). To determine the root cause of the problems, the techniques may collect different trace files from multiple different nodes in the telecommunications network (or from a communication interface between two nodes in the telecommunications network). Each trace file includes a log of identifiers for numerous different data packets that have been generated, received, transmitted, relayed, and/or routed via the node in the telecommunications network, and each trace file log entry may be associated with a timestamp. Once collected, the techniques may correlate the different trace files from the multiple different nodes to identify, using a broader network-based analysis, service optimization opportunities. For example, after correlating the trace files and determining that QoE has experienced a certain level of degradation, the techniques may provide an alert notification and a recommendation for optimization so that remedial actions may be implemented to address the root cause of the problems.

In various embodiments, the techniques provide the alert notification and recommendation to a network administrator when the trace file correlation and analysis determines that a key performance indicator (KPI) is not satisfying a minimum service level or service goal associated with QoE. The network administrator may then initiate the remedial actions. In alternative embodiments, the collection of the trace files, the correlation and analysis of the traces files and the implementation of the remedial actions may be performed automatically via a preset network configuration when service levels or service goals are not being satisfied.

Conventional approaches to addressing degradation in a telecommunications network's QoS and an end user's QoE are directed to analyzing in isolation what is happening at a single node in the telecommunications network. For example, a system may collect data traffic information at a single node and then present the data traffic information so that it can be manually analyzed to determine sub-optimal conditions. Accordingly, it is difficult to determine the root cause of the problems and identify service optimization opportunities because a user (e.g., network administrator) must manually compare data traffic information at one node to data traffic information at another node. This manual process is tedious and time-consuming, if not impossible, due to the amount of data traffic flowing through the nodes in the telecommunications network. Further, the user may not even have access to data traffic information from one or more nodes, making identification of the problem node or nodes inconclusive at times.

In contrast to the conventional approaches discussed above, the techniques described herein automatically merge and correlate trace files from multiple different nodes in a telecommunications network so that the data traffic information at each node can be correlated across the whole telecommunications network. This network-based correlation of the trace files allows automatic analysis to be performed in an efficient and timely manner so that service optimization opportunities can be identified. Moreover, the network-based correlation of the trace files may also help a network administrator perform a manual analysis of the data traffic flowing through the telecommunications network.

FIG. 1 depicts an illustrative environment 100 for collecting multiple trace files from different nodes that exchange data packets using a telecommunications network. To this end, the environment 100 may include a client device 102 (considered as a node herein), a mobile telecommunications network (MTN) 104 that includes multiple MTN nodes 106(1) . . . 106(N), one or more data servers 108, and a Quality of Experience (QoE) optimization system 110. Moreover, the environment 100 illustrates trace files that are logged at each node. For example, the client device 102 is associated with one or more client device node trace files 112, and the MTN nodes 106(1) . . . 106(N) are each associated with one or more MTN node trace files 114(1) . . . 114(N). In various embodiments, the data servers 108 may each be associated with a data server node trace file 116.

The client device 102 may also be referred to as a UE, as mentioned above. Thus, client devices 102 may include, but are not limited to, smart phones, mobile phones, cell phones, tablet computers, portable computers, laptop computer, personal digital assistants (PDAs), an electronic book device, a handheld gaming unit, a personal media player device, or any other portable electronic device that may generate voice and/or digital data, request voice and/or digital data over the MTN 104, receive voice and/or digital data over the MTN 104, and/or exchange voice and/or digital data over the MTN 104.

The MTN 104 may be configured to implement one or more of the second, third, and fourth generation (2G, 3G, and 4G) cellular-wireless access technologies discussed above. Thus, the MTN 104 may implement GSM, UMTS, and/or LTE/LTE Advanced telecommunications technologies. Different types of MTN nodes 106(1) . . . 106(N) in the GSM, UMTS, LTE, LTE Advanced, and/or HSPA+ telecommunications technologies may include, but are not limited to, a combination of: base transceiver stations BTSs (e.g., NodeBs, Enhanced-NodeBs), Radio Network Controllers (RNCs), serving GPRS support nodes (SGSNs), gateway GPRS support nodes (GGSNs), proxies, a mobile switching center (MSC), a mobility management entity (MME), a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an evolved packet data gateway (e-PDG), or any other data traffic control entity configured to communicate and/or route data packets between the client device 102 and the data servers 108. The MTN nodes 106(1) . . . 106(N) may be configured with hardware and software that generates and/or logs an entry in the MTN node trace files 114(1) . . . 114(N). While FIG. 1 illustrates an MTN 104, it is understood in the context of this document, that the techniques discussed herein may also be implemented in other networking technologies, such as nodes that are part of a wide area network (WAN), metropolitan area network (MAN), local area network (LAN), neighborhood area network (NAN), personal area network (PAN), or the like.

In various embodiments, each trace entry includes an identifier associated with a data packet that is communicated through an interface for the MTN nodes 106(1) . . . 106(N) or associated with a data packet routed by the MTN nodes 106(1) . . . 106(N), as further discussed herein. In various embodiments, some of the MTN nodes 106(1) . . . 106(N) may be part of a core network (e.g., backhaul portion, carrier Ethernet) that is configured to access an IP-based network that provides data communications services (e.g., so that clients can access information at data servers 108). The data servers 108 may be owned and/or operated by web-based content providers, including, but not limited to: Bing®, Facebook®, Twitter®, Netflix®, Hulu®, YouTube®, Pandora®, iTunes®, Google Play®, Amazon Store®, CNN®, ESPN®, and the like.

In various embodiments, the MTN 104 may be configured to exchange data packets between the client device 102 and the data servers 108 using wired and/or wireless links. Moreover, the MTN 104 may be configured to determine a communications path or “pipe” so that the data packets can be routed and exchanged accordingly.

The data services and data access applications discussed in this document may include, but are not limited to, web browsing, video streaming, video conferencing, network gaming, social media applications, or any application or setting on the client device 102 that is configured to generate and exchange data with data servers 108 over the MTN 104.

In various embodiments, the QoE optimization system 110 may be configured to monitor and determine whether KPIs for the different data services are being satisfied or not satisfied in association with a particular service level or service goal, which may affect the QoE. Examples of KPIs for web browsing, as well as other applications executing on the client device 102, may include webpage loading time, Domain Name System (DNS) lookup time, Transmission Control Protocol (TCP) connect time, TCP round trip time (RTT), Hypertext Transfer Protocol (HTTP) response time, and so forth. Examples of KPIs for video streaming and video conferencing, as well as other applications executing on the client device 102, may include application start delays, catalog browsing, searching delay, video start delay, fast forward and rewind delay, a number of buffering events, duration per buffering event, rebuffering ratio, a video frame rate, and so forth. Other KPIs for a UE may include application layer KPIs (such as average/minimum/maximum bit rate, traffic burstiness, amount of data bytes transferred), transport layer KPIs (such as TCP retransmissions and TCP resets), RLC/MAC layer KPIs (such as RLC retransmissions and RLC RTT), and physical layer KPIs (such as physical retransmissions, physical RTT, physical UL interference, UE power, RACH time). The KPIs provided above are presented as examples, and thus, the list is not exhaustive. Rather, service providers and/or network providers may contemplate a large number of different KPIs which aid in gauging the QoE associated with the data services provided.

FIG. 2 illustrates example components of the client device 102, which is configured to wirelessly transmit a request for data to the MTN 104 or receive data from the data servers 108 over the MTN 104. Thus, the client device 102 may include one or more processor(s) 202, a radio transceiver 204 for wirelessly communicating with the MTN 104, and a memory 206 storing a device operating system (OS) 208, various software applications 210 configured to request/receive data over the MTN 104, a network interface module 212, and the client device node trace files 112.

In various embodiments, the applications 210 stored at the client device 102 may include, but are not limited, a web browser application 214, a video streaming application 216, an online gaming application 218, and so on, through an Nth software application 220. During execution on the client device 102, each of the applications 210 may be configured to cause the client device 102 to initiate data communications with the data servers 108 over the MTN 104.

The client device 102 may be configured to communicate over a telecommunications network using any common wireless and/or wired network access technology. Moreover, the client device 102 may be configured to run any compatible device OS, including but not limited to, Microsoft Windows Mobile®, Google Android®, Apple iOS®, Linux Mobile®, as well as any other common mobile device OS.

Each of the one or more processor(s) 202, can include one or more central processing units (CPUs) having multiple arithmetic logic units (ALUs) that perform arithmetic and logical operations, as well as one or more control units (CUs) that extract instructions and stored content from processor cache-level memory, and then executes instructions by calling on the ALUs during program execution. In an implementation, the processor(s) 202 may be configured to execute each of the software applications 210 stored in the memory 206. In various embodiments, the network interface module 212 may be configured to detect an action (e.g., operation, command, user input) directed to one of the applications 210, the action triggering the generation of a data transfer request and a transmission of the data transfer request.

The memory 206 may be implemented using computer readable media, such as computer storage media. Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communications media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism.

In various embodiments, the client device node trace files 112 may correspond to individual ones of multiple layers at the client device 102. For example, the multiple layers may correspond to the Open Systems Interconnection (OSI) model characterizing and standardizing functions of a communications system in terms of abstraction layers. The multiple layers may also correspond to the Internet Protocol (IP) suite. Thus, in various embodiments, the client device 102 may log a single client device node trace file 112 for each of a physical layer, a data link layer, a network layer, a transport layer, a session layer, a presentation layer, and an application layer, as a data packet is generated and configured amongst the layers for communication from the client device 102 to the data servers 108 over the MTN 104.

Moreover, the client device 102 may log a single client device node trace file 112 for a particular set of the abstract layers mentioned above. For example, the client device may log a first client device node trace file 112 for the application/presentation/session layers, a second client device node trace file 112 for the transport/network layers, a third client device node trace file 112 for the data link layer, and a fourth client device node trace file 112 for the physical layer. By logging trace files at the layer level of the client device 102, the QoE optimization system 110 may be able to determine the root cause of problems at a more granular level after collecting the trace files at the layer level (as compared to the node level). This may further help when identifying remedial actions that optimize the QoE.

Similar to the multiple different layers at the client device 102, each of the MTN nodes 106(1) . . . 106(N), as well as each of the data servers 108, may also log different trace files (e.g., 114(1) . . . 114(N) and 116) for individual layers, or defined combination of layers. Accordingly, the QoE optimization system 110 may also identify the root cause of problems at a more granular level at the MTN nodes 106(1) . . . 106(N) and the data servers 108.

FIG. 3A depicts an example data packet 300 configured to be logged in one of the client device node trace files 112, the MTN node trace files 114(1) . . . 114(N), or the data server node trace files 116. The data packet 300 may be configured in association with one or more communication or data exchange/formatting protocols such as TCP, IP, HTTP or other protocols directed to communicating or exchanging content over the MTN 104.

In various embodiments, the data packet 300 may include a header portion 302 and a payload portion 304. The data packet may further include a portion including N fields, at least a portion of which are used to create a trace identification 306 for the data packet. In various embodiments, the fields used to create the trace identification may be part of the header portion 302, the payload portion 304, or a combination thereof.

In various embodiments, one or more of the N fields may be associated with routing and addressing information commonly included in the data packet, or one of more fields that may be defined and are unique to a particular protocol. For example, a field may include a Packet Data Protocol (PDP) address, a source port number, a destination port number, a checksum number (for IPv4 or IPv6), a sequence number, an acknowledgement number, an Internet Protocol (IP) address, a source address, a destination address or any other field in the data packet that may help distinguish one data packet from another. Moreover, a field may also help identify a request/response sequence or pair, or a particular communication session established, such that data packets can be matched and/or correlated correctly, even though the trace ID 306 as a whole may not be an exact match.

Accordingly, the trace ID 306 may be comprised of a single field, or a combination of two fields, three fields, four fields, and so forth. The more fields used to comprise the trace ID 306 may help ensure that the trace ID 306 is unique for the data packet or correlates related data packets, so that the data packets can be tracked through their communication paths. In at least one embodiment, the trace ID 306 includes four fields: a PDP address, a checksum number, a source port number, and a destination port number.

FIG. 3B depicts an example trace file 308 that may correspond to the client device node trace files 112 logged at the client device, the MTN node trace files 114(1) . . . 114(N) logged at the MTN nodes 106(1) . . . 106(N), or the data server node trace files 116 logged at the data servers 108. The trace file 308 may include a node identifier 310 that the QoE optimization system 110 may use so that it knows what node (e.g., the client device 102, one of the MTN nodes 106(1) . . . 106(N), or a data server 108) the trace file is associated with after the QoE optimization system 110 collects the trace files. Thus, the QoE optimization system 110 will be able to identify the node or nodes where the root cause of the problems is occurring and then implement remedial actions accordingly.

In various embodiments, the trace file 308 is configured to log entries for the data packets communicated via a node or node interface, e.g., the traces column 312 (e.g., the trace IDs 306 in the traces column 312 may correspond to multiple different client devices using the node to communicate). Moreover, the trace file 308 is configured to receive timing information 314 in the form of a timestamp for each entry, and associate/store the timestamp with the entry, as shown. Accordingly, the trace file 308 may sequentially log a list of numerous data packet IDs and timestamps associated with when the data packets were received, transmitted, routed, and so forth.

At each node, the timestamps are logged via use of a time source (e.g., a local time source or a remote time source). In one embodiment, the time source may be common for the nodes, or at least some of the nodes. In an alternative, the time source may be different for each node, or at least some of the nodes. Thus, the timing information 314 merged together (from multiple trace files) may be approximated merged timing information because some nodes may use different time sources that may not be synchronized.

FIG. 4 illustrates example components of the QoE optimization system 110. In various embodiments, the QoE optimization system 110 may be a service provider entity or a telecommunications provider entity that may be part of one of the MTN nodes 106(1) . . . 106(N), or in communication with the MTN nodes 106(1) . . . 106(N) via a network connection. Moreover, in various embodiments, the QoE optimization system 110 may be a standalone application that is part of the client device 102 or a data server 108.

In various embodiments, the QoE optimization system 110 may be one or more server or computing devices that include one or more processor(s) 402 and memory 404 storing a device OS 406 and a network interface module 408 that enables the trace file receiving module 410 of the QoE optimization system 110 to communicate and receive the trace files from the nodes in FIG. 1, and store the trace files in the trace file database 412 so they can be correlated and analyzed.

Each of the one or more processor(s) 402 of the QoE optimization system 110 may include one or more CPUs having multiple ALUs that perform arithmetic and logical operations, as well as one or more CUs that extract instructions and content from processor cache memory, and then executes the instructions by calling on the ALUs, as necessary, during program execution. The processor(s) 402 may further be configured to execute the modules stored in the memory 404.

The memory 404 may be implemented using computer readable media, such as computer storage media. Computer-readable media includes, at least, two types of computer-readable media, namely computer storage media and communications media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information for access by a computing device. In contrast, communication media may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism.

In various embodiments, the memory 404 may further store a trace file correlation module 414, a cross file analysis module 416, a controls module 418, a key performance indicator (KPI) module 420, a trace sorting module 422, a presentation and notification module 424, and a remedial action module 426.

The trace file correlation module 414 is configured to merge the client device node trace files 112, the MTN node trace files 114(1) . . . 114(N), and/or the data server node trace files 116. By merging the trace files, the trace file correlation module 414 matches trace identifications 306 from different nodes that may be associated with the same data packet. Accordingly, the trace identification 306 remains constant as the data packet is communicated and/or routed from the client device 102 to the one or more data servers 108 (e.g., uplink via a determined route/path in the MTN 104), or from the one or more data servers 108 to the client device 102 (e.g., downlink via a determined route/path in the MTN 104). In at least some embodiments, the trace file correlation module 414 may merge a subset of a total number of trace files collected.

In some embodiments, the trace file correlation module 414 is further configured to match corresponding request/response data packets that may not have the same trace identification 306, but may be paired by referencing one or more fields in the trace identification 306 that associates a response packet with a request packet (e.g., a sequential indicator conveying that response packet “2” is responsive to request packet “1”). In further embodiments, the trace file correlation module 414 may match a group of data packets communicated within an established communication session (e.g., a video stream), by referencing one or more fields in the trace identification 306 that associate the data packet with the communication session. One or more fields used by the trace file correlation module 414 to match a request packet and a response packet, or to match data packets communicated within an established communication session, may depend on a type of communication protocol used.

In various embodiments, once the trace file correlation module 414 merges the trace files and matches trace IDs 306 for a single data packet, for a request/response packet pair, or for data packets communicated within an established communication session, then the cross file analysis module 416 may use the correlation to perform network communications analysis and to determine the root cause of problems which may be leading to a degradation in QoE. In various embodiments, the cross file analysis module 416 may use the timing information 314 for the matched trace IDs 306 to perform the network communications analysis and to determine the root causes of problems that can be identified via timing issues. Example network communications analysis may relate to: packet delay, latency mapping, packet drop rate, congestion windows, packet loss, packet error rate, location of retransmission requests and a number of retransmission requests, etc. Moreover, results from the network communication analysis may identify one or more nodes along the communication path that are the root cause of the problems, and why the one or more nodes are the root cause of the problems. Therefore, the QoE optimization system 110 can identify opportunities to optimize the QoE by eliminating the problems, or part of the problems, via remedial actions.

In various embodiments, the cross file analysis module 416 may perform analysis across the multiple merged trace files in accordance with instructions received from a controls module 418. The controls module 418 may receive a specific type of analysis to be performed from a network administrator. For example, the network administrator may input commands to the controls module 418 that identify one or more KPIs to be analyzed to ensure that a defined service level or service goal is or is not being satisfied. In various embodiments, the KPI module 420 defines the different KPIs, as listed above, for different applications 210 executing on the client device 102. Moreover, the KPI module 420 may also define particular service levels or service goals for the KPIs, as defined by a service provider or a network telecommunications provider (e.g., by an a network administrator acting as an agent for the service provider or the network telecommunications provider).

In some embodiments, the cross file analysis module 416 may perform analysis automatically. Thus, a network administrator may configure the trace file receiving module 410 of the QoE optimization system 110 to collect the different trace files so that they can be merged by the trace file correlation module 414 and the cross file analysis module 416 can perform some sort of analysis in a periodic manner (every hour, every day, every two days, and so forth). In various embodiments, this automatic analysis may be performed separately for individual KPIs or a particular combination of KPIs. In other embodiments, the automatic and periodic analysis may be performed a particular application of the various applications 210 configured to be executed on the client device 102.

In various embodiments, the trace sorting module 422 may be employed by the cross file analysis module 416 to sort the trace IDs 306 that have been merged from the trace files collected. This sorting, or filtering, may aid in the analysis performed by the cross file analysis module 416. For example, the trace sorting module 422 may use one or more of the fields to sort the trace IDs so that data packets sent from or sent to a particular client device 102 are identified (e.g., a particular user or subscriber). The trace sorting module 422 may use the timestamps to sort the trace IDs 306 so that data packets in a particular timing window are identified. The trace sorting module 422 may use the trace sorting module 422 may use one or more of the fields to sort the trace IDs 306 so that data packets from a particular type of equipment (e.g., a model from a manufacturer) are identified. The trace sorting module 422 may use one or more of the fields to sort the trace IDs 306 so that data packets communicated for a particular application are identified. The trace sorting module 422 may use one or more of the fields to sort the trace IDs 306 so that data packets communicated to/from a particular source are identified (e.g., a data server 108).

In various embodiments, the QoE optimization system 110 employs the presentation and notification module 424 to format and present a notification or alert (e.g., via a graphical user interface) after the cross file analysis module 416 performs a network performance analysis. In one embodiment, a notification may state that networks communications are well and that one or more KPIs and service levels are being satisfied. Therefore, QoE is not currently degraded. In an alternative embodiment, an alert may report that network communications are causing degradation in QoE because one or more KPIs and a particular service level are not being satisfied. In this alternative embodiment, the presentation and notification module 424 may convey a location (e.g., one or more nodes) of the root cause of the problems and/or one or more reasons for the problems.

In various embodiments, the remedial action module 426 may include instructions to remediate the network communication problems identified. Thus, the cross file analysis module and/or the presentation and notification module 424 may access the remedial action module to determine one or more suggested solutions to the problems, and then present the selected solutions via a graphical user interface so they may be implemented. In at least one embodiment, the remedial action module 426 is configured to implement the solutions automatically in response to the identification of the problems.

FIG. 5 illustrates an example timing diagram 500 of data packets being exchanged between a first node 502 (e.g., the client device 102 or UE) and a fourth node 504 (e.g., a data server 108), via a second node 506 (e.g., an RNC) and third node 508 (e.g., a core network node) that may be part of the MTN 104. This example is provided to show how the QoE optimization system 110 may identify network communication problems using the timing information 314 in the trace files 308. Accordingly, the first node 502 logs trace entries in the client node trace files 112, the second node 506 logs trace entries in MTN node trace files 114(1), the third node 508 logs trace entries in MTN node trace files 114(2), and the fourth node logs trace entries in server node trace files 116. While four nodes are depicted in FIG. 5, it is understood in the context of this document that additional nodes may be involved in the exchange of data packets between a client device 102 and a data server 108, particularly additional nodes within the MTN 104. The example timing diagram 500 in FIG. 5 represents a horizontal correlation of packets communicated across multiple nodes of a network. Horizontal correlation may use horizontal unique trace IDs based on packet header information to correlate the packets across the multiple nodes. In contrast, vertical correlation refers to packets as they are communicated amongst multiple different layers (e.g., OSI model layers or stacks) at a single node, as further discussed with respect to FIG. 6. Vertical correlation may use a vertical unique trace ID based on IP payloads to correlate the packets as they are communicated through the layers.

FIG. 5 illustrates an initial data packet being sent from the first node 502 to the fourth node 504 (e.g., via an uplink), and a response data packet being sent from the fourth node 504 to the first node 502 (e.g., via a downlink). Accordingly, FIG. 5 shows a RTT 510 at the first node 502 that represents a time between the transmission of the initial data packet and the reception of the response data packet.

As illustrated in FIG. 5, the initial data packet is generated at the first node 502 and transmitted 512 to the second node 506. Thus, the first node 502 may log an entry for the data packet in the client node trace files 112 with a timestamp (e.g., labeled “1” in FIG. 5). The second node 506 receives the initial data packet, may access, change and/or add routing information, and then relays 514 the initial data packet to the third node 508. In association with this functionality, the second node 506 may log an entry with a timestamp for the data packet in the MTN node trace files 114(1) (e.g., labeled “2” in FIG. 5). Similarly, the third node 508 receives the relayed data packet, may access, change and/or add routing information, and then relays 516 the data packet to the fourth node 504. Here, the third node 508 may log an entry with a timestamp for the data packet in the MTN node trace files 114(2) (e.g., labeled “3” in FIG. 5).

Then the fourth node 504 receives the initial data packet and generates and transmits 518 the response packet, logging an entry with a timestamp for the data packet received, and/or the response data packet response transmitted, in the server node trace files 116 (e.g., labeled “4” in FIG. 5). Similar to the uplink, the third node 508 and the second node 506 route and relay the response packet back to the first node 502 at 520 and 522, and log entries with timestamps for the response packet (e.g., labeled “5” and “6”). The first node 502 then logs an entry with a timestamp for the response packet (e.g., labeled “7” in FIG. 5), and the RTT is complete.

When the QoE optimization system 110 collects the trace files associated with the example timing diagram in FIG. 5, the QoE optimization system 110 may determine that the RTT 510 is longer than normal or longer than expected for the particular application being used at the first node 502. After this determination, the QoE optimization system 110 may utilize the merged trace files and the separate timestamps, as discussed above with respect to FIG. 4, to calculate individual packet communication delays between the nodes (whether uplink or downlink), and identify one or more nodes that may contribute most to the longer than expected RTT during the uplink and/or the downlink (e.g., at which node was the data packet delayed).

In various embodiments, the timing diagram 500 of FIG. 5 may be representative of a TCP handshake (e.g., a synchronize request and an acknowledgement response) between a client device 102 and a data server 108. In other embodiments, the timing diagram 500 of FIG. 5 may be representative of a DNS lookup between a client device 102 and a DNS server. In even further embodiments, the timing diagram 500 of FIG. 5 may be representative of an HTTP request and a data packet response between a client device 102 and a data server 108.

FIG. 6 illustrates an example of the vertical correlation 600 that represents packets as they are generated at and/or communicated amongst multiple different layers (e.g., 1 . . . N) at a single node. For example, the different layers may be associated with an OSI model and thus may be a physical layer, a data link layer, a network layer, a transport layer, a session layer, a presentation layer, and an application layer (as well as sublayers within the layers). Moreover, vertical correlation may use a vertical unique trace ID based on IP payloads to correlate the packets as they are communicated through the layers.

FIGS. 7-9 present illustrative processes for merging trace files from multiple different nodes and correlating trace IDs so that performance metrics relating to QoE can be implemented and remedial actions may be performed. Each process is illustrated as a collection of blocks in a logical flow chart, which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer-executable instructions that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions may include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or in parallel to implement the process. For discussion purposes, the processes in FIGS. 7-9 are described with reference to the example environment 100 of FIG. 1, the example components of FIGS. 2 and 4, the example data packet of FIG. 3A, the example trace file of FIG. 3B, the example timing diagram of FIG. 5, and/or the example vertical correlation of FIG. 6.

FIG. 7 shows a flow diagram of an example process 700 for logging entries in a trace file. The example process 700 may be performed at a node that generates, communicates, receives, transmits, routes, relays, and/or stores a data packet (e.g., the client device 102, the MTN nodes 106(1) . . . 106(N), the data serves 108).

At block 702, a node monitors data packets that have been generated by, communicated through, received at, transmitted by, routed by, relayed by, and/or stored at the node. In various embodiments the monitoring may be at the node level (e.g., a single trace file for the node) or the layer level (e.g., multiple trace files for the node), as discussed above.

At block 704, the node creates and logs one or more entries for the monitored data packets in a trace file 306. As discussed above, each entry may include one or more fields that represent a trace ID 306 that distinguishes the data packet from other data packets. In various embodiments, the node may log separate entries for the data packet in different trace files associated with different layers for the node.

At block 706, the node timestamps each trace ID 306 when logging the entry in the trace file 306. Accordingly, the node may access a time source to determine the timing information for each entry.

At block 708, the node sends the one or more trace files to the QoE optimization system 110. In various embodiments, the node may send the trace files to the QoE optimization system 110 in response to a request (e.g., periodic request or on-demand request) from the QoE optimization system 110. In an alternative embodiment, the node may be aware or a reporting schedule, and proactively send the trace files to the QoE optimization system 110 in accordance with the reporting schedule.

FIG. 8 shows a flow diagram of an example process 800 for collecting trace files, merging the trace files, and performing network communications analysis. The example process 800 may be performed by the components that are part of the QoE optimization system 110.

At block 802, the trace file receiving module 410 may automatically collect the trace files from multiple nodes (e.g., the client device 102, the MTN nodes 106(1), the data servers 108). In various embodiments, the trace file receiving module 410 may automatically collect the trace files in accordance with a periodic schedule. In various embodiments, the trace file receiving module 410 may automatically collect the trace files from an identified subset of nodes in the MTN 104.

At block 804, the trace file correlation module 414 merges the trace files collected. In various embodiments, the merging may include merging trace files corresponding to different layers at a single node (e.g., layer level), as well as merging trace files received from different nodes (e.g., node level).

At block 806, the cross file analysis module 416 analyzes the merged trace files to determine whether the QoE for users of client devices has degraded to a predefined level. In various embodiments, the cross file analysis module 416 performs analysis using timestamps of trace IDs that match a single data packet, a request/response packet pair, a group of data packets that are part of an established communication session. Moreover, as part of the analysis, the cross file analysis module 416 may identify (e.g., via the KPI module 420 and/or the controls module 418) one or more KPIs to evaluate and a particular service level or service goals associated with the KPI. The QoE may be found to be degraded to the predefined level if the particular service level is not being satisfied (e.g., webpage loading time is longer than two seconds, RTT is greater than one second, etc.). As part of the analysis, the cross file analysis module 416 may employ the trace sorting module 422 to sort the merged trace IDs so the analysis can be performed.

At block 808, the cross file analysis module 416 identifies one or more nodes and/or one or more layers within the identified nodes that may be the root cause of the problems contributing to the degraded QoE.

At block 810, the presentation and notification module 424 may format and generate a report or an alert to be conveyed via a GUI to a network administrator. The report or the alert may provide a result of the cross trace file analysis.

At block 812, the remedial action module 426 may implement remedial actions to address the problems contributing to the degraded QoE. In various embodiments, the remedial actions may be implemented automatically in accordance with predefined instructions in the controls module 418. In other embodiments, the remedial actions may be implemented in response to a selection and input provided to the controls module 418 by a network administrator.

FIG. 9 shows a flow diagram of another example process 900 for collecting trace files, merging the trace files, and performing network communications analysis. The example process 900 may be performed by the components that are part of the QoE optimization system 110.

At block 902, the controls module 418 may receive a request from a network administrator to collect trace files from multiple different nodes for cross trace file analysis.

At block 904, the trace file receiving module 410 may collect the trace files from multiple nodes (e.g., the client device 102, the MTN nodes 106(1), the data servers 108).

At block 906, the trace file correlation module 414 merges the trace files collected. In various embodiments, the merging may include merging trace files corresponding to different layers at a single node (e.g., layer level), as well as merging trace files received from different nodes (e.g., node level).

At block 908, the cross file analysis module 416 may identify one or more trace IDs that provide a basis for the cross trace file analysis being requested.

At block 910, the cross file analysis module 416 may determine, based on the identified trace IDs, whether KPIs associated with the requested cross trace file analysis are satisfying a defined level.

At block 912, the presentation and notification module 424 may format and the results to a network administrator requesting the analysis.

At block 914, the remedial action module 426 may implement remedial actions to address the problems.

CONCLUSION

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.

Claims

1. A method comprising: collecting a plurality of trace files from a plurality of nodes involved in communicating data packets between one or more client devices and one or more data servers, wherein individual ones of the plurality of trace files includes trace entries and at least two trace files of the plurality of trace files are respectively collected from at least two layers of a same node of the plurality of nodes for which communication functions are characterized by an Open Systems Interconnection (OSI) model or an Internet Protocol (IP) suite;correlating the trace entries across the plurality of trace files;performing, via one or more processors configured with executable instructions, a communications analysis on the correlated trace entries to determine one or more of the plurality of nodes causing a problem that degrades a level of data service; andreporting the problem degrading the level of data service and the one or more nodes causing the problem degrading the level of data service.

2. The method of claim 1, further comprising implementing one or more remedial actions to correct the problem degrading the level of data service.

3. The method of claim 1, wherein an individual trace entry includes a trace identification identifying a data packet and a timestamp representing a time when the data packet was at least one of: received at a node;transmitted by a node; orcommunicated from one layer of a node to another layer of the node.

4. The method of claim 3, wherein the communications analysis uses the respective timestamps to perform timing analysis of the communication of the respective data packets.

5. The method of claim 3, further comprising creating the trace identification based on one or more fields from the data packet.

6. The method of claim 5, wherein the one or more fields are selected from a group comprising: a PDP address for the data packet;a checksum number for the data packet;a source port number for the data packet; anda destination port number for the data packet.

7. The method of claim 1, wherein the problem degrading the level of data service is data packet delay.

8. The method of claim 1, wherein the problem degrading the level of data service is data packet loss.

9. The method of claim 1, wherein the at least two trace files respectively collected from the at least two layers of the same node comprise a first trace file associated with a first Open Systems Interconnection (OSI) layer of the same node and a second trace file associated a second OSI layer of the same node.

10. One or more device memories storing computer-executable instructions that, when executed by one or more processors, performs operations comprising: collecting at least one trace file from individual ones of a plurality of intermediate nodes that are part of data communications between one or more client devices and one or more data servers, wherein an individual trace file includes multiple entries, each entry being associated with a data packet logged at a respective intermediate node and defining a time the entry was logged;collecting at least two layer trace files from an individual one of the one or more client devices or the one or more data servers for which communication functions are characterized by an Open Systems Interconnection (OSI) model or an Internet Protocol (IP) suite, wherein an individual layer trace file includes multiple layer entries, each layer entry: being associated with a data packet logged at a respective layer of the OSI model or of the IP suite of a client device or a data server; anddefining a time the layer entry was logged;merging the trace files collected from the plurality of intermediate nodes and the at least two layer trace files collected from individual ones of the one or more client devices or the one or more data servers to match entries and layer entries for data packets that are related to one another;analyzing a communication performance by evaluating times the matched entries and layer entries were logged; andidentifying, based on the analysis, a problem degrading a level of data service.

11. The one or more device memories of claim 10, wherein the matched entries and layer entries are associated with a same data packet.

12. The one or more device memories of claim 10, wherein the matched entries and layer entries are associated with a request/response packet pair.

13. The one or more device memories of claim 10, wherein the matched entries and layer entries are associated with an established communication session.

14. The one or more device memories of claim 10, wherein individual entries or individual layer entries include a trace identification identifying a data packet.

15. The one or more device memories of claim 14, creating the trace identification based on one or more fields of the data packet.

16. The one or more device memories of claim 15, wherein the one or more fields are selected from a group comprising: a PDP address for the data packet;a checksum number for the data packet;a source port number for the data packet; anda destination port number for the data packet.

17. The one or more device memories of claim 10, wherein the level of data service is associated with a Quality of User Experience (QoE).

18. The one or more device memories of claim 10, wherein the level of data service is associated with one or more defined key performance indicators for an application executing on at least one client device of the one or more client devices.

19. A system comprising: one or more processors;one or more memories;a trace file receiving module, stored on the one or more memories and operable by the one or more processors, that collects a plurality of trace files from a plurality of nodes involved in communicating data packets between one or more client devices and one or more data servers, individual trace files including multiple entries and wherein at least two trace files of the plurality of trace files are respectively collected from at least two layers of a same node of the plurality of nodes for which communication functions are characterized by an Open Systems Interconnection (OSI) model or an Internet Protocol (IP) suite;a trace file correlation module, stored on the one or more memories and operable by the one or more processors, that correlates the entries from one of: two or more trace files collected from two or more nodes of the plurality of nodes; orthe at least two trace files respectively collected from at least two layers of the same node of the plurality of nodes; anda cross file analysis module, stored on the one or more memories and operable by the one or more processors, that analyzes the correlated entries to identify one or more of the plurality of nodes causing a problem that degrades a level of data service associated with data packet communications.

20. The system of claim 19, wherein the problem degrading the level of data service comprises latency.