Diagnostic traffic generation for automatic testing and troubleshooting

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit of U.S. patent application Ser. No. 15/584,696, filed on May 2, 2017, entitled “Diagnostic Traffic Generation For Automatic Testing And Troubleshooting,” the contents of which are hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

The technical field generally relates to software-defined networks and, more specifically, to testing in software-defined networks.

BACKGROUND

Communication networks have migrated from using specialized networking equipment executing on dedicated hardware, like routers, firewalls, and gateways, to virtualized network components, such as virtual network functions (VNF) and virtual machines (VM) that may be implemented or run on general purpose hardware within a cloud infrastructure. Network management of network components—whether or not virtualized—may require implementing, from time to time, software changes across the network or across a subset of the network components. These software changes may include software patches, software updates, configuration changes, or installation/uninstallation of software. In the complex computing environment today there are challenges with troubleshooting network issues that may be based on these software changes.

SUMMARY

Disclosed herein is a framework for diagnostic traffic generation for automatic testing and troubleshooting. Software-defined tracing and measurement (SDTM), as disclosed herein, may allow for debugging at multiple vantage points at different layers (e.g., layer 2, layer 3, etc.). Advanced measurements apps may emulate or talk to virtual network functions to generate calls or packets or provide backend service for interactive exploration or analysis of collected data.

In an example, an apparatus may include a processor and a memory coupled with the processor that effectuates operations. The operations may include detecting an event associated with communication between a first device (e.g., a mobile device) and a second device (e.g., cloud sever) during a first period. Based on detecting the event, providing instructions to record operations by the first device or second device for a second period; and based on the recorded operations, providing instructions to install a virtual machine for generating test traffic that simulates the recorded traffic of the second period on the first device.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to limitations that solve any or all disadvantages noted in any part of this disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an exemplary layer and function implementation for software-defined tracing and measurement.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates an exemplary system that may implement software-defined tracing and measurement.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates an exemplary method for software-defined tracing and measurement.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates an exemplary method flow for software-defined tracing and measurement.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates an exemplary method for software-defined tracing and measurement.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates a schematic of an exemplary network device.

<figref idref="DRAWINGS">FIG. 7</figref> illustrates an exemplary communication system that provides wireless telecommunication services over wireless communication networks.

<figref idref="DRAWINGS">FIG. 8A</figref> is a representation of an exemplary network.

<figref idref="DRAWINGS">FIG. 8B</figref> is a representation of an exemplary hardware platform for a network.

DETAILED DESCRIPTION

With the development of software defined networks (SDNs), there are an increasing number indirections, service chaining, application programming interfaces (APIs), and layering which may create more need to independently verify connectivity, service path, or performance. Disclosed herein is a framework for debugging of operational use cases in that may be in a SDN. Software-defined tracing and measurement (SDTM), as disclosed herein, may allow for debugging at multiple vantage points at different layers (e.g., layer 2, layer 3, etc.), such as shown in <figref idref="DRAWINGS">FIG. 1</figref>. SDTM (e.g., diagnostic traffic generation for automatic testing and troubleshooting) may allow for tracing and measuring that may be run as a virtual network function (VNF) with flexibility and scale. SDTM service may provide tracer services that filter, capture, or forward flows that may include packets (e.g., requests or responses), commands, calls, or protocols to look for particular signatures. Tracers <b>94</b> may be invoked on-demand to generate test traffic. SDTM service may provide measurement services that may include deploying or controlling tracers (and collecting results), deducing expected topologies or connectivity to verify independently or interface with standard stats from other systems and network devices. Advanced measurements apps <b>91</b> (e.g., <figref idref="DRAWINGS">FIG. 1</figref>) may 1) may emulate or talk to virtual network functions to generate calls or packets; 2) provide backend service for interactive exploration or analysis of collected data; or 3) automate measurement or tracing operations.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates an exemplary system <b>100</b> that may implement VNF diagnostic traffic generation for automatic testing and troubleshooting. In system <b>100</b>, there may be a communications network <b>112</b> that may connect several devices. Exemplary devices may include switch <b>104</b>, switch <b>107</b>, router <b>110</b>, base station <b>103</b>, mobile device <b>101</b>, desktop computer <b>104</b>, or server <b>114</b>. Each device may include a hypervisor or the like that may be used to generate a virtual machine (VM) and corresponding virtual network functions (VNF). For example, there may be VM <b>113</b> in mobile device <b>101</b>, VM <b>102</b> in base station <b>103</b>, VM <b>104</b> in switch <b>105</b>, VM <b>106</b> in switch <b>107</b>, VM <b>110</b> in router <b>111</b>, and VM <b>108</b> in desktop computer <b>109</b>. As provided in more detail herein, VMs may be dynamically generated or removed, as needed.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates an exemplary method for implementing software-defined tracing and measurements (SDTM) as disclosed herein. At step <b>131</b>, server <b>114</b> may detect an event that triggers SDTM service. Events that may trigger SDTM services for step <b>131</b> may be based on types of packets traversing a network (e.g., network <b>112</b>), types of errors, reaching a threshold error rate, reaching a threshold traffic load, reaching a threshold packet loss, number of times an application resets or crashes, an operating system change (e.g., version), a network device change (e.g., hardware or software version), indication of a type of customer complaint, reaching a threshold number of customer complaints, date, time, location of a device (e.g., mobile device <b>101</b>), a billing issue, or a request from an administrator (e.g., user), among other things.

At step <b>132</b>, based on the event of step <b>131</b>, server <b>114</b> may determine one or more devices of interest, which may be further based on network paths of interest (e.g., one or more communication paths for uploading or downloading data). For example, in <figref idref="DRAWINGS">FIG. 2</figref>, cloud server <b>105</b>, mobile device <b>101</b>, or desktop computer <b>109</b> may be identified as devices of interest based on detecting threshold number of errors. At step <b>133</b>, server <b>114</b> may provide instructions for a VM or VNF to be activated on the one or more devices of interest. Activating the VM in step <b>133</b> may include providing instructions to generate a VM (or VNF) that was not already instantiated on the one more devices of interest or providing instructions to configure a VM already on the one or more devices to process or generate traffic for testing based on the situation. In an example, VM <b>102</b> may be configured to generate a particular type of traffic or process data as if it were a particular type of device (e.g., a mobile device or gaming server) running a particular type of application (e.g., online gaming application). In another example, VM <b>113</b> may generate data or functions that emulate processes that occurred when communicating with or through VM <b>102</b>. In this example, VM <b>102</b> may be an instantiated test process that simulates the functions of another VM or be the normal VM <b>102</b> not instantiated for testing purposes.

With continued reference to <figref idref="DRAWINGS">FIG. 3</figref>, at step <b>134</b>, server <b>114</b> may provide instructions for VM <b>113</b> on mobile device <b>101</b> and other VMs of interest to generate or otherwise process test traffic using the SDTM service for a test period. At step <b>135</b>, server <b>114</b> may obtain statistical information associated with the test period of step <b>134</b>. The statistical information may include network performance statistics, accounting data for the purpose of billing, usage data of the network or devices in the network. At step <b>136</b>, server <b>114</b>, based on the statistics of step <b>135</b>, may determine that one or more devices, network paths, or software applications, for example, are the source of a problem.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates an exemplary method flow for a scenario implementing VNF diagnostic traffic generation for automatic testing and troubleshooting disclosed herein. At step <b>141</b> there may be general communication between mobile device <b>101</b> and cloud server <b>105</b>. Exemplary communications may be associated with e-mail, gaming, or cloud networking services, among other things. At step <b>142</b>, server <b>141</b> may detect an event. In an example, server <b>114</b> may periodically check statistical information associated with the general communication for mobile device <b>101</b> and cloud server <b>105</b> may send a message to server <b>114</b> upon detecting the event. This event may be any event, such as the events disclosed herein with reference to <figref idref="DRAWINGS">FIG. 3</figref>. At step <b>143</b>, based on the event, server <b>114</b> may monitor or record the network traffic (or “operations” which is a term that may generally be substituted for “traffic” as disclosed herein) of mobile device <b>101</b>, cloud server <b>105</b>, or other devices along the communication path or tangentially effect the communication between mobile device <b>101</b> and cloud server <b>105</b>, such as base station <b>103</b> or router <b>110</b>. The recorded operations may include commands or messages sent or otherwise executed by mobile device <b>101</b> or cloud server <b>105</b>. The operations or traffic may include packets (e.g., requests or responses), commands, calls, or protocols. At step <b>144</b>, based on the event of step <b>142</b> or the monitored (or recorded) traffic of step <b>143</b>, server <b>114</b> may determine devices of interest to generate test traffic. The test traffic may specifically mimic the commands recorded in step <b>143</b> or may generally simulate traffic associated with applications of the type of mobile device <b>101</b> or cloud server <b>105</b>. The general simulation, for example, may be a random selection of operations based on the average (or median or mode, etc.) location or other event of mobile device, cloud server, or other device of interest. Here, for example, it is determined that mobile device <b>101</b> and cloud server <b>105</b> are the devices of interest (e.g., devices that generate traffic for the SDTM service). It is contemplated herein that other devices may be selected, such as the other devices of system <b>100</b>. The devices of interest may be determined based on multiple factors. Factors include the events of step <b>142</b> or step <b>143</b>, or otherwise disclosed herein. Another exemplary factor may include a determination of the location, such as farthest device closest to the originator of traffic that has the device capabilities (e.g., processor speed, memory amount, bandwidth of network connection, power to the device, etc.) of creating a VM for test traffic or generating test traffic. Another example, with regard to location, may be associated with the base station in which mobile device is connected or not connected with. Another factor may be based on the intersection of complaints (or detected errors) associated with a plurality of users. For example, base station <b>103</b> may be selected over mobile device <b>101</b> based on an intersection of complaints (e.g., the device that is commonly involved in different situations) or device capability.

With continued reference to <figref idref="DRAWINGS">FIG. 4</figref>, at step <b>145</b> and step <b>146</b>, server <b>114</b> may send a message to cloud server <b>105</b> or may send a message to mobile device <b>101</b> to create VM <b>104</b> of cloud server <b>105</b> or VM <b>113</b> of mobile device <b>101</b> for generating or processing test traffic. Scenarios are contemplated herein in which VM <b>113</b> may be created particularly for generating test traffic for the SDTM service, while cloud server <b>105</b> does not create another VM (e.g., uses a previously instantiated VM used for testing) or cloud server <b>105</b> processes messages from VM <b>113</b> as it would for any other device (e.g., a VM of cloud server <b>105</b> already serving real traffic and is not generally aware that it is test traffic). At this step <b>145</b> or step <b>146</b>, server <b>115</b> may also provide instructions for the created VMS to mark the test traffic in order to recognize it at a later point in time (e.g., diagnosis at step <b>148</b>). In addition, server <b>114</b> may provide instructions to create VM or generate test traffic during a particular period. The particular period may be a period of relatively low network traffic or device usage, in order to minimize impact to a user. Or the particular period may be period of relatively high traffic or device usage, in order to more effectively diagnose problems that occur during those periods of relatively high traffic or device usage.

At step <b>147</b>, tests (e.g., generation of traffic and monitoring results) may occur between mobile device <b>101</b> and cloud server <b>105</b> for a period that may have been communicated at step <b>145</b> or step <b>146</b>. It is contemplated herein per-hop one-way active or passive performance measurements on each hop using the same ports and protocols as in ordinary traffic (e.g., simulate traffic that is processed as normal, but measured more discretely). At step <b>148</b>, server <b>114</b> may determine possible issues that may have caused a previous problem (e.g., problem experienced and reported by a user associated with mobile device <b>101</b>), may determine possible issues that may cause a problem for mobile device <b>101</b> (or cloud server <b>105</b>) in the future (e.g., after installation of a software update), or other indicators associated with health of the entire or subset of system <b>100</b>. Subsequently server <b>114</b> may provide instructions to display the determined results or transmit the results of the diagnosis of step <b>148</b> to a device.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates another exemplary method for implementation of SDTM. At step <b>151</b>, Openstack (or the like) may be used to instantiate virtual infrastructure (e.g., VMs) and inject or capture test traffic. For example, VMs and VNFs may be placed within mobile device <b>101</b>, base station <b>103</b>, router <b>111</b>, and desktop computer <b>109</b> for testing. This step <b>151</b> may be proactive testing of system <b>100</b> and may not be in response to a detected error. This method (or methods herein) may be a periodic (e.g., may occur at peak times or alternatively non-peak times). At step <b>152</b>, a library may be created for other VNFs to incorporate test traffic generation on command. For example, libraries to implement SDTM may be created in existing or new VNFs. At step <b>153</b>, vRouter (or the like) may separate test traffic (e.g., injected traffic) from real traffic (e.g., normal traffic from users). At step <b>154</b>, using instantiated VMs of step <b>152</b> in the context of SDTM to determine possible problems and suggest solutions (e.g., a configuration window may pop-up with a highlighted possible configuration at issue) or provide an indication that there are no detected problems. In other words, at step <b>154</b>, the health of system <b>100</b> may be determined and communicated.

It is contemplated herein that one or more steps of SDTM (e.g., <figref idref="DRAWINGS">FIG. 3</figref>, <figref idref="DRAWINGS">FIG. 4</figref>, or <figref idref="DRAWINGS">FIG. 5</figref>) may occur on one device or may be distributed across multiple devices. Exemplary devices that may execute the disclosed methods may include an operation, administration and maintenance (OAM) server, SDN controller, router, or switch, among other things. In an exemplary implementation, distributed processing and data structures or algorithms may be used to reduce the collection traffic.

<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram of network device <b>300</b> that may be connected to or comprise a component of system <b>100</b>. Network device <b>300</b> may comprise hardware or a combination of hardware and software. The functionality to facilitate telecommunications via a telecommunications network may reside in one or combination of network devices <b>300</b>. Network device <b>300</b> depicted in <figref idref="DRAWINGS">FIG. 6</figref> may represent or perform functionality of an appropriate network device <b>300</b>, or combination of network devices <b>300</b>, such as, for example, a component or various components of a cellular broadcast system wireless network, a processor, a server, a gateway, a node, a mobile switching center (MSC), a short message service center (SMSC), an automatic location function server (ALFS), a gateway mobile location center (GMLC), a radio access network (RAN), a serving mobile location center (SMLC), or the like, or any appropriate combination thereof. It is emphasized that the block diagram depicted in <figref idref="DRAWINGS">FIG. 6</figref> is exemplary and not intended to imply a limitation to a specific implementation or configuration. Thus, network device <b>300</b> may be implemented in a single device or multiple devices (e.g., single server or multiple servers, single gateway or multiple gateways, single controller or multiple controllers). Multiple network entities may be distributed or centrally located. Multiple network entities may communicate wirelessly, via hard wire, or any appropriate combination thereof.

Network device <b>300</b> may comprise a processor <b>302</b> and a memory <b>304</b> coupled to processor <b>302</b>. Memory <b>304</b> may contain executable instructions that, when executed by processor <b>302</b>, cause processor <b>302</b> to effectuate operations associated with mapping wireless signal strength. As evident from the description herein, network device <b>300</b> is not to be construed as software per se.

In addition to processor <b>302</b> and memory <b>304</b>, network device <b>300</b> may include an input/output system <b>306</b>. Processor <b>302</b>, memory <b>304</b>, and input/output system <b>306</b> may be coupled together (coupling not shown in <figref idref="DRAWINGS">FIG. 6</figref>) to allow communications between them. Each portion of network device <b>300</b> may comprise circuitry for performing functions associated with each respective portion. Thus, each portion may comprise hardware, or a combination of hardware and software. Accordingly, each portion of network device <b>300</b> is not to be construed as software per se. Input/output system <b>306</b> may be capable of receiving or providing information from or to a communications device or other network entities configured for telecommunications. For example input/output system <b>306</b> may include a wireless communications (e.g., 3G/4G/GPS) card. Input/output system <b>306</b> may be capable of receiving or sending video information, audio information, control information, image information, data, or any combination thereof. Input/output system <b>306</b> may be capable of transferring information with network device <b>300</b>. In various configurations, input/output system <b>306</b> may receive or provide information via any appropriate means, such as, for example, optical means (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi, Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone, ultrasonic receiver, ultrasonic transmitter), or a combination thereof. In an example configuration, input/output system <b>306</b> may comprise a Wi-Fi finder, a two-way GPS chipset or equivalent, or the like, or a combination thereof.

Input/output system <b>306</b> of network device <b>300</b> also may contain a communication connection <b>308</b> that allows network device <b>300</b> to communicate with other devices, network entities, or the like. Communication connection <b>308</b> may comprise communication media. Communication media typically embody computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, or wireless media such as acoustic, RF, infrared, or other wireless media. The term computer-readable media as used herein includes both storage media and communication media. Input/output system <b>306</b> also may include an input device <b>310</b> such as keyboard, mouse, pen, voice input device, or touch input device. Input/output system <b>306</b> may also include an output device <b>312</b>, such as a display, speakers, or a printer.

Processor <b>302</b> may be capable of performing functions associated with telecommunications, such as functions for processing broadcast messages, as described herein. For example, processor <b>302</b> may be capable of, in conjunction with any other portion of network device <b>300</b>, determining a type of broadcast message and acting according to the broadcast message type or content, as described herein.

Memory <b>304</b> of network device <b>300</b> may comprise a storage medium having a concrete, tangible, physical structure. As is known, a signal does not have a concrete, tangible, physical structure. Memory <b>304</b>, as well as any computer-readable storage medium described herein, is not to be construed as a signal. Memory <b>304</b>, as well as any computer-readable storage medium described herein, is not to be construed as a transient signal. Memory <b>304</b>, as well as any computer-readable storage medium described herein, is not to be construed as a propagating signal. Memory <b>304</b>, as well as any computer-readable storage medium described herein, is to be construed as an article of manufacture.

Memory <b>304</b> may store any information utilized in conjunction with telecommunications. Depending upon the exact configuration or type of processor, memory <b>304</b> may include a volatile storage <b>314</b> (such as some types of RAM), a nonvolatile storage <b>316</b> (such as ROM, flash memory), or a combination thereof. Memory <b>304</b> may include additional storage (e.g., a removable storage <b>318</b> or a non-removable storage <b>320</b>) including, for example, tape, flash memory, smart cards, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, USB-compatible memory, or any other medium that can be used to store information and that can be accessed by network device <b>300</b>. Memory <b>304</b> may comprise executable instructions that, when executed by processor <b>302</b>, cause processor <b>302</b> to effectuate operations to map signal strengths in an area of interest.

<figref idref="DRAWINGS">FIG. 7</figref> depicts an exemplary diagrammatic representation of a machine in the form of a computer system <b>500</b> within which a set of instructions, when executed, may cause the machine to perform any one or more of the methods described above. One or more instances of the machine can operate, for example, as processor <b>302</b>, mobile device <b>101</b>, server <b>114</b>, cloud server <b>105</b>, switch <b>107</b>, and other devices of <figref idref="DRAWINGS">FIG. 2</figref>. In some embodiments, the machine may be connected (e.g., using a network <b>100</b>) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client user machine in a server-client user network environment, or as a peer machine in a peer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet, a smart phone, a laptop computer, a desktop computer, a control system, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. It will be understood that a communication device of the subject disclosure includes broadly any electronic device that provides voice, video or data communication. Further, while a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods discussed herein.

Computer system <b>500</b> may include a processor (or controller) <b>504</b> (e.g., a central processing unit (CPU)), a graphics processing unit (GPU, or both), a main memory <b>506</b> and a static memory <b>508</b>, which communicate with each other via a bus <b>510</b>. The computer system <b>500</b> may further include a display unit <b>512</b> (e.g., a liquid crystal display (LCD), a flat panel, or a solid state display). Computer system <b>500</b> may include an input device <b>514</b> (e.g., a keyboard), a cursor control device <b>516</b> (e.g., a mouse), a disk drive unit <b>518</b>, a signal generation device <b>520</b> (e.g., a speaker or remote control) and a network interface device <b>522</b>. In distributed environments, the embodiments described in the subject disclosure can be adapted to utilize multiple display units <b>512</b> controlled by two or more computer systems <b>500</b>. In this configuration, presentations described by the subject disclosure may in part be shown in a first of display units <b>512</b>, while the remaining portion is presented in a second of display units <b>512</b>.

The disk drive unit <b>518</b> may include a tangible computer-readable storage medium <b>524</b> on which is stored one or more sets of instructions (e.g., software <b>526</b>) embodying any one or more of the methods or functions described herein, including those methods illustrated above. Instructions <b>526</b> may also reside, completely or at least partially, within main memory <b>506</b>, static memory <b>508</b>, or within processor <b>504</b> during execution thereof by the computer system <b>500</b>. Main memory <b>506</b> and processor <b>504</b> also may constitute tangible computer-readable storage media.

<figref idref="DRAWINGS">FIG. 8A</figref> is a representation of an exemplary network <b>600</b>. Network <b>600</b> (e.g., system <b>100</b>) may comprise an SDN—that is, network <b>600</b> may include one or more virtualized functions implemented on general purpose hardware, such as in lieu of having dedicated hardware for every network function. That is, general purpose hardware of network <b>600</b> may be configured to run virtual network elements to support communication services, such as mobility services, including consumer services and enterprise services. These services may be provided or measured in sessions.

A virtual network functions (VNFs) <b>602</b> may be able to support a limited number of sessions. Each VNF <b>602</b> may have a VNF type that indicates its functionality or role. For example, <figref idref="DRAWINGS">FIG. 8A</figref> illustrates a gateway VNF <b>602</b><i>a </i>and a policy and charging rules function (PCRF) VNF <b>602</b><i>b</i>. Additionally or alternatively, VNFs <b>602</b> may include other types of VNFs. Each VNF <b>602</b> may use one or more virtual machines (VMs) <b>604</b> to operate. Each VM <b>604</b> may have a VM type that indicates its functionality or role. For example, <figref idref="DRAWINGS">FIG. 8A</figref> illustrates a management control module (MCM) VM <b>604</b><i>a</i>, an advanced services module (ASM) VM <b>604</b><i>b</i>, and a DEP VM <b>604</b><i>c</i>. Additionally or alternatively, VMs <b>604</b> may include other types of VMs. Each VM <b>604</b> may consume various network resources from a hardware platform <b>606</b>, such as a resource <b>608</b>, a virtual central processing unit (vCPU) <b>608</b><i>a</i>, memory <b>608</b><i>b</i>, or a network interface card (NIC) <b>608</b><i>c</i>. Additionally or alternatively, hardware platform <b>606</b> may include other types of resources <b>608</b>.

While <figref idref="DRAWINGS">FIG. 8A</figref> illustrates resources <b>608</b> as collectively contained in hardware platform <b>606</b>, the configuration of hardware platform <b>606</b> may isolate, for example, certain memory <b>608</b><i>c </i>from other memory <b>608</b><i>c</i>. <figref idref="DRAWINGS">FIG. 8B</figref> provides an exemplary implementation of hardware platform <b>606</b>.

Hardware platform <b>606</b> may comprise one or more chasses <b>610</b>. Chassis <b>610</b> may refer to the physical housing or platform for multiple servers or other network equipment. In an aspect, chassis <b>610</b> may also refer to the underlying network equipment. Chassis <b>610</b> may include one or more servers <b>612</b>. Server <b>612</b> may comprise general purpose computer hardware or a computer. In an aspect, chassis <b>610</b> may comprise a metal rack, and servers <b>612</b> of chassis <b>610</b> may comprise blade servers that are physically mounted in or on chassis <b>610</b>.

Each server <b>612</b> may include one or more network resources <b>608</b>, as illustrated. Servers <b>612</b> may be communicatively coupled together (not shown) in any combination or arrangement. For example, all servers <b>612</b> within a given chassis <b>610</b> may be communicatively coupled. As another example, servers <b>612</b> in different chasses <b>610</b> may be communicatively coupled. Additionally or alternatively, chasses <b>610</b> may be communicatively coupled together (not shown) in any combination or arrangement.

The characteristics of each chassis <b>610</b> and each server <b>612</b> may differ. For example, <figref idref="DRAWINGS">FIG. 8B</figref> illustrates that the number of servers <b>612</b> within two chasses <b>610</b> may vary. Additionally or alternatively, the type or number of resources <b>610</b> within each server <b>612</b> may vary. In an aspect, chassis <b>610</b> may be used to group servers <b>612</b> with the same resource characteristics. In another aspect, servers <b>612</b> within the same chassis <b>610</b> may have different resource characteristics.

Given hardware platform <b>606</b>, the number of sessions that may be instantiated may vary depending upon how efficiently resources <b>608</b> are assigned to different VMs <b>604</b>. For example, assignment of VMs <b>604</b> to particular resources <b>608</b> may be constrained by one or more rules. For example, a first rule may require that resources <b>608</b> assigned to a particular VM <b>604</b> be on the same server <b>612</b> or set of servers <b>612</b>. For example, if VM <b>604</b> uses eight vCPUs <b>608</b><i>a, </i>1 GB of memory <b>608</b><i>b</i>, and 2 NICs <b>608</b><i>c</i>, the rules may require that all of these resources <b>608</b> be sourced from the same server <b>612</b>. Additionally or alternatively, VM <b>604</b> may require splitting resources <b>608</b> among multiple servers <b>612</b>, but such splitting may need to conform with certain restrictions. For example, resources <b>608</b> for VM <b>604</b> may be able to be split between two servers <b>612</b>. Default rules may apply. For example, a default rule may require that all resources <b>608</b> for a given VM <b>604</b> must come from the same server <b>612</b>.

An affinity rule may restrict assignment of resources <b>608</b> for a particular VM <b>604</b> (or a particular type of VM <b>604</b>). For example, an affinity rule may require that certain VMs <b>604</b> be instantiated on (that is, consume resources from) the same server <b>612</b> or chassis <b>610</b>. For example, if VNF <b>602</b> uses six MCM VMs <b>604</b><i>a</i>, an affinity rule may dictate that those six MCM VMs <b>604</b><i>a </i>be instantiated on the same server <b>612</b> (or chassis <b>610</b>). As another example, if VNF <b>602</b> uses MCM VMs <b>604</b><i>a</i>, ASM VMs <b>604</b><i>b</i>, and a third type of VMs <b>604</b>, an affinity rule may dictate that at least the MCM VMs <b>604</b><i>a </i>and the ASM VMs <b>604</b><i>b </i>be instantiated on the same server <b>612</b> (or chassis <b>610</b>). Affinity rules may restrict assignment of resources <b>608</b> based on the identity or type of resource <b>608</b>, VNF <b>602</b>, VM <b>604</b>, chassis <b>610</b>, server <b>612</b>, or any combination thereof.

An anti-affinity rule may restrict assignment of resources <b>608</b> for a particular VM <b>604</b> (or a particular type of VM <b>604</b>). In contrast to an affinity rule—which may require that certain VMs <b>604</b> be instantiated on the same server <b>612</b> or chassis <b>610</b>—an anti-affinity rule requires that certain VMs <b>604</b> be instantiated on different servers <b>612</b> (or different chasses <b>610</b>). For example, an anti-affinity rule may require that MCM VM <b>604</b><i>a </i>be instantiated on a particular server <b>612</b> that does not contain any ASM VMs <b>604</b><i>b</i>. As another example, an anti-affinity rule may require that MCM VMs <b>604</b><i>a </i>for a first VNF <b>602</b> be instantiated on a different server <b>612</b> (or chassis <b>610</b>) than MCM VMs <b>604</b><i>a </i>for a second VNF <b>602</b>. Anti-affinity rules may restrict assignment of resources <b>608</b> based on the identity or type of resource <b>608</b>, VNF <b>602</b>, VM <b>604</b>, chassis <b>610</b>, server <b>612</b>, or any combination thereof.

Within these constraints, resources <b>608</b> of hardware platform <b>606</b> may be assigned to be used to instantiate VMs <b>604</b>, which in turn may be used to instantiate VNFs <b>602</b>, which in turn may be used to establish sessions. The different combinations for how such resources <b>608</b> may be assigned may vary in complexity and efficiency. For example, different assignments may have different limits of the number of sessions that can be established given a particular hardware platform <b>606</b>.

For example, consider a session that may require gateway VNF <b>602</b><i>a </i>and PCRF VNF <b>602</b><i>b</i>. Gateway VNF <b>602</b><i>a </i>may require five VMs <b>604</b> instantiated on the same server <b>612</b>, and PCRF VNF <b>602</b><i>b </i>may require two VMs <b>604</b> instantiated on the same server <b>612</b>. (Assume, for this example, that no affinity or anti-affinity rules restrict whether VMs <b>604</b> for PCRF VNF <b>602</b><i>b </i>may or must be instantiated on the same or different server <b>612</b> than VMs <b>604</b> for gateway VNF <b>602</b><i>a</i>.) In this example, each of two servers <b>612</b> may have sufficient resources <b>608</b> to support 10 VMs <b>604</b>. To implement sessions using these two servers <b>612</b>, first server <b>612</b> may be instantiated with 10 VMs <b>604</b> to support two instantiations of gateway VNF <b>602</b><i>a</i>, and second server <b>612</b> may be instantiated with 9 VMs: five VMs <b>604</b> to support one instantiation of gateway VNF <b>602</b><i>a </i>and four VMs <b>604</b> to support two instantiations of PCRF VNF <b>602</b><i>b</i>. This may leave the remaining resources <b>608</b> that could have supported the tenth VM <b>604</b> on second server <b>612</b> unused (and unusable for an instantiation of either a gateway VNF <b>602</b><i>a </i>or a PCRF VNF <b>602</b><i>b</i>). Alternatively, first server <b>612</b> may be instantiated with 10 VMs <b>604</b> for two instantiations of gateway VNF <b>602</b><i>a </i>and second server <b>612</b> may be instantiated with 10 VMs <b>604</b> for five instantiations of PCRF VNF <b>602</b><i>b</i>, using all available resources <b>608</b> to maximize the number of VMs <b>604</b> instantiated.

Consider, further, how many sessions each gateway VNF <b>602</b><i>a </i>and each PCRF VNF <b>602</b><i>b </i>may support. This may factor into which assignment of resources <b>608</b> is more efficient. For example, consider if each gateway VNF <b>602</b><i>a </i>supports two million sessions, and if each PCRF VNF <b>602</b><i>b </i>supports three million sessions. For the first configuration—three total gateway VNFs <b>602</b><i>a </i>(which satisfy the gateway requirement for six million sessions) and two total PCRF VNFs <b>602</b><i>b </i>(which satisfy the PCRF requirement for six million sessions)—would support a total of six million sessions. For the second configuration—two total gateway VNFs <b>602</b><i>a </i>(which satisfy the gateway requirement for four million sessions) and five total PCRF VNFs <b>602</b><i>b </i>(which satisfy the PCRF requirement for 15 million sessions)—would support a total of four million sessions. Thus, while the first configuration may seem less efficient looking only at the number of available resources <b>608</b> used (as resources <b>608</b> for the tenth possible VM <b>604</b> are unused), the second configuration is actually more efficient from the perspective of being the configuration that can support more the greater number of sessions.

To solve the problem of determining a capacity (or, number of sessions) that can be supported by a given hardware platform <b>605</b>, a given requirement for VNFs <b>602</b> to support a session, a capacity for the number of sessions each VNF <b>602</b> (e.g., of a certain type) can support, a given requirement for VMs <b>604</b> for each VNF <b>602</b> (e.g., of a certain type), a give requirement for resources <b>608</b> to support each VM <b>604</b> (e.g., of a certain type), rules dictating the assignment of resources <b>608</b> to one or more VMs <b>604</b> (e.g., affinity and anti-affinity rules), the chasses <b>610</b> and servers <b>612</b> of hardware platform <b>606</b>, and the individual resources <b>608</b> of each chassis <b>610</b> or server <b>612</b> (e.g., of a certain type), an integer programming problem may be formulated.

As described herein, a telecommunications system wherein management and control utilizing a software designed network (SDN) and a simple IP are based, at least in part, on user equipment, may provide a wireless management and control framework that enables common wireless management and control, such as mobility management, radio resource management, QoS, load balancing, etc., across many wireless technologies, e.g. LTE, Wi-Fi, and future 5G access technologies; decoupling the mobility control from data planes to let them evolve and scale independently; reducing network state maintained in the network based on user equipment types to reduce network cost and allow massive scale; shortening cycle time and improving network upgradability; flexibility in creating end-to-end services based on types of user equipment and applications, thus improve customer experience; or improving user equipment power efficiency and battery life—especially for simple M2M devices—through enhanced wireless management.

While examples of a telecommunications system in which diagnostic traffic generation for automatic testing and troubleshooting may be processed and managed have been described in connection with various computing devices/processors, the underlying concepts may be applied to any computing device, processor, or system capable of facilitating a telecommunications system. The various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the methods and devices may take the form of program code (i.e., instructions) embodied in concrete, tangible, storage media having a concrete, tangible, physical structure. Examples of tangible storage media include floppy diskettes, CD-ROMs, DVDs, hard drives, or any other tangible machine-readable storage medium (computer-readable storage medium). Thus, a computer-readable storage medium is not a signal. A computer-readable storage medium is not a transient signal. Further, a computer-readable storage medium is not a propagating signal. A computer-readable storage medium as described herein is an article of manufacture. When the program code is loaded into and executed by a machine, such as a computer, the machine becomes a device for telecommunications. In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile or nonvolatile memory or storage elements), at least one input device, and at least one output device. The program(s) can be implemented in assembly or machine language, if desired. The language can be a compiled or interpreted language, and may be combined with hardware implementations.

The methods and devices associated with a telecommunications system as described herein also may be practiced via communications embodied in the form of program code that is transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via any other form of transmission, wherein, when the program code is received and loaded into and executed by a machine, such as an EPROM, a gate array, a programmable logic device (PLD), a client computer, or the like, the machine becomes a device for implementing telecommunications as described herein. When implemented on a general-purpose processor, the program code combines with the processor to provide a unique device that operates to invoke the functionality of a telecommunications system.

While a telecommunications system has been described in connection with the various examples of the various figures, it is to be understood that other similar implementations may be used or modifications and additions may be made to the described examples of a telecommunications system without deviating therefrom. For example, one skilled in the art will recognize that a telecommunications system as described in the instant application may apply to any environment, whether wired or wireless, and may be applied to any number of such devices connected via a communications network and interacting across the network. Therefore, a telecommunications system as described herein should not be limited to any single example, but rather should be construed in breadth and scope in accordance with the appended claims.

In describing preferred methods, systems, or apparatuses of the subject matter of the present disclosure—diagnostic traffic generation for automatic testing and troubleshooting—as illustrated in the Figures, specific terminology is employed for the sake of clarity. The claimed subject matter, however, is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to accomplish a similar purpose. In addition, the use of the word “or” is generally used inclusively unless otherwise provided herein. It is contemplated that steps of <figref idref="DRAWINGS">FIG. 3</figref>, <figref idref="DRAWINGS">FIG. 4</figref>, or <figref idref="DRAWINGS">FIG. 5</figref>, for example, may be skipped or combined.

This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to practice the invention, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art (e.g., skipping steps, combining steps, or adding steps between exemplary methods disclosed herein). Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.