Patent Publication Number: US-8544034-B2

Title: Method and system for automated monitoring of video assets

Description:
FIELD OF THE DISCLOSURE 
     The present disclosure relates to baseband video monitoring, and in particular to automated monitoring of baseband video assets. 
     BACKGROUND 
     Users of a multimedia content distribution network (MCDN) may be provided a wide range of video assets to select from. A service provider operating the MCDN may be faced with various quality control issues related to the video assets and the performance of MCDN equipment. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a block diagram of selected elements of an embodiment of an MCDN; 
         FIG. 2  is a block diagram of selected elements of an embodiment of an expert test monitoring platform (ETMP); 
         FIG. 3  is a block diagram of selected elements of an embodiment of a multimedia handling device (MHD); 
         FIG. 4  is a block diagram of selected elements of an embodiment of a video asset; 
         FIG. 5  illustrates selected elements of an embodiment of an MCDN test monitoring method; 
         FIG. 6  illustrates selected elements of an embodiment of an MCDN test monitoring method; and 
         FIG. 7  is a block diagram of selected elements of an embodiment of an ETMP configurator/executor. 
     
    
    
     DETAILED DESCRIPTION 
     In one aspect, a disclosed method for monitoring a multimedia content distribution network (MCDN) includes receiving user input selecting a multimedia handling device (MHD) for remote control, wherein the MHD is included in a plurality of MHDs installed in an expert test monitoring platform (ETMP) coupled to the MCDN, and receiving a user input sequence for controlling multimedia output presented by the selected MHD. The method may further include capturing the user input sequence to an ETMP script, and sending, to the selected MHD, a sequence of remote control commands corresponding to the user input. The ETMP script may be globally addressable to any desired MHD in the ETMP. The multimedia output presented by the selected MHD may include MCDN program channels, video-on-demand programs, pay-per-view programs, previously recorded programs, Internet content, or a combination thereof. 
     In certain embodiments, the user input sequence may further comprise a first portion that enables the MHD to display an electronic program guide (EPG) provided by the MCDN, and a second portion that enables user interaction with the EPG via remote control commands. The method may further include capturing the user input sequence, including capturing a plurality of second user input in the ETMP script, and storing the captured ETMP script. The method may still further include retrieving a previously stored first ETMP script, receiving third user input specifying a target MHD for the first ETMP script, globally addressing the first ETMP script to execute on the target MHD, and executing the first ETMP script on the target MHD. The remote control commands specified in the first ETMP script may be sent to the target MHD for execution. The method may also include retrieving a previously stored second ETMP script, combining at least a portion of the first ETMP script with at least a portion of the second ETMP script into a third ETMP script, and storing the third ETMP script. 
     In some embodiments, the captured ETMP script may be stored to an ETMP database, while the first user input may be received via a graphical user interface (GUI), the GUI may include a virtual remote control for controlling the selected MHD. The method may then also include displaying an indication of the captured ETMP script, receiving fourth user input for editing the captured ETMP script, and storing the edited ETMP script. 
     In a further aspect, a disclosed computerized test system for monitoring output channels from an MCDN includes a processor coupled to memory media and a network adapter accessible to the processor. The memory media may further include instructions executable by the processor to receive user input to operate an MHD included in an ETMP, while the ETMP may further include a plurality of MHDs configured to output MCDN program channels, an ETMP network coupled to the network adapter, and a network-based remote control unit configured to control individual ones of the plurality of MHDs in response to commands received via the ETMP network. The memory media may further include instructions to capture the user input as an ETMP script, and globally address the ETMP script to any one of the plurality of MHDs. The user input may correspond to remote control commands executable by the MHD to control multimedia output at the MHD, including MCDN program channels. 
     In certain embodiments, the memory media may include instructions to save the captured ETMP script, and retrieve a previously saved first ETMP script. In response to receiving the user input, a corresponding remote control command to the MHD may be sent. The memory media may further include instructions to retrieve a previously saved second ETMP script, concatenate the first ETMP script with the second ETMP script into a third ETMP script, and save the third ETMP script. 
     In some embodiments, the memory media may include instructions executable by the processor to execute the first ETMP script on a target MHD selected from the plurality of MHDs. A global address for the target MHD may be specified for the first ETMP script. The instructions to save the captured ETMP script may further include instructions to save the captured ETMP script at an ETMP database coupled to the ETMP network. The instructions to receive the user input may further include instructions to receive the user input via a GUI, including a virtual remote control for controlling the MHD. 
     In yet another aspect, an ETMP for monitoring output channels from an MCDN includes a plurality of addressable ports operable to connect to a respective plurality of MHDs configured as selectable units under test (UUTs) and configured to output MCDN channels. The ETMP may include at least one ETMP configurator configured to select at least one current UUT(s) from among the plurality of MHDs, capture an ETMP script indicative of user input for controlling a current UUT, store the captured ETMP script, and globally address a remote control command in the ETMP script to the current UUT. 
     In some embodiments, the ETMP may further include an ETMP database for storing ETMP scripts, and an ETMP network configured to connect the MHDs, the ETMP configurator(s), and the ETMP database. The ETMP may also include a power controller coupled to the ETMP network for controlling power supplied to the selected UUT(s) in response to receiving a network power control command, a remote controller coupled to the ETMP network for selecting an MCDN channel in response to receiving a channel selection command, and a video matrix switch for routing a plurality of baseband video signals from the plurality of MHDs to the at least one ETMP configurator. The video matrix switch may be coupled to the ETMP network. In response to receiving a network video switch command, the video matrix switch may be configured to selectively switch a plurality of baseband signals output by the MHDs to any one or more of a plurality of frame acquirer inputs associated with the at least one ETMP configurator. 
     In given embodiments, the ETMP configurator may be configured to retrieve a previously saved first ETMP script, retrieve a previously saved second ETMP script, concatenate at least a portion of the first ETMP script with at least a portion of the second ETMP script into a third ETMP script, and store the third ETMP script. The ETMP configurator may further be configured to address the third ETMP script to the current UUT, and execute the third ETMP script on the current UUT. 
     In the following description, details are set forth by way of example to facilitate discussion of the disclosed subject matter. It should be apparent to a person of ordinary skill in the field, however, that the disclosed embodiments are exemplary and not exhaustive of all possible embodiments. 
     Throughout this disclosure, a hyphenated form of a reference numeral refers to a specific instance of an element and the un-hyphenated form of the reference numeral refers to the element generically or collectively. Thus, for example, widget  12 - 1  refers to an instance of a widget class, which may be referred to collectively as widgets  12  and any one of which may be referred to generically as a widget  12 . 
     Turning now to the drawings,  FIG. 1  is a block diagram illustrating selected elements of an embodiment of an MCDN  100  including ETMP  170 , which may be used for monitoring an output channel from MCDN  100  and to capture user commands during testing, as will be described in detail herein. Although multimedia content is not limited to television (TV), video on demand (VOD), or pay-per-view (PPV) programs, the depicted embodiments of MCDN  100  and its capabilities are primarily described herein with reference to these types of multimedia content, which are interchangeably referred to herein as “multimedia content”, “multimedia content programs”, “multimedia programs” or, simply, “programs.” 
     The elements of MCDN  100  illustrated in  FIG. 1  depict network embodiments with functionality for delivering multimedia content to a set of one or more subscribers. It is noted that different embodiments of MCDN  100  may include additional elements or systems (not shown in  FIG. 1  for clarity) as desired for additional functionality, such as data processing systems for billing, content management, customer support, operational support, or other business applications. 
     As depicted in  FIG. 1 , MCDN  100  includes one or more clients  120  and a service provider  121 . Each client  120  may represent a different subscriber of MCDN  100 . In  FIG. 1 , a plurality of n clients  120  is depicted as client  120 - 1 , client  120 - 2  to client  120 - n,  where n may be a large number. Service provider  121  as depicted in  FIG. 1  encompasses resources to acquire, process, and deliver programs to clients  120  via access network  130 . Such elements in  FIG. 1  of service provider  121  include content acquisition resources  180  connected to switching network  140  via backbone network  175 , as well as application server  150 , database server  190 , and content delivery server  160 , also shown connected to switching network  140 . 
     Access network  130  demarcates clients  120  and service provider  121 , and provides at least one connection path between clients  120  and service provider  121 . In some embodiments, access network  130  is an Internet protocol (IP) compliant network. In some embodiments, access network  130  is, at least in part, a coaxial cable network. It is noted that in some embodiments of MCDN  100 , access network  130  is owned and/or operated by service provider  121 . In other embodiments, a third party may own and/or operate at least a portion of access network  130 . 
     In IP-compliant embodiments of access network  130 , access network  130  may include a physical layer of unshielded twisted pair cables, fiber optic cables, or a combination thereof. MCDN  100  may include digital connections between clients  120  and a node (see also  FIG. 4 ) in access network  130  while fiber, cable or another broadband medium connects service provider resources to the node. In other embodiments, the broadband cable may extend all the way to clients  120 . In certain embodiments, fiber optic cables may be provided from the node in access network  130  to each individual client  120 . The connections between access network  130  and clients  120  may include digital subscriber line (DSL) connections. In particular embodiments, the connections may be DSL-compliant twisted pair or another type of galvanic loop (see also  FIG. 4 ). 
     As depicted in  FIG. 1 , switching network  140  provides connectivity for service provider  121 , and may be housed in a central office or other facility of service provider  121 . Switching network  140  may provide firewall and routing functions to demarcate access network  130  from the resources of service provider  121 . In embodiments that employ DSL-compliant connections, switching network  140  and/or access network  130  may include elements of a DSL access multiplexer (DSLAM) that multiplexes many subscriber DSLs to backbone network  175  (see also  FIG. 4 ). 
     In  FIG. 1 , backbone network  175  represents a private network including, as an example, a fiber based network to accommodate high data transfer rates. Content acquisition resources  180  as depicted in  FIG. 1  encompass the acquisition of various types of content including broadcast content, other “live” content including national content feeds, and VOD content. 
     Thus, the content provided by service provider  121  encompasses multimedia content that is scheduled in advance for viewing by clients  120  via access network  130 . Such multimedia content, also referred to herein as “scheduled programming,” may be selected using an EPG, such as EPG  316  described below with respect to  FIG. 3 . Accordingly, a user of MCDN  100  may be able to browse scheduled programming well in advance of the broadcast date and time. Some scheduled programs may be “regularly” scheduled programs, which recur at regular intervals or at the same periodic date and time (i.e., daily, weekly, monthly, etc.). Programs which are broadcast at short notice or interrupt scheduled programs are referred to herein as “unscheduled programming.” 
     Acquired content is provided to content delivery server  160  via backbone network  175  and switching network  140 . Content may be delivered from content delivery server  160  to clients  120  via switching network  140  and access network  130 . Content may be compressed, encrypted, modulated, demodulated, and otherwise encoded or processed at content acquisition resources  180 , content delivery server  160 , or both. Although  FIG. 1  depicts a single element encompassing acquisition of all content, different types of content may be acquired via different types of acquisition resources. Similarly, although  FIG. 1  depicts a single content delivery server  160 , different types of content may be delivered by different servers. Moreover, embodiments of MCDN  100  may include content acquisition resources in regional offices that are connected to switching network  140 . 
     Although service provider  121  is depicted in  FIG. 1  as having switching network  140  to which content acquisition resources  180 , content delivery server  160 , and application server  150  are connected, other embodiments may employ different switching networks for each of these functional components and may include additional functional components (not depicted in  FIG. 1 ) including, for example, operational subsystem support (OSS) resources. 
       FIG. 1  also illustrates application server  150  connected to switching network  140 . As suggested by its name, application server  150  may host or otherwise implement one or more applications for MCDN  100 . Application server  150  may be any data processing system with associated software that provides applications for clients or users. Application server  150  may provide services including multimedia content services, e.g., EPGs, digital video recording (DVR) services, VOD programs, PPV programs, IPTV portals, digital rights management (DRM) servers, navigation/middleware servers, conditional access systems (CAS), and remote diagnostics, as examples. 
     Applications provided by application server  150  may be downloaded and hosted on other network resources including, for example, content delivery server  160 , switching network  140 , and/or on clients  120 . Application server  150  is configured with a processor and storage media (not shown in  FIG. 1 ) and is enabled to execute processor instructions, such as those included within a software application. As depicted in  FIG. 1 , application server  150  may be configured to include various applications (not shown in  FIG. 1 ) that may provide functionality to clients  120 . 
     Further depicted in  FIG. 1  is database server  190 , which provides hardware and software resources for data warehousing. Database server  190  may communicate with other elements of the resources of service provider  121 , such as application server  150  or content delivery server  160 , in order to store and provide access to large volumes of data, information, or multimedia content. In some embodiments, database server  190  includes a data warehousing application, accessible via switching network  140 , that can be used to record and access structured data, such as program or channel metadata for clients  120 . Database server  190  may also store device information, such as identifiers for client  120 , model identifiers for remote control devices, identifiers for peripheral devices, etc. 
     Also shown in  FIG. 1  is ETMP  170 , which represents a facility for test monitoring of output channels of MCDN  100 . ETMP  170  may include infrastructure for emulating functionality associated with clients  120  for the purpose of capturing and analyzing output video and/or audio signals in order to test the performance and quality of video assets provided by MCDN  100  (see also  FIG. 2 ). 
     It is noted that clients  120  may include network appliances collectively referred to herein as customer premises equipment (CPE). In various embodiments, CPE may include the following devices: a gateway (GW), an MHD (see also  FIG. 3 ), and a display device (not shown in  FIG. 1 ). Any combination of the GW, the MHD, and the display device may be integrated into a single physical device. Thus, for example, CPE might include a single physical device that integrates the GW, MHD, and a display device. As another example, an MHD may be integrated into a display device, while the GW may be housed within a physically separate device. 
     The GW may provide connectivity for client  120  to access network  130 . The GW may provide an interface and conversion function between access network  130  and a client-side local area network (LAN). The GW may include elements of a conventional DSL or cable modem. In some embodiments, the LAN may further include routing functionality for routing multimedia content, conventional data content, or a combination of both in compliance with IP or another network layer protocol. In some embodiments, the LAN may encompass or represent an IEEE 802.3 (Ethernet) LAN, an IEEE 802.11-type (WiFi) LAN, or a combination thereof. The GW may still further include WiFi or another type of wireless access point to extend the LAN to wireless-capable devices in proximity to the GW. The GW may also provide a firewall (not depicted) between clients  120  and access network  130 . 
     Clients  120  may further include a display device or, more simply, a display (not shown in  FIG. 1 ). The display may be implemented as a TV, a liquid crystal display screen, a computer monitor, or the like. The display may comply with a display standard for computer monitors and/or TV displays. Standards for computer monitors include analog standards such as video graphics array (VGA), extended graphics array (XGA), etc., or digital standards such as digital visual interface (DVI) and high definition multimedia interface (HDMI), among others. A TV display may comply with standards such as National Television System Committee (NTSC), Phase Alternating Line (PAL), or another suitable standard. The display may include one or more integrated speakers to play audio content. 
     Clients  120  may further include respective remote control (not shown in  FIG. 1 ), which is configured to control the operation of MHD by means of a user interface, such as EPG  316  (see  FIG. 3 ) that may be displayed by the display. The remote control of client  120  may be operable to communicate requests or commands wirelessly to the MHD using infrared (IR) or radio frequency (RF) signals. MHDs may also receive requests or commands via buttons located on side panels of MHDs. 
     The MHD may be enabled and configured to process incoming multimedia signals to produce audio and visual signals suitable for delivery to the display and any optional external speakers. Incoming multimedia signals received by the MHD may be compressed and/or encrypted, digital or analog, packetized for delivery over packet-switched embodiments of access network  130  or modulated for delivery over cable-based access networks. In some embodiments, the MHD may be implemented as a stand-alone set top box suitable for use in a co-axial or IP-based MCDN. 
     Referring now to  FIG. 2 , a block diagram illustrating selected elements of an embodiment of ETMP  170  is presented. The embodiment depicted in  FIG. 2  is an exemplary implementation of ETMP  170  for illustrative purposes. It will be understood that, in different embodiments, elements depicted in  FIG. 2  may be modified, rearranged, or omitted. For example, in certain embodiments, ETMP network  240  may refer to portions of a larger, external network system (not shown in  FIG. 2 ). In various embodiments, video matrix switch  250  may represent either an automatic switch or a manual switch or a combination thereof. Other substitutions may be implemented in given embodiments of ETMP  170 , as desired. 
     In  FIG. 2 , ETMP network  240  is shown providing communication links between various elements in ETMP  170 , as will now be described in detail. It is noted that ETMP network  240  may also link ETMP  170  to switching network  140  (not shown in  FIG. 2 , see  FIG. 1 ). Also shown in  FIG. 2  are UUTs  220 , which may represent similar elements as CPE associated with clients  120 , as described previously. In  FIG. 1 , UUT  220 - 1  and  220 - 2  are shown as two exemplary instances for clarity, while it will be understood that ETMP  170  may include different numbers of UUT  220  in various embodiments. UUT  220  may represent an embodiment of client  120  that is implemented in ETMP  170  for the purposes of testing and analyzing output channels of MCDN  100 . Accordingly, UUT  220  may provide similar functionality as client  120 , but may omit certain elements that are not relevant for testing purposes (see also  FIG. 3 ). For example, UUT  220  may not include a display. In  FIG. 2 , UUT  220 - 1  may include MHD  225 - 1  and GW  223 - 1 , as described previously (see also  FIG. 3 ), while UUT  220 - 2  may include MHD  225 - 2  and GW  223 - 2 . 
     As depicted in  FIG. 2 , network-based remote control  228  may represent a means to generate remote control signals for reception by MHD  225 . Network-based remote control  228  may be configured to receive network commands that are addressed to a specific remote control port (not shown in  FIG. 2 ) associated with a particular MHD  225 , such as MHD  225 - 1 . In this manner, network-based remote control  228  may provide functionality to emulate a remote control operated by a user of client  120  (see  FIG. 1 ). Network commands sent to network-based remote control  228  may originate from a test operator of ETMP  170  or from an ETMP test program that is configured to execute in an automated manner. 
     Also shown in  FIG. 2 , network-based power control  230  may represent a means to control (i.e., switch) power to UUT  220 , including to MHD  225 , GW  223 , and/or other elements. Network-based power control  230  may be configured to receive network commands that are addressed to a specific power circuit associated with a particular UUT  220 . In this manner, network-based power control  230  may provide programmable switching capability to power down and power up UUT  220  and associated elements. Network commands sent to network-based power control  230  may originate from a test operator of ETMP  170  or from an ETMP test program, as will be described in detail below. 
     On the operational side of ETMP  170  in  FIG. 2  are ETMP configurators/executors  260  and ETMP executors  270 . A “configurator” refers to a module that allows an operator (not shown in  FIG. 2 ) to perform individual test operations, generate test sequences, obtain test results, and otherwise manually operate a test facility. An ETMP configurator is therefore specific to ETMP  170 . An “executor” refers to a module that is configured to execute previously stored test sequences, also referred to as test programs, jobs, batch files, scripts, etc., comprised of individual test operations or test instructions. An ETMP executor is specific to ETMP  170 . ETMP configurators/executors  260  represent configurator modules that are executable on a computing device coupled to ETMP  170 , which also may include executor functionality. ETMP executors  270  represent executor modules that do not include configurator functionality. ETMP  170  may include ETMP configurators/executors  260 - 1 ,  260 - 2  and so on, up to an arbitrary p-number of ETMP configurators/executors  260 - p.  ETMP  170  may include ETMP executors  270 - 1 ,  270 - 2  and so on, up to an arbitrary m-number of ETMP executors  270 - m.    
     Additionally, in  FIG. 2 , video matrix switch  250  is shown providing connectivity between MHDs  225  and ETMP configurators/executors  260  and ETMP executors  270 . Video matrix switch  250  may receive network commands via link  252  to ETMP network  240 . Video matrix switch  250  may couple to output baseband video signals from MHD  225  via links  254 . Specifically, video matrix switch  250  may receive an output signal from MHD  225 - 1  via link  254 - 1  and from MHD  225 - 2  via link  254 - 2 . Furthermore, video matrix switch  250  may be coupled to inputs of ETMP configurators/executors  260  via link  256 - 1  and to inputs of ETMP executors  270  via link  256 - 2 . It is noted that links  256  may represent multiple connections that form one edge of a switching matrix, while links  254  represent another edge of the switching matrix. It is further noted that link  254  may represent a communication port, such as an addressable network port, that is operable to connect to MHD  225 . 
     Also shown in  FIG. 2  is ETMP master controller  232 , which represents a functional module configured to manage access to resources of ETMP  170 . ETMP master controller  232  may be configured to receive control requests for access to ETMP resources (such as UUTs  220  and associated elements in ETMP  170 ) from ETMP configurators or executors. For example, ETMP executor  270 - 1  may send a control request for access to UUT  220 - 2  from ETMP master controller  232 , which may then grant the control request and assign control to ETMP executor  270 - 1 . Subsequent requests for access to UUT  220 - 2  may then be denied by ETMP master controller  232 , so long as ETMP executor  270 - 1  is assigned control of UUT  220 - 2 . In certain embodiments, ETMP master controller  232  may take a priority of an ETMP test program into consideration when granting control requests to access ETMP resources and may terminate a currently assigned control relationship in favor of a higher priority one. In one embodiment, a scheduled ETMP test program may be assigned to ETMP executor  270 - 2  when a scheduled start time approaches the current time. The scheduled ETMP test program may be designated for UUT  220 - 2 , which may be assigned for control by ETMP configurator/executor  260 - 1 . In such an instance, ETMP master controller  232  may be configured to reassign control of UUT  220 - 2  to ETMP executor  270 - 2  and terminate the assignment of ETMP configurator/executor  260 - 1 . A user of ETMP configurator/executor  260 - 1  may be given a warning by ETMP master controller  232  that a scheduled test is about to begin on UUT  220 - 2  and that a presently active test session will soon be terminated. 
     Finally, in  FIG. 2 , ETMP database  234  may represent a repository for data and information associated with ETMP  170 . For example, ETMP database  234  may store configuration information representing ETMP resources, including network addresses and connection information for UUTs  220 , video matrix switch  250 , ETMP configurators/executors  260 , ETMP executors  270 , network-based remote control  228  and network-based power control  230 . In various embodiments, ETMP master controller  232  may query ETMP database  234  for such information when managing control requests for ETMP resources. ETMP database  234  may further store ETMP test programs, as well as results of executed ETMP test programs and test operations. It is noted that various other elements in ETMP  170  may be configured to access ETMP database  234 , as desired. 
     In operation of ETMP  170 , a user may access ETMP configurator/executor  260 - 1  to perform test operations on UUT  220 - 1  (see also ETMP studio application  400  in  FIGS. 4 ,  7 ). The user may first send a control request to ETMP master controller  232  for access to UUT  220 - 1 . After the control request has been approved and access to UUT  220 - 1  has been assigned to ETMP configurator/executor  260 - 1 , ETMP configurator/executor  260 - 1  may query ETMP database  234  for network addresses and configuration information associated with UUT  220 - 1 . Using a queried network address, the user may send a network command using ETMP configurator/executor  260 - 1  to network-based power control  230  to power up UUT  220 - 1 . ETMP configurator/executor  260 - 1  may also be used to send a network command to network-based remote control  228  to select a particular video channel for output by UUT  220 - 1  (i.e., MHD  225 - 1 ). ETMP configurator/executor  260 - 1  may also be used to send a network command to video matrix switch  250  via switch link  254 - 1  (an output from MHD  225 - 1 ) to an input of ETMP configurator/executor  260 - 1  via link  256 - 1 . The input to ETMP configurator/executor  260 - 1  may be at frame acquirer  326  (i.e., frame grabber) (see  FIGS. 3 and 7 ), which may be configured to acquire a video and/or audio portion of the selected video channel that has been routed via video matrix switch  250 . The acquired audio/video may be used to perform a test operation, which may generate a test result. 
     During usage of ETMP  170 , a user may activate recording of operations performed using ETMP configurator/executor  260 . The operations may represent actions taken via a GUI of ETMP studio application  400  (see  FIGS. 4 ,  7 ). The recorded operations may be stored in ETMP database  234  as an ETMP script (not shown in  FIG. 2 ), that may be retrieved at a later time and executed using ETMP executor  270 . Execution of the ETMP script may involve sending corresponding remote control commands to UUT  220 . It is noted that the ETMP script may be globally addressable to any instance of UUT  220 . The user may also combine portions from different ETMP scripts to generate new ETMP scripts. In this manner, redundancy avoidance and efficient sharing of workload may be accomplished among users of ETMP  170 . 
     Referring now to  FIG. 3 , a block diagram illustrating selected elements of an embodiment of UUT  220 , including further details of MHD  225 , is presented. UUT  220  may be configured to execute remote control commands associated with ETMP test scripts, as mentioned above. In  FIG. 3 , MHD  225  is shown as a functional component of UUT  220  along with GW  223 , which is shown receiving multimedia content  360  from switching network  140 . It is noted that UUT  220  may represent functionality similar to that provided to clients  120  and, in particular, may receive substantially the same multimedia content  360 , as received by clients  120  (see  FIG. 1 ). In this manner, UUT  220  may serve as a realistic and accurate representation of clients  120  within ETMP  170  for testing and monitoring purposes, as described herein. 
     In the embodiment depicted in  FIG. 3 , MHD  225  includes processor  301  coupled via shared bus  302  to storage media, collectively identified as memory media  310 . MHD  225 , as depicted in  FIG. 3 , further includes network adapter  320  that interfaces MHD  225  to switching network  140  via GW  223  and through which MHD  225  receives multimedia content  360 . GW  223  is shown providing a bridge to switching network  140 , and receiving multimedia content  360  from switching network  140 . 
     In embodiments suitable for use in IP-based content delivery networks, MHD  225 , as depicted in  FIG. 3 , may include transport unit  330  that assembles the payloads from a sequence or set of network packets into a stream of multimedia content. In coaxial-based access networks, content may be delivered as a stream that is not packet-based and it may not be necessary in these embodiments to include transport unit  330 . In a co-axial implementation, however, other tuning resources (not explicitly depicted in  FIG. 3 ) may be used to “filter” desired content from other content that is delivered over the coaxial medium simultaneously and these tuners may be provided in MHD  225 . The stream of multimedia content received by transport unit  330  may include audio information and video information and transport unit  330  may parse or segregate the two to generate video stream  332  and audio stream  334  as shown. 
     Video and audio streams  332  and  334 , as output from transport unit  330 , may include audio or video information that is compressed, encrypted, or both. A decoder unit  340  is shown as receiving video and audio streams  332  and  334  and generating native format video and audio streams  342  and  344 . Decoder  340  may employ any of various widely distributed video decoding algorithms including any of the Motion Pictures Expert Group (MPEG) standards, or Windows Media Video (WMV) standards including WMV 9, which has been standardized as Video Codec-1 (VC-1) by the Society of Motion Picture and Television Engineers. Similarly decoder  340  may employ any of various audio decoding algorithms including Dolby® Digital, Digital Theatre System (DTS) Coherent Acoustics, and Windows Media Audio (WMA). 
     The native format video and audio streams  342  and  344  as shown in  FIG. 3  may be processed by encoders/digital-to-analog converters (encoders/DACs)  350  and  370  respectively to produce video and audio signals  352  and  354  in a format compliant with a display, as mentioned previously. Since MHD  225  is configured for test monitoring within ETMP  170 , a display may be omitted from UUT  220 . Video and audio signals  352  and  354 , which may be referred in aggregate to as the “baseband video signal,” may represent analog signals, digital signals, or a combination thereof, in different embodiments. In  FIG. 3 , video and audio signals  352  and  354  are shown being ultimately routed to frame acquirer  326  (see also  FIG. 7 ), which may be associated with ETMP configurator/executor  260  and/or ETMP executor  270 . The routing of video and audio signals  352  and  354  may be accomplished using video matrix switch  250  (see  FIG. 2 ), as described above. 
     Memory media  310  encompasses persistent and volatile media, fixed and removable media, and magnetic and semiconductor media. Memory media  310  is operable to store instructions, data, or both. Memory media  310  as shown may include sets or sequences of instructions and/or data, namely, an operating system  312 , EPG  316 , and MCDN application  318 . Operating system  312  may be a UNIX or UNIX-like operating system, a Windows® family operating system, or another suitable operating system. In some embodiments, memory media  310  is configured to store and execute instructions provided as services to UUT  220  by application server  150 , as mentioned previously. For example, MCDN application  318  may represent a combination of various sources of multimedia content that have been combined and generated as an output channel by application server  150 . 
     EPG  316  represents a guide to the multimedia content provided to UUT  220  via MCDN  100 , and may be output as an element of the user interface. The user interface may include a plurality of menu items arranged according to one or more menu layouts, which enable operation of MHD  225  using a remote control. 
     Local transceiver  308  represents an interface of MHD  225  for communicating with external devices, such as a remote control or network-based remote control  228  (see  FIG. 2 ). Local transceiver  308  may provide a mechanical interface for coupling to an external device, such as a plug, socket, or other proximal adapter. In some cases, local transceiver  308  is a wireless transceiver, configured to send and receive IR or RF or other signals. In some implementations local transceiver  308  receives IR or RF signals, but does not transmit IR or RF signals, i.e., local transceiver  308  may be a receiver. Local transceiver  308  may be accessed by a remote control module (not shown in  FIG. 3 ) for providing remote control functionality. In some embodiments, local transceiver  308  may include WiFi functionality. 
     Turning now to  FIG. 4 , a block diagram of selected elements of an embodiment of ETMP studio application  400  (see also  FIG. 7 ) are shown as a GUI screen. ETMP studio application  400  may provide various functionality to a user of ETMP configurator  260  (see  FIG. 2 ), on which ETMP studio application  400  may be executed. In particular, ETMP studio application  400  may be used to perform various operations via remote control commands on UUT  220 , and to view corresponding results of an output generated by UUT  220 , that may be captured using frame acquirer  326  (see  FIGS. 3 ,  7 ). 
     As shown in  FIG. 4 , ETMP studio application  400  may include virtual remote control  402 , which may represent functionality substantially similar to a physical embodiment of the individual remote control usable with client  120 , as described above with respect to  FIG. 1 . Virtual remote control  402  may receive user input via the GUI screen, and, in response, send corresponding commands to UUT  220  via network-based remote control  228  (see  FIG. 2 ). Since there may be a myriad of commands involved in using ETMP studio application  400  for testing UUT  220 , a user of ETMP studio application  400  may desire to capture, or record, a sequence of user input actions to virtual remote control  402 . ETMP studio application  400  may accordingly be configured to record user input operations and generate an ETMP script (not shown in  FIG. 4 ), which may be stored and retrieved for later use. The ETMP script may be generated in a manner that permits global addressing of UUT  220  within ETMP  170 , such that any available UUT  220  may be used with any ETMP script. ETMP studio application  400  may further be configured to provide functionality to allow users to load, modify, edit, delete, rename, or combine at least certain portions of ETMP scripts, among other operations. In certain embodiments, ETMP scripts may be stored by ETMP studio application  400  using ETMP database  234  (see  FIG. 2 ). 
     Turning now to  FIG. 5 , selected elements of an embodiment of a method  500  for monitoring of MCDN output channels is illustrated in flow chart form. In one embodiment, method  500  may be performed by ETMP  170  (see  FIGS. 1 ,  2 ). In particular, method  500  may represent an example of capturing and storing an ETMP script using ETMP studio application  400  (see  FIG. 4 ). It is noted that certain operations described in method  500  may be optional or may be rearranged in different embodiments. 
     In method  500 , first user input may be received (operation  502 ) for selecting an MHD in an ETMP for remote control. The MHD may be one of a plurality of UUTs configured for use in the ETMP. In response to receiving the first user input, the selected MHD may be assigned to the user for performing testing operations. Then, second user input may be received (operation  504 ) for controlling multimedia output presented by the selected MHD. The second user input may represent remote control commands that are selected by the user using an ETMP studio application (see also  FIGS. 4 and 7 ). In certain embodiments, the second user input may include a first portion that enables the MHD to display an EPG provided by the MCDN. The second user input may further include a second portion that enables user interaction with the EPG via remote control commands. The second user input may be captured (operation  506 ) to an ETMP script that is globally addressable to a desired MHD. In other words, the ETMP script may be reused with another MHD in the ETMP by readdressing the remote control commands included in the ETMP script. Remote control commands corresponding to the second user input may be sent (operation  508 ) to the MHD. The remote control commands may cause the MHD to output certain multimedia output, such as an MCDN channel, an EPG page, a multimedia program, etc. 
     Next in method  500 , a determination may be made whether additional second user input is received (operation  510 ). The determination in operation  510  may be made based on explicit user input or on another indication, such as on a time period of inactivity. When the result of operation  510  is YES, method  500  may then loop to operation  504  to receive additional second user input. In this manner, a sequence of elements of second user input may be received and captured to an ETMP script in method  500 . When the result of operation  510  is NO, a further determination may be made whether the ETMP script is done, that is, complete (operation  512 ). When the result of operation  512  is NO, the ETMP script may be edited (operation  514 ). When the result of operation  512  is YES, then the ETMP script may be stored (operation  516 ). It is noted that ETMP database  234  (see  FIG. 2 ) may be configured to store and retrieve ETMP scripts. 
     Turning now to  FIG. 6 , selected elements of an embodiment of method  600  for managing ETMP scripts are illustrated in flow chart form. In one embodiment, method  600  may be performed by ETMP  170  (see  FIGS. 1 ,  2 ). In particular, method  600  may represent an example of managing an ETMP script using ETMP studio application  400  (see  FIG. 4 ). It is noted that certain operations described in method  600  may be optional or may be rearranged in different embodiments. 
     A previously stored first ETMP script may be retrieved (operation  602 ). Then, user input may be received (operation  604 ) specifying a target MHD for the first ETMP script. The first ETMP script may be globally addressed (operation  606 ) to execute on the target MHD. Operation  606  may include addressing individual remote control commands within the first ETMP script to execute on the target MHD. The first ETMP script may be executed (operation  608 ) on the target MHD by sending remote control commands specified in the first ETMP script to the target MHD. It is noted that in certain embodiments, operations  602  through  608  may be executed as an individual method. 
     A previously stored second ETMP script may be retrieved (operation  610 ). The second ETMP script may be different from the first ETMP script. At least some portions of the first ETMP script may be combined (operation  612 ) with at least some portions of the second ETMP script into a third ETMP script. It is noted that the first ETMP script and the second ETMP script may be generated by different users of ETMP  170 . Finally, the third ETMP script may be stored (operation  614 ). It is noted that, upon a subsequent retrieval (not shown in  FIG. 6 ), the third ETMP script may be globally addressed to a desired MHD and executed on the desired MHD, as described above with respect to the first ETMP script. 
     Referring now to  FIG. 7 , a block diagram illustrating selected elements of an embodiment of ETMP configurator/executor  700  is presented. ETMP configurator/executor  700  may represent ETMP configurator/executor  260  and/or ETMP executor  270  (see  FIG. 2 ) in various embodiments. As shown in  FIG. 2 , multiple instances of ETMP configurator/executor  700  may be configured for use in conjunction with a given ETMP  170  facility. The elements of ETMP configurator/executor  700  depicted in  FIG. 7  may be physically implemented as a single, self-contained device. In certain implementations, ETMP configurator/executor  700  may alternatively be implemented using a number of different devices that are physically separated, but coupled together for centralized control. It is noted that ETMP configurator/executor  700  may include additional components, such as a power supply and a cooling element, which have been omitted from  FIG. 7  for clarity. As shown in  FIG. 7 , ETMP configurator/executor  700  may operate in conjunction with ETMP  170  (see also  FIGS. 1 and 3 ) to execute the methods and operations described herein. In certain embodiments, ETMP configurator/executor  700  may represent a virtualized computing environment, wherein certain elements depicted in  FIG. 7  are shared or represent virtualized components. 
     In the embodiment depicted in  FIG. 7 , ETMP configurator/executor  700  includes processor  701  coupled via shared bus  702  to storage media collectively identified as memory media  710 . ETMP configurator/executor  700 , as depicted in  FIG. 7 , further includes network adapter  720  that interfaces ETMP configurator/executor  700  to a network (not shown in  FIG. 7 ), such as ETMP network  240  (see  FIG. 2 ). In embodiments suitable for use with ETMP  170 , ETMP configurator/executor  700 , as depicted in  FIG. 7 , may include peripheral adapter  706 , which provides connectivity for the use of input device  708  and output device  709 . Input device  708  may represent a device for user input, such as a keyboard or a mouse, or even a video camera. Output device  709  may represent a device for providing signals or indications to a user, such as loudspeakers for generating audio signals. 
     ETMP configurator/executor  700  is shown in  FIG. 7  including display adapter  704  and further includes a display device or, more simply, a display  705 . Display adapter  704  may interface shared bus  702 , or another bus, with an output port for one or more displays, such as display  705 . Display  705  may be implemented as a liquid crystal display screen, a computer monitor, a TV or the like. Display  705  may comply with a display standard for computer monitors and/or TV displays. Standards for computer monitors include analog standards such as VGA, XGA, etc., or digital standards such as DVI and HDMI, among others. A television display may comply with standards such as NTSC, PAL, or another suitable standard. Display  705  may include one or more integrated speakers to play audio content. 
     Memory media  710  encompasses persistent and volatile media, fixed and removable media, and magnetic and semiconductor media. Memory media  710  is operable to store instructions, data, or both. Memory media  710  as shown includes sets or sequences of instructions  724 - 2 , namely, an operating system  712 , ETMP script(s)  714 , and ETMP studio application  400 . Operating system  712  may be a UNIX or UNIX-like operating system, a Windows® family operating system, or another suitable operating system. Instructions  724  may also reside, completely or at least partially, within processor  701  during execution thereof. It is further noted that processor  701  may be configured to receive instructions  724 - 1  from instructions  724 - 2  via shared bus  702 . ETMP script(s)  714  may represent a sequence of test operations generated by user input to ETMP studio application  400 , as described previously. ETMP script(s)  714  may be generated using ETMP studio application  400 , which may provide ETMP configurator functionality. ETMP script(s)  714  may also be executed using ETMP executor functionality. 
     To the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited to the specific embodiments described in the foregoing detailed description.