CN101095353A - A system and method for grouping program identifiers into multicast groups - Google Patents

Abstract

The disclosed embodiments relate to a system and method for grouping program identifiers into multicast groups. More specifically, a method is provided, comprising: receiving a request for satellite service from a requester device (22), wherein the request includes at least one program identifier; creating a second set of program identifiers; the identifier is compared with a previously requested first program identifier set stored on the satellite service providing device (14); and if the requested program identifier matches one of the program identifiers in the first program identifier set matches, then the matched program identifier is moved from the first program identifier group to the second program identifier group, wherein the multicast of the second program identifier group is suitable for sharing by the requesting device (22) and another device .

Description

Systems and methods for grouping program identifiers into multicast groups

technical field

The present invention generally relates to sending video or other digital data over a network. More specifically, the present invention relates to a system for grouping program identifiers ("PIDs") into multicast groups for Internet Protocol ("IP") delivery in order to provide uninterrupted Serve.

Background technique

This section is intended to introduce the reader to various prior art that may be related to various aspects of the present invention that are described and/or claimed below. It is believed that this discussion helps to provide the reader with a background in which to better understand aspects of the invention. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

Over the past few years, most people realize that satellite TV systems such as DirecTV have become more common. In fact, since the introduction of DirecTV in 1994, more than 12 million American households have become satellite TV subscribers. Most of these subscribers live alone where it is relatively easy to install and connect a satellite dish. For example, a satellite TV dish can be mounted on a roof.

However, many potential subscribers live or temporarily reside in multi-dwelling units ("MDUs"), such as hotels or high-rise apartment buildings. Unfortunately, providing satellite television service to individual living units within an MDU involves additional challenges. It is impractical and/or prohibitively expensive to provide and connect a satellite television dish to each household. For example, in a high-rise apartment building with a thousand apartments, it is impractical to install a thousand satellite TV dishes on the roof of the building. Some traditional systems avoid these problems by converting the digital satellite TV signal to an analog signal that can be sent to multiple households over a single coaxial cable. However, these systems offer limited channels, reduced quality compared to all-digital systems, and do not provide the satellite TV experience that single-family users are accustomed to.

What is needed is an improved system and/or method for providing satellite television to multi-dwelling units.

Contents of the invention

Certain aspects commensurate in scope with the originally claimed invention are presented below. It should be understood that these aspects are presented merely to provide the reader with a brief description of certain forms the invention might take and that these aspects are not intended to limit the scope of the invention. Indeed, the invention may include various aspects not presented below.

The disclosed embodiments relate to systems and methods for grouping program identifiers into multicast groups. More specifically, a method is provided, comprising: receiving a request for satellite service from a requester device (22), wherein the request includes at least one program identifier; creating a second set of program identifiers; comparing the identifier with a previously requested first program identifier set stored on the satellite service providing device (14); and if the requested program identifier matches one of the program identifiers in the first program identifier set , then the matched program identifier is moved from the first program identifier group to a second program identifier group, wherein multicasting of the second program identifier group is suitable for sharing by the requesting device (22) and another device.

Description of drawings

Advantages of the present invention will become apparent when the following detailed description is read in conjunction with the accompanying drawings, in which:

1 is a block diagram of an exemplary satellite IP television system according to one embodiment of the present invention;

Fig. 2 is another embodiment of the exemplary satellite IP television system shown in Fig. 1;

Figure 3 is a block diagram of an exemplary satellite gateway of the present invention; and

FIG. 4 is a flowchart illustrating grouping program identifiers into multicast groups according to an embodiment of the present invention.

Detailed ways

One or more specific embodiments of the invention are described below. In an effort to provide a concise description of these embodiments, not all features of an actual implementation are described in the specification. It should be recognized that, as in any engineering or design project, in the development of any actual implementation, a number of implementation-specific decisions must be made to achieve the developer's specific objectives, such as constraints related to the system and business Compatibility, which is different for different implementations. Furthermore, it should be appreciated that such development might be complex and time consuming, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure.

Turning to FIG. 1 , reference numeral 10 generally designates and illustrates a block diagram of an exemplary satellite IP television system according to one embodiment. As shown, in one embodiment, system 10 may include one or more satellite dishes 12a through 12m, a head-end unit such as satellite gateway 14, an IP distribution network ) 20 and one or more set-top boxes ("STB") 22a to 22n. However, one of ordinary skill in the art will recognize that the embodiment of system 10 shown in FIG. 1 is only one possible embodiment of system 10 . Likewise, illustrated components of system 10 may be rearranged or omitted, or additional components may be added to system 10, in alternative embodiments. For example, with minor modifications, system 10 could be configured for distributed non-satellite video and audio services.

Satellite television dishes 12a-12m may be configured to receive video, audio, or other types of television-related data transmitted from satellites orbiting the earth. As will be described below, in one embodiment, satellite dishes 12a-12m are configured to receive DirecTV programmed on the KU band from 10.7 to 12.75 gigahertz ("GHz"). However, in alternative embodiments, the satellite dishes 12a-12m may be configured to receive other types of Direct Broadcast Satellite ("DBS") or Television Reception Only ("TVRO") signals, such as Dish Network signals, ExpressVu signal, StarChoice signal, etc. In other non-satellite based systems, satellite dishes 12a-12m may be omitted from system 10.

In one embodiment, low noise block converters ("LNCs") in satellite dishes 12a-12m receive input signals from orbiting satellites and convert these input signals to 950 and 2150 megahertz ("MHz") ”) of the L-band frequency. As will be described in further detail below in conjunction with FIG. 2, each of the satellites 12a-12m may be configured to receive one or more incoming satellite television signals (referred to as transponders) on a particular frequency and having a particular polarization, And it is used to convert these satellite signals into L-band signals, and each L-band signal can contain multiple video or audio signals.

Satellite dishes 12a-12m may be configured to transmit L-band signals to a headend unit or gateway server, such as satellite gateway 14. In alternative non-satellite embodiments, the headend unit may be a cable television receiver, high definition television receiver, or other video distribution system.

The satellite gateway 14 includes a satellite tuning, demodulation and demultiplexing module 16 and an IP wrapper module 18 . Module 16 may include a plurality of tuners, demodulators and demultiplexers to convert the modulated and multiplexed L-band signals transmitted from satellites 12a-12m into a plurality of Single Program Transport Streams ("SPTS"), Each SPTS carries services (eg, TV channel video, TV channel audio, program guide, etc.). In one embodiment, module 16 is configured to generate a single program transport stream for all services received by satellite dishes 12a-12m. However, in alternative embodiments, module 16 may generate transport streams for only a subset of the services received by satellite dishes 12a-12m.

The satellite tuner, demodulation and demultiplexer module 16 may send the SPTS to the IP wrapper module 18 . In one embodiment, IP wrapper module 18 repackets the data in the SPTS into a plurality of Internet Protocol (“IP”) packets suitable for transmission over IP distribution network 20 . For example, IP wrapper module 18 may convert DirectTV protocol packets in SPTS to IP packets. Additionally, IP wrapper 18 may be configured to receive server requests from STBs 22a-22n and to multicast (i.e., broadcast by IP address to one or more STBs 22a-22n) IP SPTS to those STBs 22a requesting a particular service -22n.

In an alternative embodiment, the IP wrapper module 18 may also configure the IP protocol SPTS for multicasting services not requested by one of the STBs 22a-22n. It should be noted that modules 16 and 18 are merely one exemplary embodiment of satellite gateway 14 . In alternative embodiments, such as the embodiment described below in conjunction with FIGS. 2 and 3 , the functionality of modules 16 and 18 may be redistributed or combined among various suitable components or modules.

IP distribution network 20 may include one or more routers, switches, modems, splitters or bridges. For example, in one embodiment, the satellite gateway 14 may be connected to a main distribution frame ("MDF") which is connected to an intermediate distribution frame ("IDF") which is connected to the coaxial cable of the Ethernet bridge , the Ethernet bridge is connected to the router, and the router is connected to one or more of the STBs 22a-22n. In another embodiment, the IP distribution network 20 may be an MDF connected to a digital subscriber line access multiplexer ("DSLAM") connected to a DSL modem connected to a router. In another embodiment, the IP distribution network may include a wireless network, such as an 802.11 or WiMax network. In such embodiments, STBs 2a-22n may include wireless receivers configured to receive multicast IP packets. Those of ordinary skill in the art will recognize that the above-described embodiments are exemplary only. Likewise, a number of suitable forms of IP distribution networks may be employed in system 10 in alternative embodiments.

IP distribution network 20 may be connected to one or more STBs 22a-22n. The STBs 22a-22n may be any suitable type of video, audio or other data receiver capable of receiving IP packets such as IP SPTS over the IP distribution network 20. It will be appreciated that the term set top box ("STB") as used herein may not only include devices located on televisions. Rather, the STBs 22a-22n may be any device or device, internal or external to a television, monitor, or computer, described herein as being configurable to include, but not limited to, a video component, computer, wireless telephone, or other form of video recorder . In some embodiments, STBs 22a-22n may also be referred to as integrated receiver decoders ("IRDs").

In one embodiment, the STBs 22a-22n may be DirectTV receivers configured to receive services such as video and/or audio through Ethernet ports (among other inputs). However, in alternative embodiments, the STBs 22a-22n may be designed and/or configured to receive multicast transmissions over coax, twisted pair, copper wire, or wirelessly via a wireless standard such as the IEEE 802.11 standard .

As described above, system 10 may receive video, audio and/or other data transmitted in space by satellites and process/convert the data for distribution over IP distribution network 20 . Accordingly, FIG. 2 is another embodiment of an exemplary satellite IP television system 10 according to one embodiment. Figure 2 shows three exemplary satellite television dishes 12a-12c. Each satellite dish 12a-12c may be configured to receive signals from one or more satellites orbiting the Earth. Those of ordinary skill in the art will recognize that satellites and signals transmitted from satellites are often referred to in terms of the orbital slots in which the satellites are located. For example, satellite dish 12a is configured to receive a signal from a DirecTV satellite located in an orbital slot of 101 degrees. Similarly, satellite dish 12b receives a signal from a satellite located at 119 degrees, and satellite dish 12c receives a signal from a satellite located in an orbital slot at 110 degrees. It will be appreciated that in alternative embodiments, the satellite dishes 12a-12c may receive signals from a plurality of other satellites located in a plurality of orbital slots, for example 95 degree orbital slots. Additionally, the satellite dishes 12a-12c may also be configured to receive polarized satellite signals. For example, in FIG. 2, satellite dish 12a is configured to receive signals of left polarization (shown as "101L" in the figure) and right polarization (shown as "101R").

As described above in connection with FIG. 1 , satellite dishes 12 a - 12 c receive KU-band satellite signals and convert these signals to L-band signals for transmission to satellite gateway 14 . However, in some embodiments, the L-band signals generated by the satellite dishes 12a - 12c may be combined into fewer signals or split into more signals before reaching the satellite gateway 14 . For example, as shown in FIG. 2, the L-band signals from the satellite dishes 12b and 12c may be combined via switch 24 into a single L-band signal containing satellites from 110 degrees and 119 degrees. the L-band signal.

As shown, the system 10 may also include a plurality of 1:2 splitters 26a, 26b, 26c, and 26d for splitting the L-band signal transmitted from the satellite dishes 12a-12c into two L-band signals, each L-band signal comprises half of the service of the L-band signal before splitting. In alternative embodiments, 1:2 splitters 26a-26b may be omitted or integrated into satellite gateways 14a and 14b.

The newly split L-band signals may be sent from 1:2 splitters 26a-26d to satellite gateways 14a and 14b. The embodiment of system 10 shown in FIG. 2 includes two satellite gateways 14a and 14b. However, in alternative embodiments, system 10 may include any suitable number of satellite gateways 14 . For example, in one embodiment, the system may include three satellite gateways 14 .

The satellite gateways 14a and 14b can further subdivide the L-band signal and then tune to one or more services on the L-band signal to produce one or more services that can be repackaged into IP packets and multicast on the IP distribution network 20. SPTS. Additionally, one or more satellite gateways 14a, 14b may also be connected to a public switched telephone network ("PSTN") 28 . Since the satellite gateways 14a, b are connected to the PSTN 28, the STBs 22a-22n can communicate with satellite service providers through the IP distribution network 20 and the satellite gateways 14a, b. This function advantageously eliminates the need for connecting each individual STB 22a-22n directly to the PSTN 28.

The IP distribution network 20 may also be connected to an Internet Service Provider (“ISP”) 30 . In one embodiment, IP distribution network 20 may be used to provide Internet services, such as high-speed data access, to STBs 22a-22n and/or other suitable devices (not shown) connected to IP distribution network 20.

As mentioned above, the satellite gateways 14a, b may be configured to receive multiple L-band signals, to generate multiple SPTSs, and to multicast the requested SPTSs over the IP distribution network 20 . Referring now to FIG. 3 , a block diagram of an exemplary satellite gateway 14 is shown. As shown, the satellite gateways 14a,b include a power supply 40 , two front ends 41a and 41b and a back end 52 . The power supply 40 may be any of a number of industry standard AC or DC power supplies, configurable to enable the front end 41a, b and back end 52 to perform the functions described below.

The satellite gateways 14a,b may also include two front ends 41a,b. In one embodiment, each front end 41a, b is configurable to receive two L-band signal inputs from the 1:2 splitters 26a-26d described with reference to FIG. For example, the front end 41a can receive two L-band signals from the 1:2 splitter 26a, and the front end 41b can receive two L-band signals from the 1:2 splitter 26b. In one embodiment, each L-band of the input front ends 41a, b includes eight or fewer services.

The front ends 41a, b may then use 1:4 L-band splitters 42a, 42b, 42c and 42d to further subdivide the L-band input. Once subdivided, the L-band signal may pass into four banks 44a, 44b, 44c and 44d of the dual tuner chain. Each dual-tuner link in groups 44a-44d is configurable to tune to two services within the L-band signal received by the individual dual-tuner link to generate SPTS. Each dual tuner link may then send the SPTS to one of low voltage differential signaling ("LVDS") drivers 48a, 48b, 48c, and 48d. LVDS drivers 48 a - 48 d may be configured to amplify transmit signals for sending to backend 52 . In alternative embodiments, instead of LVDS drivers 48a-48d, different forms of differential drivers and/or amplifiers may be used. Other embodiments may employ serialization of all transmission signals to be routed to the backend 52 together.

As shown, the front ends 41a, b may also include microprocessors 46a and 46b. In one embodiment, the microprocessors 46a, 46b may control and/or relay commands to the sets of dual tuner links 44a-44d and the 1:4 L-band splitters 42a-42d. Microprocessors 46a,b may comprise ST10 microprocessors produced by ST Microelectronics. Microprocessors 46a, b may be connected to LVDS receiver and transmitter modules 50a and 50b. The LVDS receiver/transmitter modules 50a, b may facilitate communication between the microprocessors 46a, b and components on the backend 52, as described below.

Turning next to backend 52, backend 52 includes LVDS receivers 54a, 54b, 54c, and 54d configured to receive transport stream signals sent by LVDS drivers 48a-48d. Backend 52 also includes LVDS receiver/transmitter modules 56a and 56b configured to communicate with LVDS receiver/transmitter modules 50a, b.

As shown, LVDS receivers 54a-54d and LVDS receiver/transmitters 56a, b are configured to communicate with transport processors 58a and 58b. In one embodiment, the transport processors 58a,b are configured to receive SPTS generated by the dual tuner link in the front end 41a,b. For example, in one embodiment, transport processors 58a, 58b may be configured to generate 16 SPTS. The transport processors 58a, b may be configured to repacketize the SPTS into IP packets that may be multicast on the IP distribution network 20 . For example, transport processors 58a, b may repacket DirecTV protocol packets into IP protocol packets, and then multicast these IP packets to one or more STBs 22a-22n on IP addresses.

The transport processors 58a, b may also be connected to a bus 62, such as a 32-bit, 66 Mz Peripheral Component Interconnect ("PCI") bus. Through bus 62 , transport processors 58 a , b may communicate with network processor 70 , Ethernet interface 84 and/or expansion slot 66 . Network processing 70 may be configured to receive requests for services from STBs 22a-22n and instruct transport processors 58a, b to multicast the requested services. In one embodiment, the network processor is an IXP425 network processor produced by Intel. Although not shown, the network processor 70 may also be configured to send status data to the front panel of the satellite gateway 14a, b, or to support debugging or monitoring of the satellite gateway 14a, b through a debug port.

The transport processors 58a, b are also connected to an Ethernet interface 68 via a bus 62, as shown. In one embodiment, Ethernet interface 68 is a Gigabit Ethernet interface providing a copper or fiber optic interface to IP distribution network 20 . In addition, the bus 62 can also be connected to expansion slots, such as PCI expansion slots, so that the satellite gateways 14a, b can be upgraded or expanded.

The transport processors 58a,b are also connected to a host bus 64. In one embodiment, the contour 64 is a 16-bit data bus connecting the transport processors 58a, b to a modem 72, which is configurable for communication over the PSTN 28 as described above. In an alternative embodiment, a modem 72 may also be connected to the bus 62 .

As noted above, satellite gateway 14 may be configured to receive services such as video, audio, or other data and to multicast these services over IP distribution network 20 to STBs 22a-22n. In one embodiment, satellite gateway 14 multicasts services by grouping related services into a single multicast. For example, if one of the STBs 22a-22n requests video and audio for an ABC television broadcast, one of the satellite gateways 14 may group the program identifier for the video portion of the ABC broadcast along with the program identifier for the audio portion of the ABC broadcast as a satellite gateway 14 Multicast groups that can be multicast on specific IP addresses. If another of the STBs 22a-22n wishes to watch the same ABC broadcast with the same audio, the satellite gateway 14 may order the STBs 22a-22n to access the IP address associated with the previously created multicast group.

The techniques described above work well for creating multicast groups when the program identifiers have a static relationship. However, as described below, additional techniques may be beneficial if program identifier relationships become more complex. For example, the above ABC broadcast may be one of the STBs 22a-22n requesting only the ABC broadcast, one of the STBs 22a-22n requesting a split-screened NBC broadcast with the ABC broadcast, and one of the STBs 22a-22n requesting the ABC broadcast Another plea for split-screen CBS. In this case, creating one multicast group that includes only ABC broadcasts, another multicast group that includes NBC broadcasts and ABC broadcasts, and another multicast group that includes ABC broadcasts and CBS broadcasts may not be an efficient use of bandwidth.

Accordingly, FIG. 4 is a flowchart illustrating an exemplary technical solution 80 for grouping program identifiers into multicast groups according to one embodiment. As shown in FIG. 82, aspect 80 may begin by setting the counter SPTSNum equal to zero and clearing the set of system program identifiers ("PIDs") known as the system PIDset. The system PISset may be an array of PIDsets that the satellite gateway 14 is currently multicasting or previously multicasting. Next, as indicated at block 83, the satellite gateway may create a conflicting PIDset. In one embodiment, satellite gateway 14 may create a conflicting PIDset for each transponder that satellite gateway 14 is receiving. However, in alternative embodiments, different criteria may be used to create conflicting PIDsets.

After creating the conflicting PIDset, as represented by block 84, the satellite gateway 14 may receive a request from one of the STBs 22a-22n (see FIG. 1) containing PIDs for one or more services. Once the satellite gateway 14 receives the PID request, as indicated at block 86 , the satellite gateway 14 may group the requested PIDs into a temporary PIDset for the requesting STB, referred to as the client PIDset.

After packetizing the requested PID, as shown at block 88, the satellite gateway 14 may determine whether the number of SPTS is greater than zero. If the number of SPTS is equal to zero (ie not greater than zero), technical solution 80 will proceed to block 102 as described below. However, if the number of SPTSs is greater than zero, then as shown in block 90, the satellite gateway 14 determines whether the client PIDset intersects with the system PIDset (i.e., whether any PID in the client PIDset is in a PIDset within the system PIDset array). If the customer PIDset does not intersect with the system PIDset, then technical solution 80 will proceed to block 102 as further described below.

However, if the client PIDset does intersect with the system PIDset, then as shown at block 92, the satellite gateway 14 determines whether the client PIDset intersects with more than one system PIDset at more than one PID. If the client PIDset only intersects at one PID, then as shown at block 94, the satellite gateway 14 may add the PIDs in the client PIDset that are not already in the intersected system PIDset to the intersected system PIDset. In an alternative embodiment, block 92 may be omitted from solution 80, and the satellite gateway 14 may proceed to block 98 regardless of the number of intersections. Returning to block 96, once the intersection PID has been added to the intersecting system PIDset, the satellite gateway 14 may respond by sending Requested STB 22a-22n. Furthermore, in the event that a later collision involves a PID in the intersecting system PIDset, the satellite gateway 14 may respond with a multicast of the transponder's conflicting PIDset associated with the client PIDset even if the conflicting PIDset is empty , so that the STBs 22a-22n can monitor for conflicting multicasts. After the response, the technical solution may loop back to block 84 when another of the STBs 22a-22n requests service.

Turning to block 92, if the client PIDset intersects the system PIDset at more than one PID, then as shown at block 98, the satellite gateway 14 may remove from each intersecting system PIDset the client PIDset that intersects the intersecting system PIDset PID. Next, as represented by block 100, the satellite gateway 14 may add the intersection PID to the conflicting PIDset. After creating the conflicting PIDset, the satellite gateway 14 may add the client PIDset to the system PIDset array, as indicated by block 102 , and increment the counter SPTSNum, as indicated by block 104 .

After performing these tasks, the satellite gateway 14 can create the multicast group containing the PID from the system PIDset array (i.e., the PID in the aforementioned client PIDset minus the PID in the conflicting PIDset) and the group containing the PID from the conflicting PIDset at array position SPTSNum-1. The multicast group responds to the requesting STB 22a-22n. As noted above, in the event that a later collision involves one of the PIDs in the client PIDset, the satellite gateway 14 may use the value of the multicast group to respond so that the STB can monitor for conflicting multicasts. Finally, as shown, solution 80 may loop back to block 84 when another of STBs 22a-22n requests service.

While the invention can readily be modified in many ways and in alternative forms, specific embodiments are illustrated in the drawings and described in detail herein. It should be understood, however, that the invention is not intended to be limited to the particular forms disclosed. Rather, the invention covers all modifications, equivalents and alternatives falling within the spirit and scope of the invention as defined by the appended claims.

Claims (20)

1. A method comprising: receiving a request for satellite service from a requester device (22), wherein the request includes at least one program identifier; creating a second set of program identifiers; comparing the requested program identifier with a previously requested first set of program identifiers stored on the satellite service providing device (14); and If the requested program identifier matches one of the program identifiers in the first program identifier group, the matched program identifier is moved from the first program identifier group to a second program identifier group, wherein A multicast of two program identifier sets is adapted to be shared by a requester device (22) and another device. 2. The method of claim 1, comprising sending the service associated with the second set of program identifiers to the requester device (22). 3. The method of claim 2, wherein sending the service comprises multicasting the service over an IP distribution network (20). 4. The method of claim 1, comprising: creating a third set of program identifiers that includes requested program identifiers that do not match one of the program identifiers in the first set of program identifiers; and The services associated with the program identifiers in the third set of program identifiers are sent to the requester device (22). 5. A method as claimed in claim 4, comprising storing the third set of program identifiers on the satellite service providing device (14). 6. The method of claim 1, wherein receiving the request for satellite service from the requester device (22) comprises receiving a request for DirecTV satellite programming. 7. The method of claim 1, wherein receiving a request for satellite service from a requester device comprises receiving a satellite television request from a set top box. 8. A system comprising: A head end unit (14) configured for: receiving a request for satellite service from a requester device (22), wherein the request includes at least one program identifier; creating a second set of program identifiers; comparing the requested program identifier with a previously requested first set of program identifiers stored on the satellite service providing device (14); and If the requested program identifier matches one of the program identifiers in the first program identifier group, the matched program identifier is moved from the first program identifier group to a second program identifier group, wherein A multicast of two program identifier sets is adapted to be shared by a requester device (22) and another device. 9. The system of claim 8, wherein the head-end unit (14) is configured to send the service associated with the program identifiers of the second set of program identifiers to the requester device (22). 10. The system of claim 8, wherein the head-end unit (14) is configured to transmit services associated with program identifiers in the second set of program identifiers to the set-top box (22). 11. The system of claim 8, wherein the head-end unit (14) is configured to multicast the service to the set-top boxes (22) over the IP distribution network (20). 12. The system according to claim 8, wherein the head-end unit (14) is configured to: creating a third set of program identifiers that includes requested program identifiers that do not match one of the program identifiers in the first set of program identifiers; and The services associated with the program identifiers in the third set of program identifiers are sent to the requester device (22). 13. The system of claim 8, wherein the headend unit is configured to receive requests for DirecTV satellite programming. 14. A head end unit (14), comprising: means for receiving a request for satellite service from a requester device (22), wherein the request includes at least one program identifier; means for creating a second set of program identifiers; means for comparing the requested program identifier with a previously requested first set of program identifiers stored on the satellite service providing means (14); and means for moving the matched program identifier from the first program identifier group to the second program identifier group when the requested program identifier matches one of the program identifiers in the first program identifier group , wherein the multicast of the second set of program identifiers is adapted to be shared by the requestor device (22) and another device. 15. The head-end unit (14) of claim 14, comprising means for sending the service associated with the program identifiers of the second set of program identifiers to the requester device (22). 16. A head-end unit (14) according to claim 14, comprising means for multicasting the service to set-top boxes (22) over an IP distribution network (20) 17. The head-end unit (14) according to claim 14, comprising: means for creating a third set of program identifiers that includes a requested program identifier that does not match one of the program identifiers in the first set of program identifiers; and Means for sending the service associated with the program identifiers in the third set of program identifiers to the requester device (22). 18. The head-end unit (14) of claim 14, comprising means for storing the third set of program identifiers on the head-end unit (14). 19. The head-end unit (14) of claim 14, wherein the means for receiving the request for satellite service from the requester device (22) comprises receiving a request for DirecTV satellite programming. 20. The head-end unit (14) of claim 14, wherein the means for receiving a request for satellite service from a requester device comprises a receiver configured to receive a request from a set-top box.

Images