1. Field of the Invention
This invention relates to satellite broadcast television and more specifically to test procedures for performing failure diagnostics on a customer IRD.
2. Description of the Related Art
Satellite television programming has become widely available and has become a popular alternative to analog broadcast and cable services. Service providers such as DIRECTV® and EchoStar Communications Corp. (Dish Network™) provide a wide variety of programming.
As shown in
Each customer site 16 includes an integrated receiver decoder (IRD) 22 for decrypting and decoding customer selected programming content; an antenna, a multiswitch for selection of the appropriate satellite signal, a coax cable from the antenna to the IRD, connectors, inline amplifiers and low noise block downconverter (LNBs) (collectively the outdoor unit “ODU” 24) for downloading and routing the broadcast stream to the IRD; a video display, e.g. TV, 26; and a recording device 28 such as a VCR. A digital video recorder (DVR) integrates the features of the IRD and recording device as well as many other features and services such as Tivo®. Each IRD includes universal components such as an RF tuner/demodulator for receiving a signal from the antenna, a phone modem for performing the “callback” function and a decoder for decrypting/decoding the programming content. Each IRD is paired with a removable access card 30 that is customer specific and includes security information such as decryption keys and account information such as account numbers, an access card ID number, subscribed services, rating limits and billing limits. The access card determines if the customer is authorized to watch a program, and if they are, sends an authorization to decode the audio and video packets in the broadcast stream and direct them to television 26 for viewing and/or recording device 28.
It is not uncommon that problems will occur at the customer site, which interferes with the customer's ability to select, download, decrypt or report back activity to the service provider. The source of failure can be improper installation, user error or hardware failures in the ODU, IRD or access card. The customer will typically call a CSR for assistance. At a minimum, the CSR should be able to identify the problem and take the proper remedial action such as mailing the customer a new access card, an IRD, or dispatching a technician to replace one of the ODU components. More often than not, the problem is not attributable to a hardware failure and easily fixed if it can be identified.
Unfortunately the current self-test functions of IRD, hence the information available to the CSR is very limited, at best performing a gross functional test. In most cases, the signal and tuning test only check for signal on the currently tuned transponder, the modem test verifies a dial tone, and a basic access card read test verifies communication with the access card and validates its ID number. A simple LNB polarity test is usually performed by having the customer tune to channels 100 (ODD), 999 (EVEN) and 400 (119 switching), but this only confirms a problem exists; it does not isolate the problem. Even these basic tests require the CSR to walk the customer through the on-screen menu to verify the signal levels and validate communication with the access card, which is time consuming and frustrating for the customer.
Accurately troubleshooting these problems, especially remotely, is very difficult, and not always very precise. CSRs typically work from a script and are not experienced. Different CSRs may diagnose the same failure differently, prompting the customer to make repeated calls looking for resolution to their problem. Ultimately it is the CSR's judgment call as to the problem; do they replace the IRD, the access card or dispatch a technician? Typically they will replace either the access card or the IRD, a vast majority of which have no failures when returned for repair.
The limited self-test capabilities of the IRD and the ad hoc diagnostic procedures performed by the CSRs cost the service provider time and money and reduce customer satisfaction; in some cases leading to the customer's dropping the service.
The present invention provides an IRD with expanded self-test capabilities, both hardware and software, that will provide standardized and more precise diagnostics with limited customer interaction and more reliable and accountable service. This in turn will save the service provider time and money and will limit downtime thereby enhancing customer satisfaction.
This is accomplished by defining a set of tests for the IRD and ODU, upgrading the IRD hardware and storing the software for executing the tests in the IRD. When a service problem occurs, an IRD test is initiated by either calling a CSR or automated test center, which in turn send a packet over the broadcast network to the customer's IRD, or by relying on the customer to navigate an on-screen menu.
The IRD runs a sequence of tests that determine the fitness of the IRD including the access card and modem and the health of the ODU. Instructions are displayed on-screen if customer interaction is required, e.g. “remove/replace the coax between the IRD and ODU.” As the tests are completed, the results are displayed on-screen and written to a file. If a test fails, the appropriate remedial action such as “reset to factory default settings”, “service call”, “replace IRD, access card, modem, ODU” or “do nothing” is also written to the file.
When the test sequence is complete, the IRD creates a header message identifying the customer, the date, the problem and the remedial action, appends the file and forwards it to the satellite service provider over a back channel (fax, email, data packet). The satellite service provider archives the file, modifies the header message to provide customer contact information and the responsible dealer, and forwards the file to the service dealer. The service dealer performs the specified remedial action by either making a service call or mailing the replacement hardware.
To improve service and accountability, the network may be configured so that when the dealer receives and accepts the service request from the satellite service provider, an acknowledgement is sent from the dealer back to the service provider confirming that the remedial action will be taken. The service provider in turn sends an acknowledgement over the broadcast network to the customer specifying the service dealer, the remedial action and schedule. This provides the service provider with a “paper trail” that the dealer has in fact received and accepted the service request and provides the customer with assurances that the problem will be fixed in a timely manner and a phone number to call if service is not forthcoming. The acknowledgement and actual service performed may be appended to the file and archived at the service provider.
These and other features and advantages of the invention will be apparent to those skilled in the art from the following detailed description of preferred embodiments, taken together with the accompanying drawings, in which:
a and 2b are a flowchart of the IRD self-test diagnostics in accordance with the present invention;
a-4e are flowcharts illustrating the execution of the test packet;
a-7b and 8a-8b are examples of messages sent to the satellite service provider and the dealer; and
The present invention provides an IRD with expanded self-test capabilities, both hardware and software, that will provide standardized and more precise diagnostics with limited customer interaction and more reliable and accountable service. This in turn will save the service provider time and money and will limit downtime thereby enhancing customer satisfaction.
As illustrated in
As shown in
Once initiated, the IRD runs a sequence of tests that determine the fitness of the IRD including the access card and modem and the health of the ODU (step 66). Instructions or messages are displayed on-screen if customer interaction is required, e.g. “remove/replace the coax between the IRD and ODU” (step 68). As the tests are completed, the results are displayed on-screen and written to a file (step 70). If a test fails, the appropriate remedial action such as “reset to factory default settings”, “service call”, “replace IRD, access card, modem, ODU” or “do nothing” is also written to the file. The IRD executes each successive test until finished (step 72). If no test fails (step 74), a “test passed” message may be displayed to the customer and the test ends (step 76).
If one or more tests fail, the IRD creates a header message identifying the customer, the date, the problem and the remedial action, appends the file and forwards it to the satellite service provider over a back channel (fax, email, data packet) (step 78). The system may be configured to send this message even if all tests pass. The customer may at this point call the CSR to discuss the test results and what will happen next (step 80). The satellite service provider archives the file, modifies the header message to provide customer contact information and the responsible dealer, and forwards the file to the service dealer (step 82). The service dealer accepts the service request (step 84) and performs the specified remedial action by either making a service call (step 86) or mailing the replacement hardware (step 88).
To improve service and accountability, the network may be configured so that when the dealer receives and accepts the service request from the satellite service provider, an acknowledgement is sent from the dealer back to the service provider confirming that the remedial action will be taken (step 90). The service provider in turn sends an acknowledgement over the broadcast network, telco, internet or some other communication channel to the customer specifying the service dealer, the remedial action and schedule (step 92). This provides the service provider with a “paper trail” that the dealer has in fact received and accepted the service request and provides the customer with assurances that the problem will be fixed in a timely manner and a phone number to call if service is not forthcoming. The acknowledgement and actual service performed may be appended to the file and archived at the service provider.
A particular sequence of IRD and ODU tests 94 is illustrated in
Upon initiation of the test sequence (step 110), the IRD measures the even polarity LNB voltage supplied by the IRD to the ODU to ensure compliance with specifications (step 112). If the voltage is too high, the LNB and/or multiswitch may burn up. If the voltage is too low, the LNB and/or multiswitch will not switch properly. If the LNB voltage is not within the specification (step 114), the customer is instructed to “Remove the Coax Cable from the Satellite Antenna In Connector” via OSD1116 and the test is rerun (step 118). Removal of the Coax Cable removes a possible short circuit and isolates the IRD from the ODU to better isolate the failed component. If the test fails again, the required remedial action is to replace the IRD (step 120). The customer is informed that “A Failure has been detected in the IRD” via OSD3122 and a TEXT2 service provider message 104 is generated indicating that the customer has a failed IRD. If the test passes twice with the coax disconnected, the required remedial action is a service call (step 124). The customer is informed that “An Error has been detected in the IRD” via OSD2126 and a TEXT1 service provider message 100 is generated indicating that the customer requires service. The test sequence may either continue to execute all of the tests to provide a complete test report or may terminate on detection of a failure.
Assuming either that the first test passes or that all tests in the sequence are run, the odd polarity LNB voltage is measured (step 128) and interrogated using the same sequence of steps and messages.
A similar sequence of steps are used to measure the even and odd polarity LNB currents (steps 130, 132) and then interrogate any problems. If the LNB current is not within the specification (step 134), it is either “over current” or “under current”. If over current, the customer is instructed to “Remove the Coax Cable from the Satellite Antenna In Connector” via OSD1116 and the test is rerun (step 136). If the test fails again, the required remedial action is to replace the IRD (step 138). The customer is informed that “A Failure has been detected in the IRD” via OSD3122 and a TEXT2 service provider message 104 is generated. If under current, the customer is instructed to “Verify Coax Connection” via OSD10140 and the test is rerun (step 142). If the test fails again, the required remedial action is a service call (step 144). The customer is informed that “An Error has been detected in the IRD” via OSD2126 and a TEXT1 service provider message 100 is generated. The results of the test including Pass/Fail and the performance are written to the test data report.
Thereafter, the IRD measures the 22 kHz tone frequency and amplitude coming out of the IRD (step 150). This test determines compliance with the specifications. If the frequency or amplitude are outside specifications then the IRD will not be able to switch to the other satellites. If the measurements are not within the specification (step 152), the customer is instructed to “Remove the Coax Cable from the Satellite Antenna In Connector” via OSD1116 and the test is rerun (step 154). Removal of the Coax Cable isolates the IRD from the ODU. If the ODU is short circuited, the IRD which had failed, might now pass. If the test fails again, the required remedial action is to replace the IRD (step 156). The customer is informed that “A Failure has been detected in the IRD” via OSD3122 and a TEXT2 service provider message 104 is generated.
The IRD then executes the telco test to check for dial tone (step 160). If the IRD does not detect a dial tone (step 162), the customer is instructed to “Take your telephone off the hook and listen for a tone. Press select to start” via OSD 6164 to initiate a sequence of DTMF tones (step 166). This outputs an audible tone that can be heard on the telephone while it is even off hook. If the customer and CSR are on the phone, the IRD would never be able to detect a dial tone, so what this does is test the modem by outputting the tone for all to hear, thus validating the modem and connection to the phone line. The customer is queried “Did you hear a tone during the test?” via OSD7168 (step 170). If the customer responds in the affirmative by clicking a menu button on the OSD, the message “Telephone test complete, please hang up your phone” is displayed via OSD4172 and the test ends. If the customer responds in the negative, the required remedial action is to schedule a service call (step 174). The customer is informed that “A Failure has been detected in the IRD” via OSD3122 and a TEXT2 service provider message 104 is generated indicating that the customer has a failed IRD.
The IRD attempts to test the access card, including reading the access card ID number (step 180). This validates that the card reader in the IRD is functional and the access card itself is functional and can perform a simple read write operation. If unsuccessful, the required remedial action is to replace the access card (step 182). The customer is informed that “A error has been detected with the access card” via OSD5184 and a TEXT2 service provider message 104 is generated indicating that the customer has a failed access card.
The IRD then attempts to read the IRD ID (step 190). If unsuccessful, the required remedial action is to replace the IRD (step 192). The customer is informed that “A failure has been detected in the IRD” via OSD3122 and a TEXT2 service provider message 104 is generated indicating that the customer has a failed IRD.
The IRD then tests the hard drive for both space remaining and the health of the drive (step 200). If the drive is nearly full, the customer is instructed to “Delete programming from the hard drive” via OSD 202. If the hard drive is unhealthy, the required remedial action is to replace the IRD (step 204). The customer is informed that “A failure has been detected in the IRD” via OSD3122 and a TEXT2 service provider message 104 is generated indicating that the customer has a failed IRD. The IRD then reads and records the IRD odometer reading (date and/or time the IRD was first activated) for warranty verification (step 206).
The IRD then retrieves the current IRD antenna configuration (step 210) (Single 212, Dual 214, Triple 216 or Other 218 Satellite) to perform the signal level test, both even and odd polarities on all applicable satellites to verify that either the LNB or multi-switch properly switches polarity. The IRD then measures and records the even and odd polarity signal levels for the satellites A, B, C, . . . (step 220). If any signal level is unacceptable (step 222), the required remedial action is a service call (step 224). The customer is informed that “An Error has been detected in the IRD” via OSD2126 and a TEXT1 service provider message 100 is generated indicating that a service call is needed.
Once the sequence of tests is completed, the IRD writes a summary to the test data report 98 (step 230). For example, 1 TEST FAIL, 16 TEST PASS, Schedule Service Call or Replace (IRD, Access Card, Modem). The customer is informed of the test results “Test complete with X Failures Detected” via OSD 8232 and of the remedial action that will be taken “Report forwarded to satellite service provider, Service call will be scheduled in 3-5 business days” or “Report forwarded to satellite service provider, the dealer will mail you a replacement (IRD, access card, modem) in 3-5 business days” via OSD 11234. At this point, steps 78-92 are executed to forward the header messages 100 and/or 104 and test data report 98 to the satellite service provider, which archives the reports and generates the TEXT1 or TEXT2 dealer messages 102 or 106. When the dealer receives and acknowledges the service request or hardware replacement, an acknowledge message is sent back to the satellite service provider and customer confirming the remedial action.
To perform the sequence of self-tests the standard IRD 108 must be upgraded as shown in
The hardware is modified to include a LNB monitor 240 between the satellite signal input 242 and the L band tuner and demodulator 244 to measure the LNB voltage and current and perform the 22 Khz tone test. The LNB monitor 240 measures the voltage and current provided by the tuner/demodulator at input 242 when terminated with a coax to the antenna. The LNB monitor also generates a 22 Khz tone for testing the 110/119 switching function of the multiswitch in the ODU. These types of simple measurement and test circuits are well known in the art.
The hardware may also be modified to include a modem monitor 246 between a telephone jack 248 and the modem 250. to internalize the telco tests. The modem monitor would not only test for the dial tone but would also test the phone line for acceptable operation parameters or conditions, e.g. voltage and current. The modem monitor could also supply DTMF tones that could be heard by the customer and CSR while on the phone to verify that the modem itself is operational.
The other test functions can be implemented with software changes and downloads to the access card. The operation of the standard IRD is well known in the art and will not be discussed herein.
While several illustrative embodiments of the invention have been shown and described, numerous variations and alternate embodiments will occur to those skilled in the art. Such variations and alternate embodiments are contemplated, and can be made without departing from the spirit and scope of the invention as defined in the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4057847 | Lowell et al. | Nov 1977 | A |
4677467 | Hayes | Jun 1987 | A |
4760597 | Hayes et al. | Jul 1988 | A |
4987486 | Johnson et al. | Jan 1991 | A |
5093921 | Bevin, Jr. | Mar 1992 | A |
5373288 | Blahut | Dec 1994 | A |
5666293 | Metz et al. | Sep 1997 | A |
5796953 | Zey | Aug 1998 | A |
5936667 | Saib et al. | Aug 1999 | A |
5954808 | Paul | Sep 1999 | A |
6049830 | Saib | Apr 2000 | A |
6081533 | Laubach et al. | Jun 2000 | A |
6160991 | Chappell et al. | Dec 2000 | A |
6285396 | Har Shoshanim et al. | Sep 2001 | B1 |
6445907 | Middeke et al. | Sep 2002 | B1 |
6598229 | Smyth et al. | Jul 2003 | B2 |
6611865 | Perugini et al. | Aug 2003 | B1 |
6662367 | Dapper et al. | Dec 2003 | B2 |
6681344 | Andrew | Jan 2004 | B1 |
6687486 | Grzeczkowski | Feb 2004 | B2 |
7020689 | Simyon et al. | Mar 2006 | B2 |
20020184568 | Kurrasch | Dec 2002 | A1 |
20030028891 | Hardt et al. | Feb 2003 | A1 |
20030237035 | Bowers et al. | Dec 2003 | A1 |
20040014479 | Milman | Jan 2004 | A1 |
20040158863 | McLain | Aug 2004 | A1 |
20040237116 | Allen | Nov 2004 | A1 |
20050183130 | Sadja et al. | Aug 2005 | A1 |
20090058397 | Fitzpatrick et al. | Mar 2009 | A1 |
Number | Date | Country |
---|---|---|
WO 9413107 | Jun 1994 | WO |
WO 0137568 | May 2001 | WO |
WO 0180528 | Oct 2001 | WO |
WO 0197039 | Dec 2001 | WO |
WO 02076100 | Sep 2002 | WO |
WO 02078345 | Oct 2002 | WO |
WO 03049445 | Jun 2003 | WO |