TECHNICAL FIELD

[0001] This application relates generally to computer technology, including but not limited to methods and systems for simulating network impairments for testing network- enabled applications.

BACKGROUND

[0002] Streaming media systems have evolved techniques for addressing network impairments caused by congestion, physics, and various physical layer protocol

idiosyncrasies. Examples of such techniques include buffering, dynamic bitrate adaptation, and other congestion management techniques. Real time interactive streaming, for fields such as cloud gaming, introduces various constraints that differ from those caused by streaming for passive consumption. As such, determining the efficacy of congestion management techniques for real time interactive streaming applications is extremely difficult due to the many variables at play, both with the various network impairments as well as the interactive nature of the application.

[0003] One technique for testing streaming media systems involves the use of simulated networks. However, not only is it very difficult to accurately simulate real-world communication networks, it is also challenging to design simulations that yield reproducible results.

SUMMARY

[0004] The implementations described in this specification are directed to developing real time interactive streaming applications by using a simulated test network embodying dynamic real-world impairments.

[0005] In some implementations, a network simulator is presented, governed by a set of simulation scenarios. A traffic generator emulates a real-time encoder with controls for emulating target bitrates, error correction and related variables to create traffic similar to what would be generated by an equivalent real time video encoder. A developer client receives traffic generated from the traffic generator. The traffic traverses the network simulator on its way to the developer client. The developer client participates in a protocol to actively record the traffic. A congestion management algorithm interfaces to the traffic generator, modulating its behavior based on the feedback from the developer client.

[0006] The described implementations allow developers of real time streaming applications to predict how a particular application will perform over varying types of real world network conditions. The described implementations have an advantage of providing accurate performance evaluations by reproducing real world network impairments, but with the convenience of a lab environment.

[0007] In accordance with some implementations, a method is performed at an electronic device having one or more processors and memory storing one or more programs for execution by the one or more processors. The method includes: obtaining a first network simulation scenario selected from a plurality of predefined network simulation scenarios, each of the network simulation scenarios embodying a specific combination of dynamic network parameters, wherein the dynamic network parameters for a respective predefined simulation scenario are based on measurements of a real world communication environment corresponding to the respective simulation scenario; executing a network-enabled test application; encoding a video stream associated with a plurality of specific operations of the network-enabled test application; simulating transmission of the encoded video stream in a simulated test network for the first network simulation scenario with associated first dynamic network parameters; generating a filtered data stream that reflects simulated real time effects of the simulated test network on transmission of the encoded data stream based on the first dynamic network parameters; and determining a plurality of time-varying quality metrics for the filtered data stream.

[0008] In accordance with some implementations, a method is performed at an electronic device having one or more processors and memory storing one or more programs for execution by the one or more processors. The method includes: obtaining a network- enabled test application; displaying, in a first user interface of the computing system, a plurality of affordances associated with a respective one of a plurality of predefined network simulation scenarios, each of the network simulation scenarios embodying a specific combination of dynamic network parameters, wherein the dynamic network parameters for a respective predefined simulation scenario are based on measurements of a real world communication environment corresponding to the respective simulation scenario; receiving a user selection of a first affordance associated with a first network simulation scenario; and in response to the user selection of the first affordance: encoding a video stream associated with a plurality of specific operations of the network-enabled test application; simulating transmission of the encoded video stream in a simulated test network for the first network simulation scenario with associated first dynamic network parameters; determining one or more performance aspects of the network-enabled test application based on a plurality of time-varying quality metrics for the filtered data stream; and associating the one or more performance aspects of the network-enabled test application with the first simulation scenario.

[0009] In accordance with some implementations, an electronic device includes one or more processors and memory storing one or more programs to be executed by the one or more processors. The one or more programs include instructions for performing any of the methods described above. In accordance with some implementations, a non-transitory computer-readable storage medium stores one or more programs, the one or more programs include instructions, which, when executed by an electronic device with one or more processors, cause the electronic device to perform any of the methods described above.

BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure l is a block diagram illustrating an example interactive streaming environment in accordance with some implementations.

[0011] Figure 2 is a block diagram illustrating an example test environment in accordance with some implementations.

[0012] Figure 3 is a block diagram illustrating an example developer console in accordance with some embodiments.

[0013] Figures 4A-4F are block diagrams illustrating an example simulation environment in accordance with some implementations.

[0014] Figures 5A-5C are graphs of example network impairments in accordance with some implementations.

[0015] Figures 6A-6D illustrate example user interfaces in accordance with some implementations.

[0016] Figure 7 is a flow diagram illustrating an example method for tracking a simulated user experience in accordance with some implementations. [0017] Figure 8 is a flow diagram illustrating an example method for tracking a simulated user experience in accordance with some implementations.

[0018] Figure 9 is a flow diagram illustrating an example method for deriving parameters for simulation scenarios in accordance with some implementations.

[0019] Like reference numerals refer to corresponding parts throughout the drawings.

DESCRIPTION OF IMPLEMENTATIONS

[0020] In various implementations described in this application, a testing environment includes a network simulator including a plurality of simulation scenarios. Each simulation scenario embodies a specific combination of dynamic network parameters, and the dynamic network parameters for a respective simulation scenario are based on measurements of a real world communication environment corresponding to the respective simulation scenario.

When a network-enabled test application is executed in the test environment, an output data stream from the test application is transmitted through the network simulator, where it is exposed to impairments associated with the dynamic network parameters. A developer client receives the resulting impaired data stream and determines a plurality of time-varying quality metrics for the test application, where the quality metrics are specific to a respective simulation scenario. In this manner, a simulated user experience can be determined based on real world network conditions, in the convenience of a lab environment.

[0021] Figure 1 is an example interactive streaming environment 100 in accordance with some implementations. The interactive streaming environment 100 includes a client device 102 and an optional media device 106 on a local network 110. In some

implementations, the local network 110 supports wired (e.g., Ethernet) and/or wireless (e.g., Wi-Fi) communications. For example, the local network 110 includes a router device that networks one or more devices into the local network 110. The local network 110 is communicatively coupled to communication networks 112 (e.g., wide-area networks, the internet). Alternatively, the client device 102 and/or media device 106 are communicatively coupled to communications networks 112, without an intermediary local network 110.

[0022] In some implementations, the client device 102 and the media device 106 are communicatively coupled. The client device 102 and the media device 106 may communicate with each other through the local network 110 and/or directly (e.g., via Bluetooth or other wireless communications). In some implementations, the client device 102 and the media device 106 are local to each other (e.g., in the same room, in the same house, etc.). The media device 106 is coupled to one or more output devices 108 that output visual and/or audio content (e.g., a television, a display monitor, a sound system, speakers, etc.). In some implementations, the media device 106 is a casting device (e.g., CHROMECAST by Google Inc.) or a device that otherwise includes casting functionality.

[0023] The client device 102 is a device that includes, and can run, one or more applications. In some implementations, the client device 102 is a smartphone, tablet device, a laptop or notebook computer, a desktop computer, or a multimedia device.

[0024] In some implementations, the client device 102 includes one or more applications that are configured to operate in conjunction with the media device 106. In some implementations, the applications include a media device application for pairing the client device 102 with the media device 106 and configuring the media device 106. The

applications also include one or more applications that cast associated content to the media device 106. In some implementations, an application casts data and/or content to the media device 106 by sending the data/content directly to the media device 106 (e.g., via the local network 110) and/or by directing the media device 106 to a remote location (e.g., a Universal Resource Locator (“URL”) or other link to a location at a server system) from which the media device 106 can stream or otherwise receive data/content. The media device 106 receives data/content from the application and/or the remote location and outputs visual and/or audio content corresponding to the received data/content to the output device 108.

[0025] In the interactive streaming environment 100, a user of the client device 102

(hereinafter“user”) starts a streaming session (e.g., a game) by launching a streaming application (e.g., a game application) for execution at the client device 102. The executing streaming application communicates with a server 114 to establish a session. In some implementations, the user instructs the streaming application to communicate with the media device 106 to direct the media device 106 to receive data associated with the streaming session for outputting. For these implementations, a session is established between the streaming application, the remote server 114, and the media device 106.

[0026] The user of the client device 102 optionally invites additional users to join the session (e.g., the first player invites other players to join the game). An identifier of the session is presented to users of one or more client devices 104. In some implementations, the session identifier is or otherwise includes an internet link (e.g., a Universal Resource Locator (“URL”)) in a notification. If an additional user opens the notification, the user may access the session identifier directly from the notification or activate an affordance to display the session identifier (e.g., in another application). The additional user(s) then join the session upon accessing the session identifier. Specifically, when the session identifier is used at a client 104 (e.g., the session identifier link is activated), the client 104 communicates with the server 114 in order to join the session. After the client 104 joins the session, the users at clients 102 and 104 can participate in the streaming session (e.g., play the game) by, for example, making inputs that affect the output of the session.

[0027] In some implementations, if the additional client 104 is already on the local network 110 of the first client 102, communications between the server 114 and the additional client 104 go through the local network 110. If the additional client 104 is not on the local network 110, communications between the server 114 and the additional client 104 go through a different connection (e.g., through communication network(s) 112).

[0028] In some implementations, as part of the process of a client 102/104 joining the session, the server 114 accesses the capabilities of the client 102/104 and/or a quality of the communicative connection between the server 114 and the client 102/104. In some implementations, the server 114 measures network latency between the client 102/104 and the server 114. If the measured latency is above a threshold and a lower-latency connection is available, the server 114 suggests that the client 102/104 change to the lower latency connection, or invite the user of the client 102/104 to change the client 102/104 to the lower latency connection. For example, if the client 104 is on a cellular wireless connection 112, and the local network 110 is available, the server 114 suggests that the client 104 should connect through the local network 110.

[0029] In some implementations, the latency threshold requirements differ between streaming applications. For example, some streaming applications (e.g., action games) are best experienced on lower latency connections, and some other streaming applications (e.g., online board games or card games) are not as demanding with respect to latency, and the server 114 may make connection recommendations in view of these different requirements.

[0030] In some implementations, a streaming application requires a companion application associated with the streaming application. For implementations in which the streaming application is a game application, a companion application is a virtual game controller application for controlling gameplay. In some implementations, the server 114 communicates with the client 102/104 to set up a virtual game controller on the player client 102/104. In some implementations, the server 114 assesses whether the client 102/104 has the needed resources for the virtual game controller (e.g., whether the client 102/104 has an application needed to implement the virtual game controller and/or whether the

communicative connection between the client 102/104 and the server 114 has a latency that is appropriate for the game session). Depending on the available resources at the client 102/104, the connection quality, and the requirements for the game, the virtual game controller may be implemented differently at the client 102/104 (e.g., for situations in which connection quality is low the virtual game controller is implemented as a streamlined version including fewer features).

[0031] In some implementations, the client 102/104 accesses the streaming application and/or the companion application with a webpage-based interface. For example, a virtual game controller interface for a game may be embedded in a webpage, and the webpage is rendered in a web browser on the client 102/104. If a webpage-based controller interface is the controller of choice for the session, the server 114 transmits the control interface webpage to the client 102/104 when the client 102/104 joins the session.

[0032] Figure 2 is a block diagram illustrating an example test environment 200 in accordance with some implementations. The test environment 200 includes a developer console 210 and a simulation environment 230.

[0033] In some implementations, the developer console 210 includes an input/output

(I/O) interface 220, which includes input device(s) 222 (e.g., a keyboard and/or mouse) and output device(s) 224 (e.g., a display) for facilitating interaction between the developer console 210 and a developer (or any other user of the developer console 210). The developer console 210 further includes memory 216, one or more processors 214 (referred to herein as central processing units (CPUs)), and a communication interface 212 for interfacing with the simulation environment 230 (e.g., through channel 213). In some implementations, the simulation environment 230 includes a communication interface 232 for interfacing with the developer console 210, one or more CPUs 234, memory 236, and a simulation module 240. The simulation module 240 includes a client module 242, a test application (“test app”) module 244, and a network simulator 246.

[0034] The client module 242 supplies a stream 243 of input data (e.g., simulating input data generated by a user of client device 102, Figure 1). The input data stream 243 from client module 242 is supplied to the test app module 244, where it affects output data 245 from the application being tested (e.g., session output from server 114, Figure 1). The output data 245 (e.g., a video stream or an encoded video stream) from the test app module 244 is transmitted through the network simulator 246, where it is subjected to various impairments, as described in more detail below. The impaired output stream 247 from the network simulator is transmitted to the developer console 210 through the communication interfaces 212 and 232, and displayed on an output device 224. In some implementations, CPU 214 derives quality metrics from the impaired output stream 247 and displays the quality metrics on an output device 224. In some implementations, an encoding module (e.g., 434, Figure 4A) adjusts a congestion management algorithm of the test app based on the quality metrics.

[0035] Figures 3 is a block diagram illustrating an example developer console 210 in accordance with some implementations. The developer console 210 includes one or more CPUs 214, one or more communication interfaces 212, memory 216, an I/O interface 220, and one or more communication buses 302 for interconnecting these components (sometimes called a chipset). The I/O interface 220 includes one or more input devices 222 (e.g., a keyboard, a mouse, a voice-command input unit or microphone, a touch screen display, a touch-sensitive input pad, a gesture capturing camera, or other input buttons or controls) and one or more output devices 224 (e.g., a visual display which enables presentation of user interfaces and display content), for facilitating interaction between the developer console 210 and a developer (or any other user of the developer console 210). In some implementations, the developer console 210 is implemented as a server that does not have an I/O interface 220, and instead client systems such as a mobile device or other client device (not shown) are used by developers and other people to access simulation data and/or other information stored in the developer console 210 (e.g., in memory 216) and to convey commands to the developer console 210 through the communication interface 212.

[0036] Memory 216 includes high-speed random access memory, such as DRAM,

SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 216, optionally, includes one or more storage devices remotely located from one or more processing units 214. Memory 216, or alternatively the non-volatile memory within memory 216, includes a non-transitory computer readable storage medium. In some implementations, memory 216, or the non- transitory computer readable storage medium of memory 216, stores the following programs, modules, and data structures, or a subset or superset thereof:

• Operating system 312 including procedures for handling various basic system services and for performing hardware dependent tasks;

• Communication module 314 for connecting the developer console to other devices (e.g., simulation environment 230) via one or more communication interfaces 212 (wired or wireless) and optionally one or more networks, such as the internet, other wide area networks, local area networks, metropolitan area networks, and so on;

• User interface module 316 for enabling presentation of information (e.g., a graphical user interface for presenting application(s), widgets, websites and web pages thereof, and/or application content, text, etc.) at the output device(s) 224 of the developer console 210;

• Settings input module 318 for prompting (e.g., through an output device 224) and accepting (e.g., through an input device 222) settings for the simulation module 240, including client settings, test app specifications, and simulation scenario settings;

• App controller module 320 for facilitating interactions between a developer and a specified companion application (e.g., a virtual game controller) for implementations in which the developer manually controls the test application (e.g., plays the game being tested); and

• Results output module 322 for determining quality metrics based on the impaired output stream and displaying results based on the quality metrics on an output device 224.

[0037] Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, modules or data structures, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 216, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 216, optionally, stores additional modules and data structures not described above.

[0038] Figures 4A is a block diagram illustrating an example simulation environment

230 in accordance with some implementations, and figures 4B-4F are block diagrams illustrating contents of various modules in figure 4A in accordance with some implementations. The simulation environment 230 includes one or more CPUs 234, one or more communication interfaces 212, memory 236, and one or more communication buses 402 for interconnecting these components (sometimes called a chipset). In some

implementations, the simulation environment 230 is implemented as a server.

[0039] Memory 236 includes high-speed random access memory, such as DRAM,

SRAM, DDR RAM, or other random access solid state memory devices; and, optionally, includes non-volatile memory, such as one or more magnetic disk storage devices, one or more optical disk storage devices, one or more flash memory devices, or one or more other non-volatile solid state storage devices. Memory 236, optionally, includes one or more storage devices remotely located from one or more processing units 234. Memory 236, or alternatively the non-volatile memory within memory 236, includes a non-transitory computer readable storage medium. In some implementations, memory 236, or the non- transitory computer readable storage medium of memory 236, stores the following programs, modules, and data structures, or a subset or superset thereof:

• Operating system 412 including procedures for handling various basic system services and for performing hardware dependent tasks;

• Communication module 414 for connecting the simulation environment to other

devices (e.g., developer console 210) via one or more communication interfaces 232 (wired or wireless) and optionally one or more networks, such as the internet, other wide area networks, local area networks, metropolitan area networks, and so on;

• Simulation module 240 for simulating user input, executing the test application, and simulating network impairments, the simulation module 240 including:

o Client module 242 for executing pre-defmed user inputs (e.g., entered by a simulated user) or manually entered user inputs (e.g., entered by the developer in the course of manually playing the game or otherwise controlling the test application), the client module 242 including:

a database, table, or other collection 422 of client programs, each client program including particular client settings 422-1 through 422-M (Figure 4B), where the settings for a particular client program include (i) an identifier of the particular client (e.g., Beginner, Novice, Expert, Custom- 1, Custom-2, etc.), and (ii) a particular sequence of commands representing simulated user inputs (e.g., run for w seconds, jump at x timestamp, fire weapon y at direction z at timestamp x+l, and so forth); and

a database, table, or other collection 424 of controller or companion programs (e.g., virtual game controller programs as described with reference to Figure 1), each controller program including particular settings 424-1 through 424-N (Figure 4C), where the settings for a particular controller or companion program include (i) an identifier of the particular program (e.g., Full Game Controller, Streamlined Game Controller, Media Buttons Set 1, Media Buttons Set 2, etc.), (ii) the inputs for each setting (e.g., joystick, up, down, button A, button B, accelerometer, etc.), (iii) a mapping of inputs to particular commands (e.g., button A is mapped to a jump command, button B is mapped to a fire command, etc.), and (iv) a controller layout (e.g., directional buttons on the left of a user interface, buttons A and B on the right the user interface, etc.);

Test application module 244 for providing server-side functionalities associated with test applications (e.g., game applications), including but not limited to storing application state data (e.g., game state data) and other application-related data, processing inputs (e.g., gameplay inputs) from client module 242, and rendering outputs (e.g., gameplay outputs), referred herein as an output data stream, the test application module 244 including:

a database, table, or other collection 432 of test applications (e.g., games to be tested) that, when run in the simulation environment by CPU(s) 234, are optionally controlled by input commands 422 from the client module 242 in order to produce an output data stream for encoding, each test application including particular settings and data corresponding to the test applications 432-1 through 432-P (Figure 4D), where the settings and data include: (i) an identifier of the particular test application, (ii) companion/controller settings for implementations in which the test application is configured to be controlled by a particular companion application; and (iii) congestion management algorithms (optionally included in encoding module 434) for adjusting encoder controls to account for varying network capacities; and

an encoder 434 with controls for emulating target bitrates, error correction, and related variables to encode the output data stream and transmit the output data stream to the network simulator 246; and Network simulator 246 for simulating real world network impairments (e.g., such as those present in local network 110 and/or communication network(s)

112, Figure 1) through which the encoded output data stream is transmitted on its way to the developer console 210, the network simulator 246 including: a database, table, or other collection 442 of simulation scenarios (described in more detail below), each simulation scenario including particular settings and data corresponding to the simulation scenario 442-1 through 442-Q (Figure 4E), where the settings and data include: (i) an identifier of the particular simulation scenario, (ii) commands associated with particular simulated impairments (e.g., one-way latency, round trip latency, jitter, packet loss, TCP retransmission, etc.), and (iii) a command recipe or sequence for executing the aforementioned commands in a time-based manner (described in more detail below with respect to Figure 5); and

a database, table, or other collection 444 of simulation data (described in more detail below with respect to Figures 6C-6D), where the simulation data 444-1 through 444-R (Figure 4F) represents results of analyses by the CPU(s) 234 for R simulations, where the simulation data includes: (i) scenario data identifying the particular simulation scenario that programmed or selected for the simulation, (ii) client data identifying the particular client program that was selected or the manual inputs that were received for the simulation, (iii) test app data identifying the application that had been tested for the simulation, (iv) the encoded output data stream (the output of test app module 244), (v) the impaired output data stream (the output of network simulator 246), (vi) events, flags, or other results of interest based on the analysis of the impaired data stream for display on an output device 224 (Figures 6C-6D), and (vii) a summary of the results of the simulation for

display on an output device 224 (Figures 6C-6D).

[0040] Figures 5A-5C are graphs of three impairments in an example command recipe 442-l(iii) in accordance with some implementations. Examples of network

impairments include, but are not limited to: one-way latency, round trip latency, jitter, packet loss, and TCP retransmission. The example command recipe 442-l(iii) includes a first impairment 510, a second impairment 520, and a third impairment 530. The command recipe dynamically varies each impairment over time, with to representing an initial time index with respect to a particular simulation (e.g., the beginning of the simulation), and ti through t ₇ representing subsequent time indices. At to, the first impairment 510 is at an initial level 512, the second impairment 520 is at an initial level 522, and the third impairment is at an initial level 532. Stated another way, a data stream transmitted through a network simulator 246 which is programmed to run a simulation scenario characterized by command recipe 442- l(iii) will be subjected to at least the three impairments 510, 520, and 530 at initial levels. For example, the data stream may be impaired by an initial level 512 of latency, an initial level 522 of jitter, and an initial level 532 of packet loss. At time t3, impairment 510 changes to an increased level 514, impairment 520 remains at the initial level 522, and impairment 530 changes to an increased level 534. At time ts, impairment 510 remains the same while impairment 520 changes to an increased level 526 and impairment 530 increases again to level 536. At time t ₇ , impairment 520 decreases to the initial level 522 while impairments 510 and 530 remain unchanged. In some implementations, changes in impairment levels take place at a microsecond level. For example, the amount of time between each time index in Figure 5 (e.g., from to to ti, ti to t2, and so forth) is one microsecond. In some

implementations, one or more changes in impairment levels take place in as little as less than a microsecond apart, and in as much as minutes apart.

[0041] The various network impairments are modeled off of real world network scenarios. For instance, impairment 510 may result from a person closing a door at time t3, thereby impeding a WiFi signal for as long as the door remains closed; impairment 520 may result from a person turning on a microwave at time ts, thereby impeding a WiFi signal until the microwave turns off at time t ₇ , at which time the impairment introduced by the microwave’s interference completely goes away; and impairment 530 may result from a person continuously walking away from a wireless router, thereby experiencing a decreased signal strength. By modeling the various impairments in each simulation scenario to simulate real world network scenarios with real world impairments (as described above), the simulation scenarios more realistically emulate real world environments. Further, by capturing the dynamic impairment changes in a static command recipe, each simulation scenario provides a reproducible sequence of dynamically changing impairments, thereby allowing for repeatable tests and reliable results when comparing different versions of the same test application. In other words, a developer testing an interactive network-enabled application (e.g., a cloud-based game) can be reassured that changes in results between tests are due to updates in the application itself, instead of variations in the testing environment.

[0042] Figures 6A-6D illustrate example user interfaces in accordance with some implementations. In some implementations, the various user interfaces described herein are configured (e.g., by user interface module 316) to be displayed on an output device 224 of the developer console 210.

[0043] Figure 6A depicts a simulation setup interface 600 which includes an affordance 602 for loading an application (432-1) for testing in the test environment 200, and a plurality of affordances 605a-j for selecting a particular simulation scenario (442-1 through 442-10). Upon selection of a test application and a particular simulation scenario, the user proceeds to run a simulation (444) using affordance 608.

[0044] Figure 6B depicts a playback interface 610 which includes a display area 612 for displaying the impaired data stream (444-l(v)) of the test application. In some

implementations, interface 610 shows the output data stream while the application is being tested, enabling substantially real time observations by the developer. Also included in interface 610 is a settings area 616 for displaying settings (444- 1 (i-iii)) related to the test application, and index area 614 for displaying a graphical depiction of various flags and/or events 6l5a-e of interest (444-l(vi)) as they relate to a timeline corresponding with the displayed output data stream, and/or an events area 618 for displaying a more comprehensive list of various flags and/or events of interest (444-l(vi)) as they are detected during the simulation.

[0045] Figure 6C depicts a results interface 620 which includes an events area 622 for displaying a list of various flags and/or events of interest (444-l(vi)) that were detected during the simulation, a summary area 624 for displaying a summary (444-l(vii)) of the results from the simulation, and snapshots 626 showing a plurality of image frames or subsets of image frames from the impaired output stream that are representative of respective events 444-l(vi). In some implementations, a reference frame is shown, having no visual artifacts as a result of impairments, in order to facilitate a comparison between an impaired frame and the nonimpaired reference frame. For example, snapshot 626-1 shows an image frame with no artifacts, which may be used as a reference frame. Snapshots 626-2, 626-3, and 626-4, on the other hand, each exhibit artifacts as a result of respective impairments 444-l(vi) from the simulation 432-1.

[0046] Figure 6D depicts a results interface 630 which includes a report area 632 for displaying a plurality of summaries (444-l(vi), 444-2(vi), 444-3(vi), and 444-4(vi)) from a plurality of respective simulations. Each summary includes or is otherwise associated with a details affordance 634 which provides access to a more detailed results interface (e.g., interface 620, Figure 6C) for each respective simulation.

[0047] The various affordances, elements, and areas displayed in the example user interfaces 600, 610, 620, and 630 are merely exemplary; a person of ordinary skill in the art would recognize that the specific means for loading and selecting files and displaying results that are depicted in the figures are not meant to be limiting in the context of interacting with an electronic device in a test environment.

[0048] Figure 7 is a flow diagram of a method 700 for tracking a simulated user experience in accordance with some implementations. The method 700 may be performed at an electronic device (e.g., developer console 210, simulation environment 230, or a combination thereof) having one or more processors (e.g., CPUs 214 and/or 234) and memory (e.g., memory 216 and/or 236) storing one or more programs for execution by the one or more processors. In some implementations, an electronic device includes one or more programs and memory storing one or more programs for execution by the one or more processors, and the one or more programs include instructions for performing the method 700. In some implementations, a non-transitory computer readable storage medium stores one or more programs, the one or more programs including instructions, which, when executed by an electronic device with one or more processors, causes the electronic device to perform the method 700.

[0049] An electronic device (e.g., simulation environment 230, Figure 2) obtains

(702) a first network simulation scenario (e.g., scenario 442-1, Figure 4E) selected from a plurality of predefined network simulation scenarios. Each of the network simulation scenarios embodies a specific combination of dynamic network parameters (e.g., command recipe 442-l(iii), Figure 4E), wherein the dynamic network parameters for a respective predefined simulation scenario are based on measurements of a real world communication environment corresponding to the respective simulation scenario. Example scenarios serving as bases for simulations include wired communication channels (e.g., Ethernet, DSL), wireless communication channels (e.g., Wi-Fi) mediums, and combinations thereof. To accurately represent a real-world communications channel, each simulation scenario includes a sequence of impairments, with one or more of the impairments independently changing over time (e.g., impairments 510, 520, and 530, Figure 5). Examples of impairments include one-way latency, round trip latency, jitter, packet loss, channel noise, channel bandwidth, and TCP retransmission. Each simulation scenario is a representative example of how real-world networks behave when subjected to different impairments. In some implementations, various real-world scenarios include Wi-Fi networks in different real-world environments (e.g., home, apartment, office, airport) and in particular areas in each environment (e.g., bedroom, kitchen, cubicle, break room, restroom, balcony). In some implementations, various real- world scenarios include DSL networks using different standards (e.g., Category 5, 5e, 6, 7, and so forth) and physical characteristics (e.g., cable length, conductor width and geometry). In some implementations, a plurality of simulation scenarios are included in a list of available simulation scenarios (e.g., scenarios 605, Figure 6A), from which one is selected (e.g., by the developer) in step 702.

[0050] The electronic device executes (704) the test application (e.g., 432-1, Figure

4D). In some implementations, the test application is a network-enabled application (e.g., a cloud-based application), an interactive application (e.g., a gaming application), or a combination thereof. In some implementations, a client (e.g., 242, Figures 2 and 4A) controls the test application with a sequence of command inputs corresponding to a plurality of specific operations of the test application. The sequence of command inputs is either pre stored in memory (e.g., 422-l(ii), Figure 4B), or entered manually by the developer by operating a pre-configured virtual controller (e.g., 424-1, Figure 4C). The test application provides an output data stream based on the inputs received by the client module, or independently of any inputs. In some implementations, an encoder (e.g., 434, Figure 4A) encodes the output data stream, and the encoded output data stream is transmitted to a network simulator (e.g., 246, Figures 2 and 4A).

[0051] The network simulator simulates (706) transmission of the output data stream, or the encoded output data stream, of the test application in a simulated test network for the first network simulation scenario (e.g., 442-1, Figure 4E) with associated first dynamic network parameters (e.g., 442-l(iii), Figure 4E). Stated another way, the output data (245, Figure 2) is transmitted through a network simulator (246, Figure 2) which is characterized by impairments corresponding to a particular preconfigured network simulation scenario. In some implementations, the network simulator subjects the output data to impairments by filtering the output data. The resulting filtered data stream reflects simulated real time effects of the simulated test network on transmission of the encoded data stream based on the first dynamic network parameters. Examples of effects of the simulated test network on transmission of the encoded data stream include a specific dropped frame, a specific lost packet, a specific measure of latency, a specific measure of quality, and a specific timeout (e.g., 44l-l(vi), Figure 4F; 618, Figure 6B).

[0052] The filtered data stream is recorded (708) in memory (e.g., 444- l(v), Figure

4F). In some implementations, data corresponding with effects of the impairments on the data stream are also recorded in memory (e.g., 444-l(vi), Figure 4F). In some implementations, the filtered data stream and/or the data corresponding with effects of the impairments on the data stream are displayed on an output device (e.g., 224, Figure 2) of the developer console 210. In some implementations, the filtered data stream and/or events associated with the filtered data stream are displayed in real time (or approximate real time) while the test application is still running (e.g., Figure 6B). In some implementations, the filtered data stream and/or events associated with the filtered data stream are displayed upon termination of the test application (e.g., Figure 6C).

[0053] The electronic device determines (710) one or more time-varying quality metrics for the filtered data stream. Examples of quality metrics include latency

measurements, jitter measurements, dropped packets, channel noise levels, and channel bandwidth levels. In some implementations, the quality metrics are determined with respect to running time of the test application, or with respect to specific portions of the test application. In some implementations, one or more performance aspects of the test application are determined based on the quality metrics (e.g., percentage of dropped packets, average/high/low latency and/or bandwidth levels, and so forth). In some implementations, a simulated user experience value is determined and associated with the simulation scenario for the test application (e.g.,“ETser Experience Score” in Summary 624, Figure 6C). In some implementations, the simulated user experience value is determined by deriving one or more simulated quality of service (QoS) values from the plurality of quality metrics, and comparing the one or more simulated QoS values with and one or more target QoS values.

For example, CPU 214 derives a simulated QoS value from a percentage of time windows during which the impaired data stream exhibits a threshold percentage of dropped packets, and the simulated QoS value (e.g., 70% packet drop rate) is compared to a target QoS value (e.g., 5% packet drop rate). If the simulated QoS value fails to meet the target QoS value, this is reflected as a factor in the overall user experience calculation. Other thresholds, factors, and weighted combinations of factors are possible depending on user/developer preference. For example, depending on how much a gaming application depends on low latency for an adequate user experience, a target latency -based QoS may be relatively more stringent than that of an application in which latency is less of an issue. In some implementations, one or more renderings of the filtered data stream are displayed (e.g., 612, Figure 6B; 626, Figure 6C) and the user experience value is determined based on a quality aspect of the displayed renderings.

[0054] In some embodiments, the electronic device adjusts (712) one or more congestion management algorithms (e.g., 432-l(iii), Figure 4D) of the test application based on one or more quality metrics. For example, if the simulated QoS is below the target QoS, a bitrate of the encoder is adjusted to compensate.

[0055] Figure 8 is a flow diagram of a method 800 for tracking a simulated user experience in accordance with some implementations. The method 800 may be performed at an electronic device (e.g., developer console 210, simulation environment 230, or a combination thereof) having one or more processors (e.g., CPUs 214 and/or 234) and memory (e.g., memory 216 and/or 236) storing one or more programs for execution by the one or more processors. In some implementations, an electronic device includes one or more programs and memory storing one or more programs for execution by the one or more processors, and the one or more programs include instructions for performing the method 800. In some implementations, a non-transitory computer readable storage medium stores one or more programs, the one or more programs including instructions, which, when executed by an electronic device with one or more processors, causes the electronic device to perform the method 800.

[0056] An electronic device (e.g., developer console 210, Figure 2) obtains (801) a test application (e.g., a network-enabled test application 432-1, Figure 4D). In some implementations, the test application is obtained when a developer loads or selects the test application using a user interface element (e.g., 602, Figure 6A) of the developer console. In some implementations, upon selection of a test application, the CPU 234 loads the selected test application from the memory 236 into the test application module 244 (Figure 2).

[0057] The electronic device displays (802) a plurality of simulation scenarios (e.g.,

442, Figure 4E). In some implementations, the simulation scenarios are displayed in a plurality of affordances (e.g., 605, Figure 6A) in the same user interface as that in step 801, or in a different user interface. In some implementations, only one simulation scenario is displayed at a time. As described above, each of the simulation scenarios embodies a specific combination of dynamic network parameters (e.g., 442-l(iii), Figure 4E), and the dynamic network parameters for each simulation scenario are based on measurements of respective real world communication environments corresponding to the respective simulation scenarios.

[0058] The electronic device receives (803) a selection of a first simulation scenario

(e.g., through selection of an affordance 605). In some implementations, a developer selects an available simulation scenario by selecting an affordance or other user interface element that corresponds to a desired simulation scenario for a particular test. Alternatively, a simulation scenario is automatically selected as part of a testing script. For example, a particular testing script may be associated with DSL testing, and include simulation scenarios 442-6 through 442-10 (Figure 6A). Upon selection of the DSL testing script, the first scenario (442-6) is automatically selected and the simulation is run. Subsequently, the next scenario (442-7) is automatically selected and the simulation is run again. In some implementations, upon any kind of selection (e.g., manual or automatic) of a simulation scenario, the CPU 234 loads the selected simulation scenario from the memory 236 into the network simulator 246 (Figure 2).

[0059] In some implementations, the electronic device also receives a selection of a client program or script (e.g., 422, Figure 4B) for automatic control of the test application and/or controller program or script (e.g., 424, Figure 4C) for manual control of the test application. In some implementations, a developer selects an available client and/or controller program by selecting an affordance or other user interface element that corresponds to the desired client and/or controller program on the same user interface as that in steps 801 and/or 802, or on a different user interface. In some implementations, upon selection of a client program, the CPU 234 loads the selected client program from the memory 236 into the client module 246 (Figure 2). [0060] Upon selection of a test application and a simulation scenario (and optionally, a client program), the electronic device runs a simulation. In some implementations, the simulation is run upon selection of an affordance (e.g., 608, Figure 6A) or other user interface element associated with starting a simulation, on the same user interface as that in steps 801 and/or 802, or on a different user interface.

[0061] In order to run a simulation, the electronic device executes (804) the test application. Upon execution of the test application, an encoder (e.g., 434, Figure 4A) associated with the test application or the test application module encodes a data stream (e.g., a video stream) associated with a plurality of specific operations of the network-enabled test application, the operations being entered manually by a developer operating a controller (e.g., a virtual game controller 424, Figure 4C), or automatically by a client program (e.g., 422, Figure 4B). In some implementations, the electronic device executes the test application in accordance with features discussed above with reference to step 704.

[0062] While the test application is being executed and the encoder is encoding a data stream, the electronic device simulates (806) transmission of the encoded data stream through the selected simulation scenario (e.g., with the associated dynamic network parameters). In some implementations, the electronic device simulates the transmission in accordance with features discussed above with reference to step 706.

[0063] The electronic device records (808) the filtered data stream in memory in accordance with features discussed above with reference to step 708, and determines (810) quality metrics of the filtered data stream in accordance with features discussed above with reference to step 710. In some implementations, the electronic device determines one or more performance aspects of the network-enabled test application based on a plurality of the quality metrics for the filtered data stream (as described above), and associates one or more of the performance aspects with the current simulation scenario of the test application being tested.

[0064] In some implementations, testing and evaluation ends (812: yes) upon completion of the current simulation scenario, and in some implementations, the electronic device adjusts (814) one or more congestion management algorithms of the test application in accordance with features discussed above with reference to step 712.

[0065] Alternatively, testing and evaluation does not end (812: no) upon completion of the current simulation scenario, and in some implementations, the electronic device proceeds to step 802, at which one or more simulation scenarios are displayed for a subsequent simulation of the test application. For example, the electronic devices receives (803) a selection of a second affordance associated with a second network simulation scenario, and in response, the electronic device executes (804) the test application, simulates (806) transmission of the encoded data stream of the test application in a simulated test network for the second simulation scenario, records (808) the resulting filtered data stream, determines (810) quality metrics and performance aspects of the filtered data stream, and associates the performance aspects with the second simulation scenario.

[0066] In some implementations, after a plurality of simulations, the electronic device displays (e.g., on output device 224), on a results user interface (e.g., 630, Figure 6D), one or more of the performance aspects of the test application associated with each simulation scenario that was run for that particular test application (e.g., simulation data for the first scenario 444-l(vi) and for the second scenario 444-2(vi)).

[0067] Figure 9 is a flow diagram of a method 900 for deriving parameters for simulation scenarios in accordance with some implementations. The method 900 may be performed at an electronic device (e.g., developer console 210 and/or simulation environment 230) having one or more processors (e.g., CPUs 214 and/or 234) and memory (e.g., memory 216 and/or 236) storing one or more programs for execution by the one or more processors.

In some implementations, an electronic device includes one or more programs and memory storing one or more programs for execution by the one or more processors, and the one or more programs include instructions for performing the method 900. In some

implementations, a non-transitory computer readable storage medium stores one or more programs, the one or more programs including instructions, which, when executed by an electronic device with one or more processors, causes the electronic device to perform the method 900.

[0068] An electronic device transmits (902) a first data stream including a first portion of content associated with a network-enabled test application to a user device through a real world communication environment (e.g., a Wi-Fi network set up in a real apartment, or a DSL network set up in a real office building, etc.).

[0069] The electronic device produces (904) first performance data for the transmission in step 902 by characterizing performance of the test application in the real world communication environment at the user device (e.g., by measuring various quality metrics and/or performance aspects as described above).

[0070] The electronic device generates (906) a test network based on the first performance data in order to approximate the real world communication network (e.g., programs a command recipe as described above with reference to Figure 4E). In some implementations, a developer programs the command recipe.

[0071] The electronic device transmits (908) a second data stream including the first portion of content associated with the network-enabled test application to the client device through the test network generated in step 906 (e.g., subjects the data stream to impairments corresponding with the commands in the command recipe).

[0072] The electronic device produces (910) second performance data for the transmission in step 908 by characterizing performance of the test application in the test network at the user device (e.g., by measuring various quality metrics and/or performance aspects as described above).

[0073] The electronic device compares (912) the first performance data (associated with the real world network) with the second performance data (associated with the simulated test network).

[0074] If the first and second performance data are not equivalent to a predetermined degree (e.g., less than 90% similar), then the derivation of the parameters for the current simulation scenario is determined to be incomplete (914: no). In some implementations, upon the determination that the derivation of the parameters for the current simulation scenario is incomplete, one or more of the test network parameters for the current simulation scenario are adjusted (916), and the process continues at step 908.

[0075] However, if the first and second performance data are equivalent to a predetermined degree (e.g., at least 90% similar), then the derivation of the parameters for the current simulation scenario is determined to be complete (914: yes). In some

implementations, upon the determination that the derivation of the parameters for the current simulation scenario is complete, the real world network is adjusted (918), or a new real world network is introduced, and the process repeats for the new real world network (and a new simulation scenario associated with the new real world network), beginning at step 902.

[0076] References have been made in detail to various implementations, examples of which are illustrated in the accompanying drawings. In the above detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention and the described implementations. However, the invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the implementations.

[0077] It will be understood that, although the terms“first,”“second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first device could be termed a second device, and, similarly, a second device could be termed a first device, without changing the meaning of the description, so long as all occurrences of the first device are renamed consistently and all occurrences of the second device are renamed consistently. The first device and the second device are both device, but they are not the same device.

[0078] The terminology used herein is for the purpose of describing particular implementations only and is not intended to be limiting of the claims. As used in the description of the implementations and the appended claims, the singular forms“a”,“an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0079] As used herein, the term“if’ may be construed to mean“when” or“upon” or

“in response to determining” or“in accordance with a determination” or“in response to detecting,” that a stated condition precedent is true, depending on the context. Similarly, the phrase“if it is determined [that a stated condition precedent is true]” or“if [a stated condition precedent is true]” or“when [a stated condition precedent is true]” may be construed to mean “upon determining” or“in response to determining” or“in accordance with a determination” or“upon detecting” or“in response to detecting” that the stated condition precedent is true, depending on the context. [0080] The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The

implementations were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various implementations with various modifications as are suited to the particular use contemplated.