A TASK ORIENTED GRAPHICAL USER INTERFACE FOR A COMMUNICATION TEST SET

Abstract: GUI 20 requires a highly skilled user to properly configure the test set for specific test being performed and to properly interpret the results of the test. In addition, the conventional GUI 20 increases the likelihood of user error when the test set is being configured and when the test results are interpreted given the large number of configuration options and test results that are presented to the user. It is accordingly an object of the present invention to provide a communication test set with a GUI that will allow a technician using the test to input the task required of the test set. Based on this selected task, the test set will automatically configure itself thus 20 minimizing the risk of an error in the configuration process. It is another object of the invention to provide a communication test set with a GUI that will allow a technician using the test set to input the task required of the test set and, based on this selected task, the GUI will present only those test results that are relevant thus minimizing the risk of error when test results are interpreted.

Description: A TASK ORIENTED GRAPHICAL USER INTERFACE FOR A COMMUNICATION TEST SET BACKGROUND A) FIELD OF INVENTION The present invention relates to a communication test set and more particularly to a communication test set with a task oriented graphical user interface. B) DESCRIPTION OF RELATED ART Figure 1 shows a conventional communication test set 10 which is used to test numerous types of communication networks. The communication test set 10 is typically used to test a network that employs a variety of different physical interfaces. In particular, the communication test set 10 is generally used to test a network that contains a TI physical interface, a DDS LL physical interface, an ISDN BRI physical interface, a Datacom physical interface, and/or an Analog physical interface. To perform the necessary testing of these physical interfaces, the communication test set 10 contains numerous components. Specifically, the communication test set 10 includes transmit and receive ports 12, 14 and 16 to receive signals from the communication links that will be tested and to transmit tested signals to other devices and ports. The test set 10 also includes a front panel of LED's 18 to provide immediate visual feedback on the status of a test. Green LED's generally indicate that the signal is present and the communication test set is synchronized to a network. Red LED's generally indicate that errors and alarms have been detected by the communication test set 10. The conventional test set 10 also includes a graphical user interface (GUI) 20 that contains various formats of information which allow a user to program the communication test set for a desired test. Specifically, the GUI 20 allows the user to (i) select the physical interface being tested, (ii) select the type of test that is to be performed by the test set, (iii) configure the communication test set for the specific test that has been selected, and (iv) view the test results once the test has been completed. Figures 2 through 11 show the various screens of the GUI 20 which allow a user to perform these four functions. Each of these screens is described in greater detail below. Figure 2 represents a main screen of the GUI 20 used by the test set 10 that allows a user to select the type of physical interface which is being tested. To accommodate this selection process, the GUI 20 shown on Figure 2 contains an interface field 22. The options available to the user for this field include a TI interface option, a DDS-LL interface option, an ISDN BRI interface option, a Datacom interface option, and an Analog interface option. The user selects one of these options by using a combination of the scroll buttons and softkeys shown on Figure 1. The GUI 20 shown in Figure 2 also requires the user to select the type of test to be performed by the communication test set 10. To accommodate this selection process, the GUI 20 shown on Figure 2 contains a test type field 24. In this example, the user has already selected a test known as the BERT test from a list options containing numerous tests that are 20 capable of being performed by the test set 10. Figure 3 shows an example of a GUI 20 that is displayed on the test set 10 after the user has made the selections shown on Figure 2. Once these selections have been made, the user will be required to manually configure the test set 10. In particular, referring to Figure 3, once the interface has been selected as DDS-LLL and the test type has been selected as BERT, the user will be required to configure the test set 10 by programming fields 26 through 44. There are numerous configuration options available for each of fields 26 through 44. For example, for the mode field 26 there are numerous options that can be selected by the user to configure the test set 10. In this specific instance, the user has already selected the TERMINATE option for this field. This option is selected by the user, as is known in the art, by using a combination of the scroll keys and soft keys shown on Figure 1. To completely configure the test set 10, the user is required to perform this selection process for each of the fields 26-44 shown on Figure 3. That is, the user is required to perform this selection process for the emulate field 28, the primary rate field 30, the secondary channel field 32, the LBO field 34, the TX clock field 36, the Loop Resp. Field 38, the pattern field 40, the Blk type field 42, and the Err Ins Type field 44. Once the configuration is completed by the user, the testing of the physical interface and line service can be performed. The results of such a test are shown on the screens of the GUI 20 illustrated in Figures 4 through 11. Figure 4 shows a screen of a GUI 20 which 20 provides a text summary of the test results. Figure 5 shows a screen of a GUI 20 which indicates if any alarms have been detected by the test. Figures 6-11 present a series of screens of the GUI 20 which contain an exhaustive list of all of the results related to the test. After the test is performed, the user of the test set 10 is then required to study and evaluate the data contained on the numerous screens of the GUI shown in Figures 4-11. Based on this data, the user will then determine if this physical interface and line service is operating properly or if there is an operational problem with the interface. The conventional GUI 20 described above and shown in Figures 1 -11, while useful, does have significant drawbacks. In particular, the conventional GUI 20 requires a highly skilled user to properly configure the test set for specific test being performed and to properly interpret the results of the test. In addition, the conventional GUI 20 increases the likelihood of user error when the test set is being configured and when the test results are inteφreted given the large number of configuration options and test results that are presented to the user. These limitations are of particular significance given that they result in an unusually high number of improper tests and improper interpretation of test results. In view of this problem, there currently exists a need for a communication test set with a GUI that will allow a user to easily configure the test set for a specific test and easily interpret the test results of such a test. OBJECTS AND SUMMARY OF THE INVENTION It is accordingly an object of the present invention to provide a communication test set with a GUI that will allow a technician using the test set to input the task required of the test set. Based on this selected task, the test set then will automatically configure itself thus 20 minimizing the risk of an error in the configuration process. It is another object of the invention to provide a communication test set with a GUI that will allow a technician using the test set to input the task required of the test set and, based on this selected task, the GUI will present only those tests results that are relevant thus minimizing the risk of error when test results are interpreted. In accordance with one embodiment of the invention, a programmable graphical user interface (GUI) for use in a communication test set which conducts line tests on one or more different physical interfaces contained within a communication network is disclosed, where the GUI comprises: a first selection means for allowing a user of the test set to select a type of physical interface to be tested; a second selection means for allowing, a user of the test set to select a task to be performed by the test set based on the physical interface selected; and a third selection means for allowing a user of the test set to select a test to be performed by the test set based on the task selected. In accordance with another aspect of this embodiment of the invention a predetermined number of features of the test set are automatically configured based on the physical interface, task and test selected. In accordance with still another aspect of this embodiment of the invention, the results to be displayed on the test set are automatically configured based on the physical interface, task and test selected. In accordance with another embodiment of the invention, a method of configuring a test set for testing a communications network is disclosed, where the method comprises the steps of: (a) presenting a selection of physical interfaces to be selected; (b) presenting a selection of tasks to be performed by the test set based on the physical interface selected; (c) presenting a selection of tests to be performed by the test set based on the task selected; and, (d) automatically configuring predetermined features of the test set based on the physical interface, task and test selected. In accordance with even still another embodiment of the invention, a programmable graphical user interface (GUI) for use in a communication test set which conducts line tests on one or more different physical interfaces contained within a communication network is disclosed, where the GUI comprises: a task selection means for allowing a user of the test set to select a task to be performed by the test set; and a test selection means for allowing a user of the test set to select a test to be performed by the test set based on the task selected. In accordance with another aspect of this embodiment of the invention, a predetermined number ot " features of the test set are automatically configured based on the task and test selected. In accordance with even another aspect of this embodiment of the invention, the results of the tests to be displayed on the test set are automatically configured based on the task and test selected. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings are included to provide an understanding of the invention and constitute a part of the specification. Figure 1 illustrates a conventional communication test set; Figure 2 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 3 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 4 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 5 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 6 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 7 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 8 illustrates a conventional GUI used by the communication test shown in Figure 1 ; Figure 9 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 10 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 11 illustrates a conventional GUI used by the communication test set shown in Figure 1 ; Figure 12 illustrates a GUI developed in accordance with the present invention for use in a communication test; Figure 13 illustrates a GUI developed in accordance with the present invention for use in a communication test; Figure 14 illustrates a GUI developed in accordance with the present invention for use in a communication test; Figure 15 illustrates a GUI developed in accordance with the present invention for use in a communication test; Figure 16 illustrates a GUI developed in accordance with the present invention for use in a communication test; Figures 17(a) through 17(b) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the TI Bert Turn-Up is selected by the user of the test set for a TI physical interface; Figures 18(a) through 18(c) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the T1/FT1 FR Turn-Up is selected by the user of the test set for a TI physical interface; Figures 19(a) through 19(b) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the DDS Bert Turn-Up is selected by the user of the test set for a TI physical interface; Figures 20(a) through 20(b) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the DDS FR Turn-Up is selected by the user of the test set for a TI physical interface; Figures 21 (a) through 21 (b) illustrate an information matrix.that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the FT1 Bert Turn-Up is selected by the user of the test set for a TI physical interface; Figures 22(a) through 22(b) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the PBX/Switch Turn -Up is selected by the user of the test set for a TI physical interface; Figures 23(a) through 23(c) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the ISDN/PRI Turn -Up is selected by the user of the test set for a TI physical interface; . Figures 24(a) through 24(b) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Monitor is selected by the user of the test set for a TI physical interface; Figure 25 illustrates an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when tasks known as DDS Bert Turn -Up and DDS Bert Trouble are selected by the user of the test set for a DDS-LL physical interface; Figures 26(a) through 26(b) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the Frm Relay Turn -Up is selected by the user of the test set for a DDS-LL physical interface; Figure 27 illustrates an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Monitor is selected by the user of the test set, for a DDS-LL physical interface; Figure 28 illustrates an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the Line Qualify is selected by the user of the test set for an ISDN BRI physical interface; Figures 29(a) through 29(c) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Circuit Calls is selected by the user of the test set for a ISDN BRI physical interface; Figures 30(a) through 30(b) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Packet Calls is selected by the user of the test set for a ISDN BRI physical interface; Figure 31 illustrates an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Bert Turn -Up is selected by the user of the test set for a Datacom physical interface; Figures 32(a) through 32(c) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the Frame Relay Turn -Up is selected by the user of the test set for a Datacom physical interface; Figure 33 illustrates an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Monitor is selected by the user of the test set for a Datacom physical interface; Figures 34(a) through 34(b) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as WB Data Turn -Up is selected by the user of the test set for an Analog physical interface; Figures 35(a) through 35(c) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the Voice Turn -Up is selected by the user of the test set for an Analog physical interface; and Figures 36(a) through 36(c) illustrate an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as VF Data Turn -Up is selected by the user of the test set for an Analog physical interface. DETAILED DESCRIPTION OF THE INVENTION Figure 12 shows a screen of GUI 50 for a communication test set developed in accordance with the present invention. The GUI 50 allows a user to select the type of physical interface which is being tested. To accommodate this selection process, the GUI 50 shown on Figure 12 contains an interface field 52. The options available to the user for field 52 include a TI interface option, a DDS-LL interface option, an ISDN BRI interface option, a Datacom interface option, and an Analog interface option. The user selects one of these options by using a combination of the scroll buttons and softkeys on the communication test set. In this specific example, the user has selected a DDS-LL interface. Figure 13 shows another screen of GUI 50 for a communication test set developed in accordance with the present invention. The GUI 50 shown in Figure 13, unlike any known conventional communication test set, allows a user to select a specific task to be performed by the communication test set for type of physical interface selected. To accommodate this task selection process, the GUI 50 shown on Figure 13 contains a task field 54. There are numerous options available to the user for field 54. Each of these option will be described in greater detail below. The user selects one of the task options by using a combination of the scroll buttons and softkeys on the communication test set. In this specific example, the user has selected a task known as DDS Bert Turn-Up. Figure 14 shows a third screen of the of a GUI 50 for a communication test set 20 developed in accordance with the present invention. The GUI 50 shown in Figure 14, again unlike any known conventional communication test set, allows a user to select a specific test to be performed by the communication test set based on the both the type of physical interface selected and the type of task selected. To accommodate this test selection process, the GUI 50 shown on Figure 14 contains a test field 56. There are numerous options available to the user for test field 56. Here again, each of these option will be described in greater detail below. The user selects one of these options by using a combination of the scroll buttons and softkeys on the communication test set. In this specific example, the user has selected a test known as Receive Loop Back. After the above three selections are made, the test set automatically configures itself to perform the specific task and test selected. In particular, after selections are made for fields 52, 54 and 56, the test set selects a predetermined default setting for a number of parameters that need to be configured before the test can be performed. The automated selection of defaults for these configuration parameters eliminates the need for the user of the test set to manually input selections for these parameters. A small number of configuration parameters are, however, presented on the screen of the GUI 50 for approval and/or modification by the user of the test set. Figure 15 shows a screen of the GUI 50 which presents configuration parameters 58-60 that require approval and/or modification by the user. Defaults for parameters 58-60 are automatically selected for the interface, task and test selected in Figures 12-14. The user of the test set can either accept these defaults or changes them depending on the circumstances of the individual test being conducted. After the fields of information shown on Figure 15 are either accepted or modified, the communication test set runs the test and presents the results of the test on the GUI 50. Figure 16 shows a screen of the GUI 50 which presents the test results. These results typically are the most common results of interest to the user for the task and test selected. Another important feature of the GUI 50 developed in accordance with present invention is that the user of the test set can easily return to screen 12 at any time simply by pushing the home button of the test set. This one button approach allows the user to begin the task based programming selection at any time simply by pushing one button. The test set and GUI 50 developed in accordance with the present invention can perform a number of task-based tests for each of the five physical interfaces described above. A detailed description of each of the task-based tests that can be performed for each physical interface is presented below. TASK-BASED TESTS PERFORMED FOR TI PHYSICAL INTERFACE Numerous task-based tests can be performed by a test set developed in accordance with present invention for a TI physical interface. Each of these tests is described in detail with reference to Figure 17 through Figure 24. Figures 17(a) through 17(b) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the TI Bert Turn-Up is selected by the user of the test set for a TI physical interface. This task is usually selected when the user is located at the customer premise, at the Network Interface Unit (NIU), or at a HTU-R. When this task is selected, the test set is emulating a CSU. Also, when this task is selected, the connection is most likely a bantam into the test set to a RJ-48 cable into the NIU. As is indicated on Figure 17(a) and 17(b), when the TI Bert Tun-Up task is selected, three specific tests can be selected. These three tests are known as the Receive Loopback - Term, Send Loopback - Term, and Straightway Bert - Term. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figures 17(a) and 17(b). The Receive Loopback - Term tests is typically selected when the test set is being used as a loopback device. Ideally, in this instance, the user is waiting for a loopback code (e.g., a CSU loop) to be sent from a centralized tester or from a test set located in the CO. The objective of this test is to perform a TI qualification test. While in this passive loopback mode, the user can view signal level, signal frequency, BPVs and bit errors while the test is being run. This test provides a method of isolating the problem to a specific piece of equipment or section of the loop. The Send Loopback - Term test is typically selected when the test set is being used to generate a loopback code for a device located at either at the customer premise (e.g., a CSU) or within the network. In this instance, the test set can be used to send a HDSL loopcode to a doubler or to a HTU-C or to send a NIU a smart repeater or loopcodes. Here, the user of the test set is typically is control of the test. The objective of this test is to perform a TI qualification test. While in this passive loopback mode, the user can similarly view signal level, signal frequency, BPVs and bit errors while the test is being run. This test provides a method for isolating the problem to a specific piece of equipment or section of the loop. The Straightway Bert - Term test is typically selected when the test set is being used as one test set at the customer premise, while another test set is located at a location remote from the customer site, typically at the CO ir at the DSX patch panel. When this test is selected, testing and analysis are performed in both directions. Again, the objective of this test is to perform a TI qualification test. While in this passive loopback mode, the user can view signal level, signal frequency, BPVs and bit errors while the test is being run. This test provides a method of isolating the problem to a specific piece of equipment or section of the loop. Figures 18(a) through 18(c) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the T1/FT1 FR Turn -Up is selected by the user of the test set for a TI physical interface. This task is usually selected when the user is at the customer premise and is using the test set to emulate a router. In "this situation, the connection is most likely a bantam into the test set to an RJ-48 cable able into the CSU. As is indicated on Figures 18(a) through 18(c), when the T1/FT1 FR Turn Up task is selected, three specific tests can be selected. These three tests are known as the LMI/PVC Check test, the Cir Check test, and the Ping Far End test. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figures 18(a) through 18(c). The LMI/PVC Check test is typically selected when it is assumed that the TI physical layer has already been tested. To perform this test, the test set is plugged into the circuit after the actual frame relay service that has been turned on by the NOC. Since this test entails just 20 connecting to the circuit and gathering results, it is a one-man test. This test is typically used as a first step to testing a frame relay circuit. The objective of this test is to verify that the Link Management Interface (LMI) is 17 functioning properly and that all expected DLCI's have Permanent Virtual Circuits(PVCs), that are properly configured and active. The Cir Check test is typically selected when it is assumed that the DDS physical layer and a LMI/PVC check have already been tested. To perform this test, the test set is plugged into the circuit after the actual frame relay service that has been turned on by the NOC. The test set is used to send/receive frames with another test set located within the CO or within the NOC responsible for Packet Switched Services. Under these circumstances, testing can also be performed to a soft loopback within the POP frame relay switch or to a hard loopback within the CO or at the far-end. The objective of this test is to verify that the customer is provided actual frame relay service at their Committed Information Rate (CIR), without losing frames due to congestion, improper Discard Eligibility (DE) flags, or incorrect PVC configurations. While this test is being conducted, physical layer results may also be viewed. The Ping Far end tests is typically selected when it is assumed that the TI physical layer and a LMI/PVC check have already been tested. To perform this test, the test set is plugged into the circuit after the actual frame relay service that has been turned on by the NOC. This test entails just connecting to the circuit sending/receiving a ping to a currently installed IP device such as a far end router and is therefore a one-man test. The objective of the test is to test connectivity to a far-end router without taking it 20 out-of-service. In this mode, the user can send IP Pings to an installed IP address (typically another router) in the network. The goal is to ensure that all IP ping messages that are sent to the far-end device are responded back with an echo reply. Figures 19(a) through 19(b) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the DDS Bert Turn-Up is selected by the user of the test set for a TI physical interface. This task is usually selected when the user is located within a central office, typically at a DSX patch panel. In this circumstance, the test set is emulating a CSU. Also, in this situation, the connection is typically bantam-to-bantam. As is indicated on Figures 19(a) through 19(b), when the DDS Bert Turn-Up task is selected, two specific tests can be selected. These two tests are known as the Straightaway - D&I test and the Send Loopback - D&I test. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figures 19(a) through 19(b). The Straightaway - D&I test is typically selected when the test set is being used as one test set within the Central Office, while another test set is located at a remote location, typically the customer premise at a NID. Testing and analysis is performed in both directions. The objective of this test is to perform a DDS qualification test from a TI access point. While in this mode, the user can view signal level, signal frequency, BPVs and bit errors while the test is being run. When this test is being performed, the DDS circuit under test is out-of-service while the remaining DSO's are in-service. This test provides a preferred method of sectionalizing a trouble and verification during a turn-up than loopback testing. The Send Loopback - D&I test is typically selected when the.test set is being used to generate a loopback code to a device located at either at either (1) the customer premise (such as the CSU/DSU), (2) the local loop (such as a repeater), or (3) within the network (such as 19 an OCU-DP or DSO-DP card). The objective of this test is to perform a DDS qualification test from a TI access point. While in this mode, the user can view signal level, signal frequency, BPVs and bit errors while the test is being run. Here again, when the test is being performed, the DDS circuit under test is out-of-service, while the remaining DSO's are in-service. Figures 20(a) through 20(c) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the DDS FR Turn-Up is selected by the user of the test set for a TI physical interface. This task is usually selected when the user is located within a central office, typically at a DSX patch panel. When this task is selected, the test set is emulating a router. In this situation, the connection is typically bantam-to-bantam. As is indicated on Figures 20(a) through 20(c), when the DDS FR Turn-UP task is selected, three specific tests can be selected. These three tests are known as the LMI/PVC Check test, the Cir Check test, and the Ping Far End test. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figures 20(a) through 20(c). The LMI/PVC Check test is typically selected when it is assumed that the DDS physical layer has already been tested. The test set is plugged into the circuit after the actual frame relay service has been turned on by the NOC. This test entails just connecting to the 20 circuit and gathering results and therefore is a one-man test. This test is the preferred first step to testing a frame relay circuit. The objective of this test is to test and verify that the Link Management Interface (LMI) is functioning properly and that all expected DLCIs have Permanent Virtual Circuits (PVCs) that are properly configured and active. The Cir Check test is typically selected when is assumed that the DDS physical layer and a LMI/PVC check have already been tested. The test set is plugged into the circuit after the actual frame relay service has been turned on by the NOC. When this test is selected, the test set is used to send and receive frames with another test set located within the CO or within the NOC responsible for Packet Switched Services. Under these circumstances, testing can also be performed to a soft loopback within the POP frame relay switch or to a hard loopback within the CO or at a remote location. The objective of this test is verify that the customer is provided actual frame relay service at their Committed Information Rate (CIR), without losing frames due to congestion, improper Discard Eligibility (DE) flags or incorrect PVC configurations. When this test is being performed, physical layer results may also be viewed. The Ping Far end test is typically selected when it is assumed that the DDS physical layer and a LMI/PVC check have already been tested. The test set is plugged into the circuit after the actual frame relay service that has been turned on by the NOC. This test entails just connecting to the circuit sending and receiving a ping to a currently installed IP device such as a far end router and therefore is a one-man test. The objective of this test is to test the connectivity of a line to a remote router without taking it out-of-service. In this mode, the user can send IP Pings to an installed IP address (typically another router) in the network. The goal of the test is to ensure that all IP pings 21 messages that are sent to the far-end device are responded back with an echo reply. Figures 21(a) through 21(c) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the FT1 Bert Turn-Up is selected by the user of the test set for a TI physical interface. This task is usually selected when the user is located within a central office, typically at a DSX patch panel. When this task is selected, the test set is emulating a CSU. In this situation, the connection is typically bantam-to-bantam. As is indicated on Figures 21(a) through 21(c), when the FT1 Bert Turn-Up task is selected, four specific tests can be selected. These four tests are known as the StraightAway - D&I test, the Send Loopback - Term test, the RCV Loopback - Term test, and the StraightAway - Term test. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figures 21(a) through 21(c). The StraightAway - D&I test is typically selected when the test set is being used as one test set within the Central Office, while another test set is located at a remote location, typically the customer premise at a NID. Under these circumstances, testing and analysis is performed in both directions. This test is preferred over a loopback test when attempting to sectionalize a problem and perform a verification during a turn-up. The objective of this test is to perform fractional TI qualification tests from a TI access point. While in this mode, the user can view signal level, signal frequency, BPVs and 20 bit errors while the test is being run. Also, when this test is being performed, the fractional DSO's under test are out-of-service while the remaining DSOs are in-service. The Send Loopback - Term test is typically selected when the test set is being used 22 to generate a V.54 loopback code to the CSU/DSU located at the customer premise. This will loopback the fractional bandwidth. Under these circumstance, the user is typically in control of the test. The objective of this test is to perform fractional TI qualification tests from a TI access point. While in this mode, the user can view signal level, signal frequency, BPVs, and bit errors while the test is being run. Also, when this test is being performed, the fractional DSO's under test are out-of-service, while the remaining DSO's are in-service. This test provides a preferred method of isolating the problem to a specific piece of equipment or portion of the loop. The RCV Loopback - Term test is typically selected when the test set is being used as a loopback device. Ideally, the user of test set is waiting for a loopback code to be sent from a centralized tester or from a test set located in the CO. The remote tester is typically in control of the test. The objective of this test is to perform a TI qualification test on a fractional bandwidth. While in this passive loopback mode, the user of the test set can view signal level, signal frequency, BPVs and bit errors while the test is being preformed. This test provides a preferred method of isolating the problem to a specific piece of equipment or portion of the loop. The StraightAway - Term test is typically selected when test set is being used as one 20 test set at the customer premise, while another test set is located at a remote location, typically the CO at a DSX patch panel. Testing and analysis is performed in both directions. This test is preferred over a loopback test when attempting to sectionalize a problem trouble 23 and perform verification during a turn-up. The objective of this test is to perform a TI qualification test on a fractional bandwidth. While in this mode, the user of the test set can view signal level, signal frequency, BPVs and bit errors while the test is being run. Figures 22(a) through 22(b) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the PBX/Switch Turn-Up is selected by the user of the test set for a TI physical interface. This task is usually selected when the user is located at the customer premise at the Network Interface Unit (NIU) or at a HTU-R. When this task is selected, the test set is emulating a PBX or CO Switch. As is indicated on Figures 22(a) through 22(b), when the PBX/Switch Turn-Up task is selected, three specific tests can be selected. These three tests are known as the Voice Call - Term test, the Voice Call - D&I test, and the TIMS - Lvl/Noise - D&I test. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figures 22(a) through 22(b). The Voice Call - Term test is typically selected after the TI physical layer has been tested and the actual voice service has been activated by the switch technician. Normally, during this test, a call is placed to any known telephone number. In this situation, the connection is most likely a bantam into the test set to N RJ-48 cable into the NIU. The objective of this test is to verify a circuit's ability to place or receive a voice call while at a TI access point. This test will verify that there are no problems associated with improper timing, improper number of digits, wrong digit type, and/or overall switch translations. The Voice Call - D&I test is typically selected after the TI physical layer has been tested and the actual voice service has been activated by the switch technician. Normally, during this test, a call is placed to any known telephone number. In this situation, the connection is typically bantam-to-bantam . The objective of this test is to verify a circuit's ability to place or receive a voice call through a CO switch from a TI access point. This test will verify that there are no problems associated with improper timing, improper number of digits, wrong digit type, and/or overall switch translations. The TIMS - Lvl/Noise - D&I test is typically selected when the test set is used to perform a TIMS measurement along with another analog TIMS unit located on a two wire pair at the customer premise. The access at the customer premise is typically a punch down block. In this situation, the connection is also typically bantam-to-bantam. The objective of this test is to verify that the DSO does not have excessive loss or noise which will result in poor voice quality. Usually a 1004Hz loss or C-message noise measurement is made when this test is performed. Figures 23(a) through 23(c) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the ISDN PRI Tum-Up is selected by the user of the test set 20 for a TI physical interface. This task is usually selected when the user is located either within a central office, typically at a DSX patch panel, or at the customer premise at the Network Interface Unit (NIU) or at a HTU-R. When this task is selected, the test set is emulating a PBX. In this situation, the connection is typically bantam-to-bantam if at a DSX patch panel or bantam into the test set to an RJ-48 cable into the NIU. As is indicated on Figures 23(a) through 23(c), when the ISDN PRI Turn-Up task is selected, three specific tests can be selected. These three tests are known as the NFAS/DCBU (46B+2d) test, the Multiple (47B + D) test, and the Single (23B+D) test. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figures 23(a) through 23(c). The NFAS/DCBU (46B+2d) test is typically selected when the test set is used to place and receive voice and data calls to either a known telephone number or to an ISDN test line such as the TPI 560P. The objective of this test is to verify the circuit's ability to place and receive voice and data calls through the CO switch and then perform a BER test, if applicable. This test will verify that there are no problems associated with improper switch translations, service configurations, specific DSO errors, or D Channel signaling. The Multiple (47B + D) test is typically selected when test set is used to place and receive voice and data calls to either a known telephone number or to an ISDN test line such as the TPI 560P. The objective of this test is again to verify the circuit's ability to place and receive voice and data calls through the CO switch and then perform a BER test, if applicable. This 20 will verify that there are no problems associated with improper switch translations, service configurations, specific DSO errors, or D Channel signaling. The Single (23B+D) test is typically selected to verify the circuit's ability to place and receive voice and data calls through the CO switch and then perform a BER test, if applicable. This will verify that there are no problems associated with improper switch translations, service configurations, specific DSO errors, or D Channel signaling. The objective of this test is also to verify the circuit's ability to place and receive voice and data calls through the CO switch and then perform a BER test, if applicable. This will verify that there are no problems associated with improper switch translations, service configurations, specific DSO errors, or D Channel signaling. Figures 24(a) through 24(b) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Monitor is selected by the user of the test set for a TI physical interface. This task is usually selected when the user is located either within a central office, typically at a DSX patch panel, or at the customer premise at the Network Interface Unit (NIU) or at the HTU-R. In this situation, the connection is typically either bantam-to-bantam, if at a DSX patch panel, or bantam into the test set to an RJ-48 cable into the NIU. As is indicated on Figures 24(a) through 24(b), when the Monitor task is selected, five specific tests can be selected. These five tests are known as the Frame Relay test, the Bert test, the Timing Slips test, the ISDN PRI test, and the Voice test. The default settings 20 for each of these tests, along with the set-up configuration and test result are also shown on Figures 24(a) through 24(b). The Frame Relay test is typically selected when the user merely connects to the monitor point and begins reviewing the displayed results. The objective of this test is to verify that the live frame relay traffic is be transmitted without excessive congestion and at the proper rate. Results such as FCS errors, frame rate, utilization, along with physical layer results can be viewed. The Bert test is typically selected when the user merely connects to the monitor point and begins reviewing the displayed results. The objective of this test is to passively monitor various TI results such as receive level, receive frequency, BPVs and CRCs. The Timing Slips test is typically selected when the user merely connects to the monitor point and begins reviewing the displayed results. The objective of this test is to passively monitor the timing between two TI signals for timing slips. In addition, various TI results such as receive level, receive frequency, BPVs, CRCs, and ABCD signaling bits can be gathered during this test. The ISDN PRI test is typically selected when the user merely connects to the monitor point and begins reviewing the displayed results. The objective of this test is to passively verify the ability place and receive calls between the PBX and the CO switch by looking at live calls, TI results, and actual D channel decodes. In addition, TI physical layer results such as receive level, receive frequency, BPVs, and CRCs can be gathered during this test. The Voice test is typically selected when the user merely connects to the monitor point and begins reviewing the displayed results. The objective of this test is to verify the ability place and receive calls between the PBX and the CO switch by looking at the completion of live calls. In addition, various TI results such as receive level, receive frequency, BPVs, CRCs, and ABCD signaling bits can be gathered during this test. TASK-BASED TESTS PERFORMED FOR DDS-LL PHYSICAL NTERFACE. Numerous task-based tests can be performed by a test set developed in accordance with present invention for a DDS-LL physical interface. Each of these tests are described in detail with reference to Figure 25 through Figure 27. Figure 25 represents an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as the DDS Bert Turn -Up is selected by the user of the test set for a DDS-LL physical interface. This task is usually selected when the user is at the customer premise and the test set is being used to emulate a CSU/DSU, or when the test set is plugged directly into the a CSU/DSU. This task is also selected when the user is at the crossbox in the field and within 18,000 feet of the CSU/DSU and the test set is being used to emulate a router. Also, when this task is selected, the connection is most likely an RJ-45 to RJ-45 cable which is fed into the LINE side of the NID or DDS termination unit if the test set is located at the CSU/DSU or an RJ-45 to alligator clips if the test set is located at a crossbox. As is indicated on Figure 25, when the DDS Bert Tun-Up task is selected, three specific tests can be selected. These three tests are known as the Receive Loopback test, the Straightaway test, and the Send CSU Loopback test. The default settings for each of these tests, along with the set-up configuration and test results are also shown on Figure 25. The Receive Loopback test is typically selected when the test set is being used as a loopback device. In this circumstance, the user of the test set is waiting for a loopback code to be sent from a centralized tester or from a test set located in the CO. The objective of this test is to perform DDS qualification tests. While in this passive mode, the user can view signal level, signal frequency, BPVs, bit errors, and sealing current while the test is being run. The Straightaway test is typically selected when the test set is being used as one test set at customer premise, while another test set is located at a remote location, typically the CO at a DSX panel. Under this scenario, testing and analysis is performed in both directions. This test is a preferred when sectionalizing a problem and performing a verification during turn-up. The objective of this test is to perform DDS qualification tests. While in this mode, the user can view signal level, signal frequency, BPVs, bit errors, and sealing current while the test is being run. The Send CSU Loopback test is typically selected when it is assumed that the DDS physical layer has already been tested. This test is used as a method of troubleshooting the customer's CSU/DSU to isolate the provider's network as a source of the problem. The technician can then use a CSU/DSU loopcode to loop up the CSU/DSU and perform BER testing. This is a one-man test. The objective of this test is to perform DDS qualification tests. While in this mode, the user can view signal level, signal frequency, BPVs, bit errors and sealing current while the test is being run. This test provides a method of isolating the problem to the CSU/DSU or the wiring between the NID and the CSU. Figures 26(a) through 26(b) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Frm Relay Turn-Up is selected by the user of the test set for a DDS-LL physical interface. This task is usually selected when the user is located at the customer premise and is using the test set to emulate a router. In this situation, the connection is most likely an RJ-45 to RJ-45 cable which is fed into the NID or DDST. As is indicated on Figures 26(a) through 26(b), when the Frm Relay Turn-Up task is selected, three specific tests can be selected. These three tests are known as the LMI/PVC test, the Ping Far End test, and the Cir Check test. The default settings for each of these tests, along with the set-up configuration and test results are also shown on Figures 26(a) through 26(b). The LMI/PVC test is typically selected when it is assumed that the DDS physical layer has already been tested. The test set is plugged into the circuit after the actual frame relay service has been turned on by the NOC. Since this test entails just connecting to the circuit and gathering results it is therefore a one-man test. This test is preferred as a first step to testing a frame relay circuit. The objective of the test is to test and verify that the Link Management Interface (LMI) is functioning properly and that all expected DLCI's have Permanent Virtual Circuits (PVCs) that are properly configured and active. The Ping Far End test is typically selected when it is assumed that the DDS physical layer and a LMI/PVC check have already been tested. The test set is plugged into the circuit after the actual frame relay service has been turned on by the NOC. Since this test entails just connecting to the circuit sending/receiving a ping to a currently installed IP device such as a remote router, it is therefore a one-man test. The objective of the test is to test the connectivity to a far-end router without taking it out-of-service. In this mode, the user can send IP Pings to an installed IP address (typically another router) in the network. The goal is to ensure that all IP ping messages that are sent to the far-end device are responded back with an echo reply. The Cir Check test is typically selected when it is assumed that the DDS physical layer and a LMI/PVC check have already been tested. The test set is plugged into the circuit after the actual frame relay service has been turned on by the NOC. Under these circumstances, the test set is used to send/receive frames from another test set located within the CO or from the NOC responsible for Packet Switched Services. With this test, testing can also be performed to a soft loopback within the POP frame relay switch or to a hard loopback within the CO or at the far-end. The objective of the test is to verify that the customer is provided actual frame relay service at their CIR, without losing frames due to congestion, improper Discard Eligibility (DE) flags and incorrect PVCs. Figure 27 represents an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Monitor is selected by the user of the test set for a DDS-LL physical interface. This task is usually selected when the user is at the customer premise and is using the test set in a passive monitoring mode. As is indicated on Figure 27, when the Monitor task is selected, two specific tests can be performed. These two tests are known as the Frame Relay and the Bert test. The default settings for each of these tests, along with the set-up configuration and test results are also shown on Figure 27. The Frame Relay test is typically selected when the customer is sending live data into the CSU/DSU via a router, while the test set is passively monitoring the circuit through the high impedance cable. When this test is selected, the user is able to view results coming from the CO and the customer's equipment. The objective of this test is to isolate and sectionalize the problem to either the network or the customer premise by using actual customer data. This test would normally be used for chronic troubles. Association between physical layer errors such as DDS frame errors and layer two protocol errors such as frame relay frame errors can be seen when this test is being performed. FCS errors, frame counts, DLCl status can also be viewed for either the entire link or a particular DLCl along with physical layer results when the test is being performed. The Bert test is typically selected when the customer is sending live data into the CSU/DSU via a router, while the test set is passively monitoring the circuit through the high impedance cable. When this test is selected, the user is able to view results coming from the CO and the customer's equipment. The objective of this test is to passively monitor the physical layer results and then isolate the problem to either the CSU/DSU or the network. TASK-BASED TESTS PERFORMED FOR ISDN-BRI PHYSICAL INTERFACE Numerous task-based tests can be performed by a test set developed in accordance with present invention for an ISDN-BRI physical interface. Each of these tests are described in detail with reference to Figure 28 through Figure 30. Figure 28 represents an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Line Qualify is selected by the user of the test set for a ISDN BRI physical interface. This task is usually selected when the user is located at either the U interface at the customer premise (emulating a Network Termination device) or at the CO (emulating a Line Termination device). In this situation, the connection is most likely an RJ-48 to RJ-48 cable at the U interface. When located at the customer premise, the test set could be connected into a NID. As is indicated on Figure 28, when the Line Qualify task is selected, only a test known as the Bert test can be performed. The Bert test is typically selected when the user of the test set is sending or responding to the appropriate EOC loopcode. This test can also be selected if the user is performing end-to-end BER testing with someone else located at the far-end. The objective of this test is to test the physical layer of the U interface towards the LT or NT device. By sending or responding to EOC loopbacks, various channels can be tested using a BERT pattern. Physical layer results such as CRC errors, bit errors are also available when this test is selected. Figures 29(a) through 29(c) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Circuit Calls is selected by the user of the test set for an ISDN BRI physical interface. This task is usually selected when the technician is located at either the U interface at the customer premise with the test set emulating a NTI/TE device. In this situation, the connection is most likely an RJ-48 to RJ-48 at the U interface. Also, when located at the customer premise, the test set could be connected into a NID. As is indicated on Figures 29(a) through 29(c), when the Circuit Calls task is selected, three specific tests can be selected. These three tests are known as the Dual Call test, the Self Call test, and the Single Call test. The default settings for each of these tests, along with the set-up configuration and test results are also shown on Figures 29(a) through 29(c). The Dual Call test is typically selected when test set is used to place and receive voice and data calls to either a known telephone number or to an ISDN test line such as the TPI 560P. In this case, both Bl and B2 calls are placed or received simultaneously to verify true dual call functionality. The objective of the test is to verify service parameters by placing and receiving voice and data calls. A 2047 BERT analysis is typically performed on a data circuit. In addition, physical layer results such as BPVs, CRC errors and frame counts can be gathered. Layer 3D Channel Decodes can also be viewed. The Self Call test is typically selected when the test set is used to place and receive voice and data calls. The technician will place an outgoing data call on one B channel and receive this call on the second B channel. The objective of the test is to verify service parameters by placing and receiving voice and data calls. A 2047 BERT analysis is typically performed on a data circuit. In addition, physical layer results such as BPVs, CRC errors and frame counts can be gathered. Layer 3 D Channel Decodes can also be viewed. The Single Call test is typically implemented to place and receive voice and data calls to either a known telephone number or to an ISDN test line such as the TPI 560P. When this test is selected, it is assumed that only one call is placed at a time on each B channel. The objective of the test is to verify service parameters by placing and receiving voice and data calls. A 2047 BERT analysis is typically performed on a data circuit. In addition, physical layer results such as BPVs, CRC errors and frame counts can be gathered when the test is selected. Layer 3D Channel Decodes can also be viewed. Figures 30(a) through 30(b) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Packet Calls is selected by the user of the test set for an ISDN BRI physical interface. This task is usually selected when the technician is located at the U interface at the customer premise. When this test is being performed, the test set is emulating a NTI/TE device. Also, in this situation, the connection is most likely an RJ-48 to RJ-48 at the U interface. When located at the customer premise, the test set could be connected into a NID while the test is being performed. As is indicated on Figures 30(a) through 30(b), when the Packet Calls task is selected, two specific tests can be selected. These two tests are known as the 0B+D Call test, and the 2B+D Call test. The default settings for each of these tests, along with the set-up configuration and test results are also shown on Figures 30(a) through 30(b). The OB+D Call test is typically selected when the test set is used to place and receive data packets calls to either a known TE packet device or to an ISDN test line such as the TPI 560P. The objective of the test is to verify service parameters by placing a receiving data packet call over the D channel and then performing analysis on the received FOX message. In addition, physical layer results such as BPVs, CRC errors and frame counts can be gathered. Layer 3 D Channel Decodes can also be viewed when this test is performed. The 2B+D Call test is typically selected when the test set is being used to place and receive data packet and B channel voice and data calls to either a known telephone number or to an ISDN test line such as the TPI 560P. The objective of the test is to verify service parameters by placing a receiving data packet call over the D channel and then performing analysis on the received FOX message, along with voice and data calls. In addition, physical layer results such as BPVs, CRC errors and frame counts can be gathered. Layer 3 D Channel Decodes can also be viewed when this test is performed. TASK-BASED TESTS PERFORMED FOR DATACOM PHYSICAL INTERFACE Numerous task-based tests can be performed by a test set developed in accordance with present invention for a Datacom physical interface. Each of these tests are described in detail with reference to Figure 31 through Figure 33. Figure 31 represents an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Bert Turn-Up is selected by the user of the test set for a Datacom physical interface. This task is usually selected when the user is at the customer premise and is using the test set to emulate a CPE (e.g., a computer or CSU). The task can also be selected when the test set is used for emulating the DTE or DCE. In this scenario, the connection is most likely a 37 pin V.35 to V.35 cable, however, 15 pin and 25 pin connectors can also be supported. As is indicated on Figure 31, when the Bert Tum-Up task is selected, only a test known as the Straightaway test can be performed. The Straightaway test is typically selected when one test set is being used at the customer premise while another test set is located at a remote location, typically the CO at a DSX panel or the far-end customer premise. Testing and analysis is performed in both directions. The objective of this test is to perform data qualification tests. While in this mode, signaling states, clock frequency and bit errors can be seen while the test is being run. In addition, the user can control handshaking states between the DTE and DCE to ensure proper transitions. Figures 32(a) through 32(c) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Frame Relay Turn-Up is selected by the user of the test set for an Datacom physical interface. This task is usually selected when the technician is at the customer premise and is using the test set to emulate a router. The task can also be selected when the test set is used for emulating the DTE or DCE. In this scenario, the connection is most likely a 37 pin V.35 to V.35 cable, however, 15 pin and 25 pin connectors are also supported. As is indicated on Figures 32(a) througH 32(c), when the Frame Relay Turn-Up task is selected, three specific tests can be selected. These three tests are known as the Cir Check test, the LMI/PVC Check test, and the Ping Far End test. The default settings for each of these tests, along with the set-up configuration and test results are also shown on Figures 32(a) through 32(c). The Cir Check is typically selected when it is assumed that the physical layer and a LMI/PVC check have already been tested. The test set is plugged into the circuit after the actual frame relay service has been turned on by the NOC. The test set is used to send/receive frames from another test set located within the CO or from the NOC responsible for Packet Switched Services. When this test is selected, testing can also be performed to a soft loopback within the POP frame relay switch or to a hard loopback within the CO or at the far-end. The objective of the test is to verify that the customer is provided actual frame relay service at their CIR without losing frames due to congestion, improper Discard Eligibility (DE) flags or incorrect PVCs. The LMI/PVC Check test is typically selected when is assumed that the physical layer has already been tested. The test set is plugged into the circuit after the actual frame relay service that has been tumed on by the NOC. Since this test entails just connecting to the circuit and gathering results it is therefore a one-man test. This is the preferred first step to testing a frame relay circuit. The objective of the test is to test and verify that the Link Management Interface (LMI) is functioning properly and that all expected DLCI's have Permanent Virtual Circuits 20 (PVCs) that are properly configured and active. The Ping Far End test is typically implemented when it is assumed that the physical layer and a LMI/PVC check have already been tested. The test set is plugged into the circuit after the actual frame relay service that has been turned on by the NOC. Since this test entails just connecting to the circuit sending/receiving a ping to a currently installed IP device such as a far end router it is therefore a one-man test. The objective of the test is to test connectivity to a far-end router without taking it out-of-service. In this mode, the user can send IP Pings to an installed IP address (typically another router) in the network. The goal is to ensure that all IP ping messages that are sent to the far-end device are responded back with an echo reply. Figure 33 represents an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Monitor is selected by the user of the test set for an Datacom physical interface. This task is usually selected when the technician is at the customer premise with the test set connected between the router and the CSU. As is indicated on Figure 33, when the Monitor task is selected, two specific tests can be selected. These two tests are known as the Bert test and the Frame Relay test. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figure 33. The Bert test is typically selected the customer is sending live data into the CPE, while the test set is passively monitoring the circuit through a high impedance cable. With this test, the user is able to view results coming from the CSU and the CPE. The objective of the test is to passively monitor physical layer results and then to isolate the problem to either the DCE or DTE. In addition, with this test, the user can control handshaking states between DTE and I)CE to ensure proper transitions. The Frame Relay test is typically selected when the customer is sending live data into the router, while the test set is passively monitoring the circuit through the high impedance cable. When this test is selected, the user is also able to view results coming from the CSU and the router. The objective of the test is to isolate and sectionalize the problem to either the DTE or DCE using actual customer data. This test would normally be used for chronic troubles. Association between physical layer errors and layer two protocol errors can be seen by using this test. This test also allows for FCS errors, frame counts and DLCl status to be viewed for either the entire link or a particular DLCl along with physical layer results. TASK-BASED TESTS PERFORMED FOR ANALOG PHYSICAL INTERFACE Numerous task-based tests can be performed by a test set developed in accordance with present invention for an Analog physical interface. Each of these tests are described in detail with reference to Figure 34 through Figure 36. Figures 34(a) through 34(b) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present oil invention when a task known as WB Data Tum-Up is selected by the user of the test set for an Analog physical interface. This task is usually selected when the technician is located at the customer premise at the punch down block or at a crossbox. In this situation, the connection is most likely bantam-to-alligator clips. This task requires the use of two cables since it is a 2 pair (i.e., 4 wire) circuit. As is indicated on Figures 34(a) through 34(b), when the WB Data Turn-Up task is selected, four tests can be performed. This four tests are known as the Tone/Loss test, the Impulse Noise test, the Freq sweep test, and the Idle Noise test. The default settings for each of these tests, along with the set-up configuration and test result are also shown on Figures 34(a) through 34(b). The Tone/Loss test is performed end-to-end with a centralized test center. Typically, the test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIM's unit located at the MDF within the Central Office. Normally, a 28Khz, a 40Khz, and 196KHz tone is used for DDS, ISDN, and HDSL testing, respectively. The objective of this test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The Impulse Noise test is normally performed end-to-end with another TIM's unit located at the MDF within the Central Office. Usually, a quiet termination is provided while the impulse hits are performed with the 50 kbit (DDS), E filter (DDS & ISDN), and F Filter (HDSL). The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service.. The Freq sweep test is typically performed end-to-end with a centralized test center. Under these circumstances, the test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). It is important to note that this test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. Normally, tones are sent a range between 100 Hz and 5 kHz. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting a digital wideband service. The Idle Noise test is usually performed end-to-end with a centralized test center. The test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. A quiet termination is provided by both units. Normally, this test is performed with the 50 kbit (DDS), E-filter (DDS & ISDN), or F-filter (HDSL). The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting a digital wideband service. Figures 35(a) through 35(c) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as Voice Tum-Up is selected by the user of the test set for an Analog physical interface. This task is usually selected when the technician is located at the customer premise at the punch down block or at a crossbox. In this situation, the connection is most likely bantam-to-lineman clips. As is indicated on Figures 35(a) through 35(c), when the Voice Turn-Up task is selected, nine tests can be performed. This nine tests are known as the Tone/Loss test, the 3 Tone Slope test, the Notch/SNR test, the Impulse Noise test, the Idle Noise test, the 108 Test Line test, the DID Calls test, the Freq Sweep test, and the LS/GS Calls test. The default settings for each of these tests, along with the set-up configuration and test results are also shown on Figures 35(a) through 35(c). The Tone/Loss test is typically selected when a test is performed end-to-end with a centralized test center. Under these circumstances, the test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central office. Normally, a 1004Hz tone is used with this test. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The 3 Tone Slope test is typically selected when the test is performed end-to-end with a centralized test center. Under these circumstances, the test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. A 404, 1004, and 2804Hz tone is sent and received to make this measurement. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The Notch/SNR test is typically selected when the test is performed end-to-end with a centralized test center. Under these circumstances, the test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. A holding tone is sent and received to make the measurement using a C-Notch filter. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The Impulse Noise test is typically selected when the test is performed end-to-end with a centralized test center. Under these circumstances, the test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. A holding tone is sent and received to make the measurement using a C-Notch filter. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The Idle Noise test is typically selected when the test is performed end-to-end with a centralized test center. This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. A quiet termination is provided by both units when this test is conducted. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The 108 Test Line is typically selected when the test is performed by dialing a 108 or a milliwatt test line within the CO switch. Once the call is received, the CO switch automatically sends out a tone at a predefined level to be measured by the test set. This test eliminates the need to test in conjunction with a test center. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. Also, by placing a call into the test line, this test also verifies that there are no problems associated with improper timing, improper number of digits, wrong digit type, and/or overall switch translations. The DID calls test is typically selected when a test is being performed after the copper wire pair has been verified for its ability to support a voice service. Typically, under these testing circumstances the test set will receive the DID call which was initiated by a centralized tester. The objective of the test is to verify the circuit's ability to receive a voice call from the CO switch. This will verify that there are no problems associated with improper wink timing, improper number of digits, wrong digit type, and overall switch translations. The Freq Sweep Test is usually selected when the test is performed end-to-end with a centralized test center. Typically, the test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). It should be noted that this test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. Normally, tones are sent in the voice frequency range between 100Hz and 4000Hz. The objective of the test is to place and receive calls in order to verify that there are no problems associated with improper timing, improper number of digits, wrong digit type, and/or overall switch translations. The LS/GS Calls test is typically selected after the copper wire pair has been verified for its ability to support a voice service. This test is performed by using the voice pair to place and receive a call. Normally, a call is placed to any known telephone number to perform this test. The objective of the test is to verify the circuit's ability to place or receive a voice call through a CO switch. This test will verify that there are no problems associated with improper timing, improper number of digits, wrong digit type, and/or overall switch translations. Figures 36(a) through 36(c) represent an information matrix that summarizes the defaults, configurations and results of a test set developed in accordance with the present invention when a task known as VF Data Tum-Up is selected by the user of the test set for an Analog physical interface. This task is usually selected when the technician is located at the customer premise at the punch down block or at a crossbox. In this situation, the connection is most likely bantam-to-alligator clips. This test requires two cables since it is a 2 pair (i.e., 4 wire) circuit. As is indicated on Figures 36(a) through 36(c), when the VF Data Tum-Up task is selected, five tests can be performed. These five tests are known as the Tone/Loss test, the Impulse Noise test, the Freq Sweep test, the 3 Tone Slope test, and the Notch/SNR test. The default settings for each of these tests, along with the set-up configuration and test results are also shown on Figures 36(a) through 36(c). The Tone/Loss test is typically performed end-to-end with a centralized test center. The test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. Normally, a 1004Hz tone is used when this test is being conducted. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The Impulse Noise test is typically performed end-to-end with a centralized test center. The test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. A holding tone is simultaneously sent and 20 received to make the measurement using a D-Notch, a 3K flat or, a 3.4K flat filter. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The Freq Sweep test is typically performed end-to-end with a centralized test center. The test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. During this test, tones are normally sent in the voiceband between 100Hz and 4000Hz. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The 3 tone Slope test is typically performed end-to-end with a centralized test center. The test center is in control of the test (i.e., the tester indicates to the field technician which tones to send/receive). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. A 404, 1004, and 2804Hz tone is simultaneously sent and received to make this measurement. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The Notch/SNR test is typically performed end-to-end with a centralized test center. The test center is in control of the test (i.e., the tester indicates to the field technician which tones to send). This test can also be performed end-to-end with another TIMS unit located at the MDF within the Central Office. A holding tone is simultaneously sent and received to make the measurement using a D-Notch, a 3K flat or, a 3.4K flat filter. The objective of the test is to ensure that the copper wire pair is not experiencing excessive loss or noise and is capable of supporting the voice service. The present invention is not to be considered limited in scope by the preferred embodiments described in the specification. For example, the term task as used herein can encompass and defined job or function to be performed by the user of the test set. As such, numerous tasks, other than those described herein, can be defined based on the need of each individual user of the test set. Also, additional tests, other than those described herein, can be defined. Similarly, the default configurations for the tasks and tests defined herein can be changed. These modifications as well as any additional modifications or advantages, which will readily occur to those skilled in the art from consideration of the specification and It practice of the invention, are intended to be within the scope and spirit of the following claims

Claims: We claim: 1. A programmable graphical user interface (GUI) for use in a communication test set which conducts line tests on one or more different physical interfaces contained within a communication network, said GUI comprising: a first selection means for allowing a user of the test set to select a type of physical interface to be tested; a second selection means for allowing a user of the test set to select a task to be performed by the test set based on the physical interface selected; and a third selection means for allowing a user of the test set to select a test to be performed by the test set based on the task selected 2. The programmable GUI of claim 1, wherein said type of physical interface is selected from a group of physical interfaces consisting of a TI physical interface, a DDS-LL physical interface, an ISDN BRI physical interface, a Datacom physical interface, and an Analog physical interface. 3. The programmable GUI of claim of claim 2, wherein (i) when said type of physical interface is selected a TI physical interface, said type of task is selected from a group of tasks consisting of TI Bert Tum-Up, Tl/FTl FR Tum-Up, DDS Bert Tum-Up, DDS FR Tum-Up, FTl Bert Tum-Up, PBX Swith Tum-Up, ISDN PRI Tum-Up Monitor; (ii) when said type of physical interface is selected as a DDS-LL physical interface, said type of task is selected from a group of tasks consisting of DDS-LL physical interface, said type of task is selected from a group of tasks consisting of DDS Bert Tum-Up, Frm Relay Tum-Up and Monitor; (iii) when said type of physical interface is selected as an ISDN BRI phyical interface, said type of task is selected from a group of tasks consisting of Line Qualify, Circuit Calls and Packet Calls. (iv) when said type of physical interface is selected as a Datacom physical interface, said type of task is selected from a group of tasks consisting of Bert Tum-Up, Frame Relay Tum-Up and Monitor; and (v) when said type of physical interface is selected as an Analog physical interface said type of task is selected from a group of tasks consisting of WB Data Tum-Up, Voice Tum-Up and VF Data Tum-Up. 4. The programmable GUI of claim 3, wherein (i) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a TI Bert Tum-Up task, said type of test is selected from a group of tests consisting of Receive Loopback - Term, Send Loopback - Term, and Straightaway Bert - Term; (ii) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a Tl/FTl FR Tum-Up, said type of test is selected from a group of tests consisting of LMI/PVC Check, Cir Check, and Ping Far End; (iii) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a DDS Bert Tum-Up task, said type of test is selected from a group of tests consisting of Straightaway - D&I, and Send Loopback - D&I; (iv) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a DDS FR Tum-Up task, said type of test is selected from a group of tests consisting of LMI/PVC Check, Cir Check and Ping Far End; (v) when said type of physical interface is selected as a TI I physical interface and said type of task is selected as a FTl Bert Tum-Up task, said type of test is selected from a group of tests consisting of Straightaway - D&I, Send Loopback - Term, RCV Loopback - Term, and Straightaway - Term; (vi) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a PBX Switch Tum-Up task, said type of test is selected from a group of tests consisting of Voice Call - Term, Voice Call - D&I, and TIMs - Lvl/Noise D&I; (vi) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a ISDN PRI Tum-Up task, said type of test is selected from a group of tests consisting of NFAS/DCBU (46B+2D), Multiple (47B+D) and Single (23B+D); and, (viii) when said type of physical interface is selected as a TI I physical interface and said type of task is selected as a Monitor task, said type of test is selected from a group of tests consisting of Frame Relay, Bert, Timing Slips, ISDN PRI and Voice. 5. The programmable GUI of claim 3, wherein (i) when said type of physical interface is selected as a DDS-LL physical interface and said type of task is selected as a DDS Bert Tum-Up task, said type of test is selected from a group of tests consisting of Receive Loopback and Straightaway; (ii) when said type of physical interface is selected as a DDS-LL physical interface and said type of task is selected as a DDS Bert Trouble task, said type of test is selected from a group of tests consisting of Send CSU Loopback; and, (iii) when said type of physical interface is selected as a DDS-LL physical interface and said type of task is selected as a DDS Frm Relay Tum-Up task, said type of test is selected from a group of tests consisting of LMI/PVC Check, Ping Far End and Cir Check; (iv) said type of physical interface is selected as a DDS-LL physical interface and said type of task is selected as a Monitor task, said type of test is selected from a group of tests consisting of Frame Relay and Monitor. 6. The programmable GUI of claim 3, wherein (i) when said type of physical interface is selected as an ISDN BRI physical interface and said type of task is selected as a Line Qualify task, said type of test is selected from a group of tests consisting of Bert; (ii) when said type of physical interface is selected as an ISDN BRI physical interface and said type of task is selected as a Circuit Calls task, said type of test is selected from a group of tests consisting of Dual Call, Self Call and Single Call; and, (iii) when said type of physical interface is selected as an ISDN BRI physical interface and said type of task is selected as a Packet Calls task, said type of test is selected from a group of tests consisting of OB+D Call and 2B+D Call. 7. The programmable GUI of claim 3, wherein (i) when said type of physical interface is selected as a Datacom physical interface and said type of task is selected as a Bert Tum-Up task, said type of test is selected from a group of tests consisting of Straightaway; (ii) when said type of physical interface is selected as a Datacom physical interface and said type of task is selected as a Frame Relay Tum-Up task, said type of test is selected from a group of tests consisting of Cir Check, LMI/PVC Check and Ping Far End; and, (iii) when said type of physical interface is selected as a Datacom physical interface and said type of task is selected as a Monitor task, said type of test is selected from a group of tests consisting of Bert and Frame Relay. 8. The programmable GUI of claim 3, wherein (i) when said type of physical interface is selected as an Analog physical interface and said type of task is selected as a WB Data Tum-Up task, said type of test is selected from a group of tests consisting of Tone/Loss, Impulse Noise, Freq. Sweep, and Idle Noise; (ii) when said type of physical interface is selected as an Analog physical interface and said type of task is selected as a Voice Tum-Up task, said type of test is selected from a group of tests consisting of Tone/Loss, 3 Tone Slope, Notch/SNR, Impulse Noise, Idle Noise, 108 Test Line, DID Calls, Freq. Sweep, and LS/GS Calls; and (iii) when said type of physical interface is selected as an Analog physical interface and said type of task is selected as a VF Data Tum-Up task, said type of test, is selected from a group of tests consisting of Tone/Loss, Impulse Noise, Freq. Sweep, 3 Tone Slope, and Notch/SNR. 9. The programmable GUI of claim 1, wherein a predetermined number of features on the test set are automatically configured based on the physical interface, task and test selected. 10. The programmable GUI of claim 1 , wherein the results to be displayed on the test set are automatically configured based on the physical interface, task and test selected. 11. A method of configuring a test set for testing a communications network, said method comprising the steps of (a) " presenting a selection of physical interfaces to be selected; (b) presenting a selection of tasks to be performed by the test set based on the physical interface selected; (c) presenting a selection of tests to be performed by the test set based on the task selected; and, (d) automatically configuring predetermined features of the test set based on the physical interface, task and test selected. 12. The method of claim 11, wherein said type of physical interface is selected from a group of physical interfaces consisting of a TI physical interface, a DDS-LL physical interface, an ISDN BRI physical interface, a Datacom physical interface, and an Analog physical interface. 13. The method of claim 12, wherein: (i) when said type of physical interface is selected as a TI physical interface, said type of task is selected from a group of tasks consisting of TI Bert Tum-Up, Tl/FTl FR Tum-Up, DDS Bert Turn-Up, DDS FR Tum-Up, FTl Bert TumUp, PBX Swith Tum-Up, ISDN PRI Tum-Up and Monitor; (ii) when said type of physical interface is selected as a DDS-LL physical interface, said type of task is selected from a group of tasks consisting of DDS Bert Tum-Up, Frm Relay Tum-Up and Monitor; (iii) when said type of physical interface is selected as an ISDN BRI physical interface, said type of task is selected from a group of tasks consisting of Line Qualify, Circuit Calls and Packet Calls; (iv) when said type of physical interface is selected as a Datacom physical interface, said type of task is selected from a group of tasks consisting of Bert Tum-Up, Frame Relay Tum-Up and Monitor; and (v) when said type of physical interface is selected as an Analog physical interface, said type of task is selected from a group of tasks consisting of WB Data Tum-Up, Voice Tum-Up and VF Data Tum-Up. 14. The method of claim 13, wherein (i) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a TI I Bert Tum-Up task, said type of test is selected from a group of tests consisting of Receive Loopback - Term, Send Loopback - Term, and Straightaway Bert - Term; (ii) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a Tl/FTl FR Tum-Up, said type of test is selected from a group of tests consisting of LMI/PVC Check, Cir Check, and Ping Far End; (iii) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a DDS Bert Tum-Up task, said type of test is selected from a group of tests consisting of Straightaway - D&I, and Send Loopback - D&I; (iv) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a DDS FR Tum-Up task, said type of test is selected from a group of tests consisting of LMI/PVC Check, Cir Check and Ping Far End; (v) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a FTl Bert Tum-Up task, said type of test is selected from a group of tests consisting of Straightaway - D&I, Send Loopback - Term, RCV Loopback - Term, -and Straightaway - Term; (vi) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a PBX Switch Tum-Up task, said type of test is selected from a group of tests consisting of Voice Call - Term, Voice Call - D&I, and TIMs - Lvl/Moise D&I; (vii) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a ISDN PRI Tum-Up task, said type of test is selected from a group of tests consisting of NFAS/DCBU (46B+2D), Multiple (47B+D) and Single (23B+D); and, (viii) when said type of physical interface is selected as a TI physical interface and said type of task is selected as a Monitor task, said type of test is selected from a group of tests consisting of Frame Relay, Bert, Timing Slips, ISDN PRI and Voice. 15. The method of claim 13, wherein (i) when said type of physical interface is selected as a DDS-LL physical interface and said type of task is selected as a DDS Bert Tum-Up task, said type of test is selected from a group of tests consisting of Receive Loopback and Straightaway; (ii) when said type of physical interface is selected as a DDS-LL physical interface and said type of task is selected as a DDS Bert Trouble task, said type of test is selected from a group of tests consisting of Send CSU Loopback; (iii) when said type of physical interface is selected as a DDS-LL physical interface and said type of task is selected as a DDS Frm Relay Tum-Up task, said type of test is selected from a group of tests consisting of LMI/PVC Check, Ping Far End and Cir Check; and (iv) when said type of physical interface is selected as a DDS-LL physical interface and said type of task is selected as a Monitor task, said type of test is selected from a group of tests consisting of Frame Relay and Monitor. 16. The method of claim 13, wherein (i) when said type of physical interface is selected as an ISDN BRI physical interface and said type of task is selected as a Line Qualify task, said type of test is selected from a group of tests consisting of Bert; (ii) when said type of physical interface is selected as an ISDN BRI physical interface and said type of task is selected as a Circuit Calls task, said type of test is selected from a group of tests consisting of Dual Call, Self Call and Single Call; and, (iii) when said type of physical interface is selected as an ISDN BRI physical interface and said type of task is selected as a Packet Calls task, said type of test is selected from a group of tests consisting of OB+D Call and 2B+D Call. 17. The method of claim 13, wherein (i) when said type of physical interface is selected as a Datacom physical interface and said type of task is selected as a Bert Tum-Up task, said type of test is selected from a group of tests consisting of Straightaway; (ii) when said type of physical interface is selected as a Datacom physical interface and said type of task is selected as a Frame Relay Tum-Up task, said type of test is selected from a group of tests consisting of Cir Check, LMI/PVC Check and Ping Far End; and, (iii) when said type of physical interface is selected as a Datacom physical interface and said type of task is selected as a Monitor task, said type of test is selected from a group of tests consisting of Bert and Frame Relay. 18. The method of claim 13, wherein (i) when said type of physical interface is selected as an Analog physical interface and said type of task is selected as a WB Data Tum-Up task, said type of test is selected from a group of tests consisting of Tone/Loss, Impulse Noise, Freq. Sweep, and Idle Noise; (ii) when said type of physical interface is selected as an Analog physical interface and said type of task is selected as a Voice Tum-Up task, said type of test is selected from a group of tests consisting of Tone/Loss, 3 Tone Slope, Notch/SNR, Impulse Noise, Idle Noise, 108 Test Line, DID Calls, Freq. Sweep, and LS/GS Calls; and (iii) when said type of physical interface is selected as an Analog physical interface and said type of task is selected as a VF Data Tum-Up task, said type of test is selected from a group of tests consisting of Tone/Loss, Impulse Noise, Freq. Sweep, 3 Tone Slope, and Notch/SNR. 19. A programmable graphical user interface (GUI) for use in a communication test set which conducts line tests on one or more different physical interfaces contained within a communication network, said GUI comprising: a task selection means for allowing a user of the test set to select a task to be performed by the test set; and a test selection means for allowing a user of the test set to select a test to be performed by the test set based on the task selected. 20. The programmable GUI of claim 19, wherein a predetermined number of features on the test set are automatically configured based on the task and test selected. 21. The programmable GUI of claim 19, wherein the results of the tests to be displayed on the test set are automatically configured based on the task and test selected.

Inventors: CHISLEY CHARLES, COHEN JORDAN, JAMES DANIEL, YARBOROUGH SEAN, CHISLEY, CHARLES, COHEN, JORDAN, JAMES, DANIEL, YARBOROUGH, SEAN
Applicants: ACTERNA LLC, ACTERNA, LLC
Application year: 2000
Main classification: H04B17
IPC codes: H04B17, H04L1, H04L12