Broadcast communication systems, such as direct broadcast satellite (DBS) systems, satellite radio (SR) broadcast systems, and cable television systems, have become exceedingly popular among consumers by providing convenient and relatively inexpensive access to numerous sources of programming, such as newscasts, sporting events, entertainment programs, and the like. Recent advances in quality and functionality, such as high-definition video programming and digital recording capability, have further enhanced the desirability of accessing such systems.
Additionally, programming over such broadcast communication systems is typically delivered to the user in a digital format, thus enhancing both the quality and reliability of the received content. In fact, the reliability of programming delivery on such systems has attained such a level that any interruption or disruption in the reception of programming often instills surprise, if not outright consternation, in the typical user. Such a problem may adversely affect the quality of one or more programming channels, and in extreme cases, may cause complete loss of one or more programs.
Such a problem may be caused by equipment errors or failure at any of a number of locations within the broadcast communication system, including communication devices located at the programming provider, the broadcast distribution facility, or the customer location. Also, environmental conditions, such as heavy rain or snow, may negatively impact program reception. Thus, in the event of a program disruption or outage, the user or consumer typically cannot or does not know the source or cause of the problem, and thus does not know if any actions on their part are required to restore service. At most, in the case of a lost programming supplier feed or similar problem within a DBS system, the programming supplier or the system provider may display a “slate,” or static video image, acknowledging the problem, but otherwise providing little or no specific information. Thus, in the event of a problem with reception, the user typically attempts to contact a customer service representative at a call center of the system provider or operator to obtain more information regarding the problem. Unfortunately, if the problem affects a large number of the users subscribing to the same programming, the volume of calls typically prevents most of the users experiencing the same problem from obtaining the information they desire. Further, the large call volume at the call center may prevent other users with potentially more serious issues from successfully reaching the call center until the problem has been remedied.
Another embodiment, a broadcast communication system 200, is depicted in
While the following discussion focuses exclusively on embodiments of the invention within the context of satellite broadcast communications, equipment involved in the reception of other forms of communication, such as various types of wireline and wireless communication, may also benefit from application of the embodiments discussed below. For example, the broadcast communication system may instead be a satellite radio (SR) system, a cable broadcast system or a terrestrial broadcast communication system.
The satellite uplink center 302 typically receives programming from one or more external information sources 320, such as a programming content provider. Examples of content providers include television broadcasting networks, sports programming outlets, news providers, and other television programming suppliers. Audio-only content providers supplying music and other audio programming may be included.
The satellite uplink center 302 transfers the programming received from the information sources 320 over one or more satellite programming channels 306 to the satellite communication receiver 304 via the communication satellite 305. More specifically, the satellite 305 includes one or more transponders 309 for receiving the programming over satellite programming uplink channels 306u and retransmitting the programming over satellite programming downlink channels 306d to the satellite communication receiver 304 associated with a user 310. In one embodiment, the satellite 305 includes 16 to 32 transponders, each of which may operate at a different transmission frequency and be capable of carrying up to twelve different programs simultaneously by way of time-division multiplexing (TDM). Each of the programs is associated with one of the satellite programming channels 306 mentioned above and discussed hereinafter.
The receiver 304 receives programming over each of the programming channels 306, typically by way of an antenna or “dish” (not shown in
In one embodiment shown in
In operation, while programming is being transferred from the information source 320 to the satellite communication receiver 304 by way of the satellite uplink center 302 and the communication satellite 305, one or more of the programming channels 306 may encounter a problem from the perspective of the user 310. The problem may be a reduction in the audio or video quality of one of the programs being received at the receiver 304 over one of the channels 306, a partial or complete loss of data associated with one of the channels 306, or any other interruption or disruption of the program being transferred over the channel 306.
The source of a channel problem may be located in at least one of a number of locations within the broadcast communication system 300. For example, one of the information sources 320 or the connection between the source 320 and the uplink center 302 may experience a failure preventing the associated programming from reaching the uplink center 302. In another example, the uplink center 302 may be experiencing internal problems, such as with reception of the programming from the information source 320, or with transmission of the programming to the satellite 305. Similarly, one or more transponders 309 of the satellite 305 may experience difficulties in receiving the programming over the channels 306 from the uplink center 302, or transmitting the programming over the channels 306 to the receiver 304.
Other channel problems may not be related to the equipment employed in the broadcast communication system 300, but may instead be caused by adverse weather or other environmental conditions affecting the communication paths of the satellite programming channels 306. For example, heavy rain or snow conditions may negatively affect the path of the programming channels 306 between the uplink center 302 and the satellite 305, as well as the path between the satellite 305 and the receiver 304. Other atmospheric conditions, such as sun spot activity or backlighting of the satellite 305 by the sun, which may temporarily “blind” the receiver 304, may cause interruption or disruption of the programming channels 306 as well.
In the presence of a channel problem, the satellite uplink center 302 may detect the existence of the problem in a number of ways, depending on the source of the problem. In the case the problem resides in one of the information sources 320 or the connection between the source 320 and the uplink center 302, the uplink center 302 may independently deduce from the programming being received that the source of the problem lies prior to the uplink center 302. Alternatively, the affected information source 320 may transfer an explicit indication of the cause of the problem to the uplink center 302. If, instead, the source of the problem lies within the uplink center 302, the uplink center 302 may detect the problem and determine its cause by way of self-diagnostic hardware or firmware, or other means.
In another example, the problem may be caused within, but remain undetected by, the uplink center 302. Another source of failure may be the communication satellite 305, including one of its transponders 309. In either of these situations, the satellite uplink center 302 may detect the problem and its cause by way of a satellite communication link (not shown in
Once the uplink center 302 has detected the problem and ascertained its cause, the uplink center 302 relays an indication of the cause of the problem to the receiver 304, as well as other receivers accepting programming from the satellite 305. In one example, the indication of the cause is transmitted from the uplink center 302 over a data channel 308 to the receiver 304 through a transponder 309 of the satellite 305. In the embodiment of
Some failures of the broadcast communication system 300, such as an error within some or all of the transponders 309 of one or more satellites 305, may prevent the indication of the cause of the detected problem from reaching the receiver 304 by way of the data channels 308. To address this potential issue, the Internet connection 332 from the uplink center 302 to the receiver 304 may be employed to transfer the indication of the cause of the problem to the receiver 304 by way of a terrestrial link, thus bypassing any errors or defects involving the satellite 305 or its transponders 309. Accordingly, if the receiver 304 detects the loss of a data channel 308 for a particular transponder 309, the receiver 304 may attempt to acquire information from a data channel 308 of another transponder 309 of the same or another satellite 305. If these attempts fail, the receiver may then look to a terrestrial link, such as the Internet connection 332 mentioned above, for the information.
In another example, some failures of the uplink center 302 may prohibit the uplink center 302 from transmitting an indication of the cause of the problem. In that case, the second uplink center 303 of
While some problems affecting reception of one or more broadcast programming channels 306 are current events which may only be detected after they occur, others may be future events which are predictable. For example, the sun may be positioned such that a satellite 305 may be backlit from the viewpoint of a receiver 304, as mentioned above, resulting in the loss of one or more programming channels 306 for a period of time. Such a phenomenon is predictable on the basis of the motion of the earth relative to the sun. As a result, information regarding the predicted failure may be provided over the data channels 308 of one or more satellites 305 so that the receivers 304 that will be impacted by the phenomenon may be alerted prior to the event. In this case, the receivers 304 to be affected during a particular time period may be identified by way of zip code or other geographical indication. Under another scenario, information concerning scheduled maintenance on a particular device within the system 300 that may cause temporary loss of programming may be relayed to the receivers 304 in a like manner.
Other information in addition to an indication of the cause of the channel problem may be generated at the uplink center 302 and forwarded to the receiver 304. This information may include, for example, an estimated time of resolution for the problem, which may help align the expectations of the user 310 with those of the technical personnel charged with resolving the problem.
In one embodiment, the receiver 304 continually monitors the one or more data channels 308 received from the satellite 305, and possibly other satellites, for problem information involving the programming channels 306. Alternatively, the receiver 304 may check for the problem information associated with a particular channel 306 if the receiver 304 is tuned to that channel 306. As discussed above, the receiver 304 may also receive the indication of the cause of a detected problem over the Internet connection 332.
The indication of the cause may be in the form of a code, such as an alphanumeric code or escape sequence, indicating one of a list of predefined potential problems. In that embodiment, the receiver 304 may translate the code into text or some other form perceivable by the user 310 by way of the display 330. In another implementation, the uplink center 302 may directly specify the text or other form to be presented to the user 310. The text may then be displayed for the user 320 when the user tunes the receiver 304 to the impacted channel 306. The indication of the cause of the problem may also be in the form of an audio message transferred from the receiver 304 to be played on the display 330 to the user 310 when tuned to the affected channel 306.
For example, presuming one of the information sources 320, associated with Network XYZ, is not able to transfer a particular program to the uplink center 302, the uplink center 302 may receive information from the source 320 indicating the cause of the problem and an estimated time for resolution. The uplink center 302 may then react to this information by causing text to be presented by the receiver 304 at the display 330 when the receiver 304 is tuned to Network XYZ to inform the user 310 of the problem. Such text may indicate that “Network XYZ is temporarily out of service due to a hardware problem at a Network XYZ facility. XYZ expects service to be restored by 10 P.M., Eastern Standard Time.” The user 310, thus being informed of the cause of the problem, may not be inclined to call the call center of the operator or provider of the broadcast communication system 300, thus reducing the amount of call traffic at the call center.
The user 310 may also be updated as to any changes in the status of the problem. For example, in the scenario presented above, if the problem is not resolved by the quoted time, the expected time of resolution may be modified at the uplink center 302, transferred to the receiver 304 via the satellite 305, and displayed to the user 310 to apprise the user 310 of the change.
As described above, various embodiments of the present invention notify a user of a broadcast communication system of channel problems. Such problems may result from any of a number of equipment failures of the system, or from adverse environmental conditions affecting the system. By notifying the user by way of his associated broadcast communication receiver in a timely manner, call traffic at the call center of the entity operating the system can be greatly reduced, thus addressing the concerns, and potentially reducing the frustration, of the users impacted by the problem. The lower call center volume also allows call center representatives to be more effective in resolving other user issues.
Embodiments of the present invention may be embodied in electronic hardware, software, or some combination thereof located within the broadcast communication receivers and distribution facilities described above. Such software may include instructions executable by one or more processors located and operating within each of the receivers and distribution facilities discussed herein.
While several embodiments of the invention have been discussed herein, other embodiments encompassed by the scope of the invention are possible. For example, while some embodiments of the invention are described above in specific reference to satellite broadcast communications, other communication systems, devices, and methods involving other forms of communication, such as wireline, wireless, or optical communications, may benefit from application of the concepts described herein. For example, satellite radio (SR) communication systems may employ a text display commonly utilized for channel and program identification to relay problem cause and anticipated resolution information to the user. Also, aspects of one embodiment may be combined with those of alternative embodiments to create further implementations of the present invention. Thus, while the present invention has been described in the context of specific embodiments, such descriptions are provided for illustration and not limitation. Accordingly, the proper scope of the present invention is delimited only by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5881289 | Duggan et al. | Mar 1999 | A |
6848062 | Desai et al. | Jan 2005 | B1 |
20020108116 | Dillon | Aug 2002 | A1 |
20030121047 | Watson et al. | Jun 2003 | A1 |
20030208777 | Danker et al. | Nov 2003 | A1 |
20050108759 | Arsenault et al. | May 2005 | A1 |
20080192820 | Brooks et al. | Aug 2008 | A1 |
20100060433 | Karabinis | Mar 2010 | A1 |
Number | Date | Country |
---|---|---|
1047268 | Oct 2000 | EP |
0243322 | May 2002 | WO |
2007021140 | Feb 2007 | WO |
Entry |
---|
International Search Report and Written Opinion issued Jul. 15, 2008. |
“Solar Transit”, Wikipedia, May 9, 2007, 2 pages, http://en.wikipedia.org/w/index.php?title=Solar—transit&printable=yes. |
Public Radio Satellite System, “Solar Outages”, Jun. 21, 2007, 2 Pages,http://www.prss.org/tech—support/solar—outages.cfm. |
Public Radio Satellite System, “Spring Solar Outage Chart”, Jun. 21, 2007, 2 pages, http://www.prss.org/tech—support/spring—so.cfm. |
Public Radio Satellite System, “Fall Solar Outage Chart”, Jun. 21, 2007, 3 pages, http://www.prss.org/tech—support/fall—so.cfm. |
Kyle J. Way, “DirecTV® Indication of Possible Solar Outage”, Jun. 21, 2007, 1 page. |
Number | Date | Country | |
---|---|---|---|
20100253785 A1 | Oct 2010 | US |