JP4848426B2 - System and method for grouping program identifiers into multicast groups - Google Patents

Description

  The present invention relates generally to the transmission of video and other digital data over a network. In particular, the present invention relates to a system that groups program identifiers (“PID”) into multicast groups for Internet Protocol (“IP”) distribution so as to provide a continuous service to clients.

  This portion is intended to illustrate various aspects of the art that may relate to various aspects of the present invention as set forth in the specification and / or claims. This description is believed to be useful for providing background information to facilitate a deeper understanding of various aspects of the present invention. Accordingly, the foregoing description is read in light of this and is not to be construed as a prior art.

  As is known to most people, satellite television systems (such as DirecTV) have been popular throughout the past few years. In fact, since the advent of DirecTV in 1994 AD, over 12 million American homes have become satellite TV subscribers. Most of the subscribers mentioned above live in single dwellings where satellite antennas are relatively easy to install and connect. For example, the satellite antenna can be installed on the roof of a house.

  However, many potential subscribers live in a multi-unit ("MDU") (such as a hotel or high-rise apartment building) or stay temporarily. Unfortunately, there are additional challenges associated with providing satellite TV services to individual units within an MDU. It may be impractical and / or very expensive to provide and connect one satellite antenna per unit. For example, in a high-rise apartment building with one thousand apartments, it may be impractical to mount 1,000 satellite antennas on the roof of the building. Some conventional systems have avoided the aforementioned problems by converting digital satellite television signals into analog signals that can be transmitted to multiple units over a single coaxial cable. However, the above-mentioned system has a limited number of channels to be provided, has a lower quality than an all-digital system, and cannot provide a satellite TV experience familiar to users living in single dwelling units.

  It would be desirable to have an improved system and / or method for providing satellite TV to multi-units.

  Specific aspects corresponding to the initial description range of the claims will be described below. The foregoing aspects are presented merely to provide a brief summary of the specific forms that the invention can take, and are not intended to limit the scope of the invention. Indeed, the invention may encompass a variety of aspects that may not be described below.

  The disclosed embodiments relate to a system and method for grouping program identifiers into multicast groups. In particular, receiving a request for satellite service from the requesting device (22), wherein the request includes at least one program identifier, creating a second program identifier group, The step of comparing with the first preceding request program identifier group stored on the satellite service providing device (14), and the matching program identifier, the requested program identifier is one of the program identifiers in the first program identifier group And moving to the second program identifier group from the first program identifier group, the multicast of the second program identifier group is shared by the requesting device (22) and another device. Provide a method adapted to

  The advantages of the present invention will become apparent upon reading the following detailed description and upon reference to the accompanying drawings.

  One or more specific embodiments of the present invention are described below. In an effort to provide a concise description of the foregoing embodiments, not all features of an actual implementation are described in the specification. As with any engineering or design project, the development of any of the above realization means makes many decisions specific to the realization means, and the specific goals of the developer (system Compliance with related constraints and business related constraints) must be achieved. Furthermore, the development effort described above is complex and time consuming, but becomes a routine task of design, assembly and manufacture for those skilled in the art who benefit from the present disclosure.

  Turning to FIG. 1, a block diagram of an exemplary satellite television over IP system according to one embodiment is shown, and is generally indicated by reference numeral 10. As shown, in one embodiment, the system 10 includes one or more satellite antennas 12a-12m, a headend device (such as a satellite gateway 14), an IP distribution network 20, and one or more set-top devices. Boxes ("STB") 22a-22n may be included. However, those skilled in the art will recognize that the embodiment of the system 10 shown in FIG. 1 is only one potential embodiment of the system 10. As such, in other embodiments, the illustrated components of system 10 can be rearranged or omitted, or additional components can be added to system 10. For example, the system 10 can be configured to deliver non-satellite video and audio services with minor modifications.

The satellite antennas 12a-12m can be configured to receive video, audio and other types of television-related data transmitted from satellites orbiting the earth. As described further below, in one embodiment, satellite antennas 12a-12m are configured to receive direcTV programming via the KU band of 10.7-12.75 gigahertz ("GHz"). However, in another embodiment, the satellite antennas 12a-12m may be other types of direct broadcast satellite ("DBS") or television receive only ("TVRO") signals (Dish network signals, express view signals, star choices). Signal, etc.) can be received. In still other non-satellite based systems, the satellite antennas 12a-12m can be omitted from the system 10.
In one embodiment, a low noise block converter ("LNC") in satellite antennas 12a-12m receives the received signal from the Earth orbiting satellite and in the L band between 950 MHz ("MHz") and 2150 MHz. Convert the aforementioned received signal to frequency. As will be described in more detail below with respect to FIG. 2, each of the satellites 12a-12m receives one or more received satellite TV signals on a particular frequency (denoted transponder) and with a particular polarization. It can be configured to receive and convert the aforementioned satellite signals into L-band signals, each of which may include multiple video or audio signals.

  Satellite antennas 12a-12m can be configured to transmit L-band signals to a headend device or gateway server (such as satellite gateway 14). In another, non-satellite embodiment, the headend device may be a cable television receiver, a high definition television receiver, or other video distribution system.

The satellite gateway 14 includes a satellite tuning / demodulation / demultiplexing module 16 and an IP wrapper module 18. Module 16 is configured from satellites 12a-12m into a plurality of single program transport streams ("SPTS") each containing services (eg, television channel video, television channel audio, program guide, etc.). A plurality of tuners, demodulators and demultiplexers may be included for converting to a modulated and multiplexed L-band signal to be transmitted. In one embodiment, module 16 is configured to generate a single program transmission stream for all services received by satellite antennas 12a-12m. However, in another embodiment, module 16 can generate a transport stream of only a subset of services received by satellite antennas 12a-12m.
The satellite tuning / demodulation / demultiplexing module 16 can send the SPTS to the IP wrapper module 18. In one embodiment, the IP wrapper module 18 repackages the data in the SPTS into a plurality of Internet Protocol (“IP”) packets suitable for transmission over the IP distribution network 20. For example, the IP wrapper module 18 can convert a DIRECTTV protocol packet in the SPTS into an IP packet. In addition, the IP wrapper module 18 receives server requests from the STBs 22a-22n and multicasts IP SPTSs to the STBs 22a-22n that requested a particular service (ie, via one or more STBs 22a-22n via an IP address). Broadcast).

  In another embodiment, the IP wrapper module 18 may be configured to multicast the IP protocol SPTS for services not requested by one of the STBs 22a-22n. Modules 16 and 18 are just one exemplary embodiment of satellite gateway 14. In other embodiments (such as those described below with respect to FIGS. 2 and 3), the functionality of modules 16 and 18 may be redistributed or aggregated among various suitable components or modules.

  The IP distribution network 20 may include one or more routers, switches, modems, splitters or bridges. For example, in one embodiment, satellite gateway 14 is combined with a master distribution frame (“MDF”), a master distribution frame (“MDF”) is combined with an intermediate distribution frame (“IDF”), and an intermediate distribution frame (“IDF”) is combined. ”) To the coaxial-Ethernet® bridge, the coaxial-Ethernet® bridge to the router, and the router to one or more STBs 22a-22n. In another example, IP distribution network 20 may be an MDF coupled to a digital subscriber line access multiplexer (“DSALM”) coupled to a DSL modem coupled to a router. In yet another example, the IP distribution network may include a wireless network (such as an 802.11 or WiMax network). In this type of embodiment, STBs 22a-22n may include a wireless receiver configured to receive multicast IP packets. Those skilled in the art will recognize that the foregoing embodiments are merely exemplary. As such, in other embodiments, a number of suitable forms of IP distribution networks can be used in the system 10.

  The IP distribution network 20 can be coupled to one or more STBs 22a-22n. The STBs 22a-22n may be any suitable type of video, audio and / or other data receiver capable of receiving IP packets (such as IP SPTS) via the IP distribution network 20. The term set top box ("STB") used in the specification and claims may not only encompass what is located on a television receiver. Rather, STBs 22a through 22n may be configured to function as described herein and in the claims, whether in or outside a television receiver, display or computer. It can be a device or an apparatus, including but not limited to video components, computers, wireless telephones and other forms of video recorders. In certain embodiments, STBs 22a-22n may also be known as integrated receiver decoders ("IRDs").

  In one embodiment, STBs 22a-22n may be directory TV receivers configured to receive services (such as video and / or audio) via an Ethernet port (among other inputs). . However, in another embodiment, the STBs 22a-22n are designed and / or configured to receive multicast transmissions via coaxial cable, stranded wire, copper wire, or wirelessly according to a wireless standard (such as the IEEE 802.11 standard). be able to.

  As described above, the system 10 can receive video, audio, and / or other data transmitted by satellites in space and process / convert this data for distribution via the IP distribution network 20. . Thus, FIG. 2 is another embodiment of an exemplary satellite television over IP system 10 according to one embodiment. FIG. 2 shows three exemplary satellite antennas 12a-12c. Each of the satellite antennas 12a-12c can be configured to receive signals from one or more orbiting satellites. Those skilled in the art will recognize that satellites and signals transmitted from satellites are often represented by the orbiting slots in which the satellites reside. For example, the satellite antenna 12a is configured to receive a signal from a direcTV satellite disposed in a 101 degree round slot. Similarly, the satellite antenna 12b receives a signal from a satellite arranged at 119 degrees, and the satellite antenna 12c receives a signal from a satellite arranged in a 110 degree round slot. In another embodiment, satellite antennas 12a-12c may receive signals from other satellites in various orbiting slots (such as a 95 degree orbiting slot). Furthermore, the satellite antennas 12a to 12c can be configured to receive polarized satellite signals. For example, in FIG. 2, the satellite antenna 12a is configured to receive a left polarization (illustrated as “101 L”) signal and a right polarization (illustrated as “101 R”) signal.

  As described above with respect to FIG. 1, the satellite antennas 12 a-12 c can receive satellite signals in the KU band and convert the aforementioned signals into L-band signals that are transmitted to the satellite gateway 14. However, in certain embodiments, the L-band signals generated by satellite antennas 12a-12c can be merged into fewer signals or split into more signals before reaching satellite gateway 14. . For example, as shown in FIG. 2, L-band signals from satellite antennas 12b and 12c are merged by switch 24 into a single L-band signal that includes L-band signals from a satellite at 110 degrees and a satellite at 119 degrees. can do.

  As shown, the system 10 includes a plurality of 1 for dividing the L-band signal transmitted from the satellite antennas 12a to 12c into two L-band signals each containing half of the service of the L-band signal before the division. : 2 splitters 26a, 26b, 26c and 26d can also be included. In another embodiment, the 1: 2 splitters 26a-b can be omitted or integrated into the satellite gateways 14a and 14b.

  The newly split L-band signal can be transmitted from the 1: 2 splitters 26a-26d to the satellite gateways 14a and 14b. The embodiment of the system 10 shown in FIG. 2 includes two of the satellite gateways 14a and 14b. However, in other embodiments, the 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 then further divide the L-band signal, then tune to one or more services on the L-band signal, repackage into IP packets, and multicast via the IP distribution network 20 One or more SPTS can be generated. Further, one or more satellite gateways 14 a, 14 b can also be coupled to a public switched telephone network (“PSTN”) 28. Since the satellite gateways 14a, 14b are coupled to the PSTN 28, the STBs 22a-22n may be able to communicate with the satellite service provider via the IP distribution network 20 and the satellite gateways 14a, 14b. This function effectively eliminates the need to couple each individual STB 22a-22n directly to the PSTN 28.

The IP distribution network 20 may also be coupled to an Internet service provider (“ISP”) 30. In one embodiment, IP distribution network 20 is used to provide Internet services (such as high-speed data access) to STBs 22a-22n and / or other suitable devices (not shown) coupled to IP distribution network 20. can do.
As described above, the satellite gateways 14 a, 14 b can be configured to receive a plurality of L-band signals, generate a plurality of SPTSs, and multicast the requested SPTSs via 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, 14b include a power source 40, two front ends 41a and 41b, and a back end 52. The power supply 40 can be any one of several industry standard AC or DC power supplies that can be configured to allow the front ends 41a, 41b and the back end 52 to perform the functions described below. .

  The satellite gateways 14a, 14b may also include two front ends 41a, 41b. In one embodiment, each of the front ends 41a, 41b can be configured to receive two L-band signal inputs from the 1: 2 splitters 26a-26d previously described with respect 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 input to the front ends 41a, 41b includes no more than eight services.

  The front ends 41a, 41b can then further divide the L-band input using 1: 4 L-band splitters 42a, 42b, 42c and 42d. Once split, the L-band signal can go to the four banks 44a, 44b, 44c and 44d of the dual tuner link. Each dual tuner link in banks 44a-44d may be configured to tune to two services in the L-band signal received by that individual dual tuner link to generate an SPTS. Each of the dual tuner links can then send the SPTS to one of the low voltage differential signal (“LDVS”) drivers 48a, 48b, 48c and 48d. The LVDS drivers 48a-48d can be configured to amplify the L-band transmission band signal for transmission to the backend 52. In other embodiments, various forms of differential drivers and / or amplifiers can be used in place of the LVDS drivers 48a-48d. Other embodiments can use serializing all of the transmitted signals together for routing to the backend 52.

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

  Turning now to the back end 52, the back end 52 includes LVDS receivers 54a, 54b, 54c and 54d configured to receive transmission stream signals transmitted by the LVDS drivers 48a-48d. The back end 52 also includes LVDS receiver / transmitter modules 56a, 56b configured to communicate with the LVDS receiver / transmitter modules 50a, 50b.

  As shown, LVDS receivers 54a-54d and LVDS receiver / transmitters 56a, 56b are configured to communicate with transmission processors 58a and 58b. In one embodiment, the transmission processors 58a, 58b are configured to receive SPTS generated by the dual tuner links in the front ends 41a, 41b. For example, in one embodiment, transmission processors 58a, 58b can be configured to generate 16 SPTSs. The transport processors 58a, 58b can be configured to repack the SPTS into IP packets that can be multicast over the IP distribution network 20. For example, the transmission processors 58a, 58b can repackage DIRECTTV protocol packets into IP protocol packets and then multicast the aforementioned IP packets on IP addresses to one or more STBs 22a-22n.

  The transmission processors 58a, 58b may also be coupled to a bus 62 (such as a 32-bit, 66 MHz peripheral component interconnect ("PCI") bus). Via bus 62, transmission processors 58 a, 58 b can communicate with network processor 70, Ethernet interface 84, and / or expansion slot 66. The network processor 70 can be configured to receive service requests from the STBs 22a-22n and instruct the transmission processors 58a, 58b to multicast the requested service. In one embodiment, the network processor is an IXP425 network processor produced by Intel. Although not shown, the network processor 70 transmits status data to the front panel of the satellite gateways 14a, 14b or supports debugging or monitoring of the satellite gateways 14a, 14b via the debug port. It can also be configured.

  As shown, transmission processors 58 a, 58 b can also be coupled to Ethernet interface 68 via bus 62. In one embodiment, Ethernet interface 68 is a Gigabit Ethernet interface that includes a copper or fiber optic interface to IP distribution network 20. In addition, the bus 62 may be coupled to an expansion slot (such as a PCI expansion slot to allow upgrade or expansion of the satellite gateways 14a, 14b).

  The transmission processors 58a, 58b can also be coupled to the host bus 64. In one embodiment, host bus 64 is a 16-bit data bus that couples transmission processors 58a, 58b to modem 72 that can be configured to communicate via PSTN 28, as described above. In another embodiment, modem 72 can be coupled to bus 62.

  As described above, the satellite gateway 14 can be configured to receive services (such as television video, audio and other data) and to multicast the services to the STBs 22a-22n via the IP distribution network 20. . In one embodiment, satellite gateway 14 multicasts services by grouping related services into a single multicast. For example, if one of the STBs 22a to 22n requests ABC television broadcast video and audio, one of the satellite gateways 14 will display the program identifier of the video portion of the ABC broadcast and the program identifier of the audio portion of the ABC broadcast. In addition, the satellite gateways 14 can be grouped into multicast groups that can be multicast at a specific IP address. If another one of the STBs 22a-22n wants to watch the same ABC broadcast with the same audio, the satellite gateway 14 informs the STB 22a-22n that it will access the IP address associated with the previously created multicast group. It is possible to instruct.

  The above approach works well for creating multicast groups where program identifiers have a static relationship. However, as will be described later, when the program identifier relationship becomes more complicated, a further method may be effective. For example, the above-described ABC broadcast requires only one of the ABC broadcasts, one of the STBs 22a to 22n, and one of the STBs 22a to 22n that requests the NBC broadcast divided from the ABC broadcast, and the ABC broadcast and the screen division. Can be requested by another one of the STBs 22a to 22n, which requests the broadcast CBS broadcast. In the above case, creating one multicast group that includes only ABC broadcasts, another multicast group that includes NBC broadcasts and ABC broadcasts, and yet another multicast group that includes ABC broadcasts and CBS broadcasts is an inefficient bandwidth. Can be use.

  Thus, FIG. 4 is a flow diagram illustrating an exemplary technique 80 for grouping program identifiers into multicast groups, according to one embodiment. As shown at block 82, technique 80 may begin by setting a counter SPTSNum equal to zero and emptying the system program identifier (“PID”) group represented as system PIDset. The system PIDset may be multicast by the satellite gateway 14 or may be a previously multicast PIDset array. The satellite gateway can then create a collision PIDset as indicated by block 83. In one embodiment, the satellite gateway 14 can create one collision PIDset for each transponder received by the satellite gateway 14. However, in other embodiments, the collision PIDset can be created using various criteria.

  After creating the collision PIDset, the satellite gateway 14 may receive a request from one of the STBs 22a-22n (FIG. 1), including the PID of one or more services, as shown at block 84. Upon receiving the PID request, the satellite gateway 14 can group the requested PIDs into the requesting STB's temporary PIDset, represented as a client PIDset, as shown in block 86.

  After grouping the request PIDs, the satellite gateway 14 can determine whether the SPTS number is greater than zero, as shown in block 88. If the SPTS number is equal to zero (ie, not greater than zero), the technique 80 proceeds to block 102 as described below. However, if the SPTS number is greater than zero, the satellite gateway 14 determines whether the client PIDset intersects the system PIDset (ie, any of the PIDs in the client PIDset is in the system PIDset, as shown in block 90). It is determined whether or not any of the above. If the client PIDset does not intersect the system PIDset, the technique 80 proceeds to block 102 as further described below.

  However, if the client PIDset actually intersects the system PIDset, the satellite gateway 14 determines whether the client PIDset intersects two or more system PIDsets at two or more PIDs, as shown at block 92. If the client PIDset intersects only in one PID, the satellite gateway 14 can add the PID in the client PIDset that was not already in the intersection system PIDset to the intersection system PIDset, as shown in block 94. In another example, block 92 may be excluded from approach 80 and 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 intersection system PIDset, the satellite gateway 14 (by including one additional PID from the client PIDset in this case) by the IP address of the multicast group containing the intersection system PIDset. It can respond to the requests STB 22a to 22n. Further, even if the collision PIDset is empty, the satellite gateway 14 is associated with the client PIDset so that the STBs 22a-22n can monitor the collision in the event of a subsequent collision for one of the PIDs in the cross system PIDset. It is also possible to respond to the transponder collision PIDset multicast. After responding, the approach can return to block 84 once again if another one of the STBs 22a-22n makes a service request.

  Returning to block 92, if the client PIDset intersects the system PIDset at two or more PIDs, the satellite gateway 14 moves the intersection PID from the client PIDset and the intersecting PIDset for each intersecting system PIDset, as shown at block 98. be able to. Next, as shown in block 100, the satellite gateway 14 can add the intersecting PID to the collision PIDset. After creating the collision PIDset, the satellite gateway 14 can add the client PIDset to the system PIDset array, as shown in block 102, and can increment the counter SPTSNum, as shown in block 104.

  After performing the above tasks, by a multicast group that includes the PID from the system PIDset array at the array location (SPTSNum-1) (ie, the PID in the preceding client PIDset-collision PIDset) and the multicast group that includes the PID from the collision PIDset It can respond to the requests STB 22a to 22n. As noted above, even if the collision PIDset is empty (ie, even if SPTSNum is equal to zero), the satellite gateway 14 responds with the multicast group of collision PIDsets associated with the transponders associated with the client PIDset, so the STB It is possible to monitor the collision multicast in the case of a later collision for one of the PIDs in the client PIDset. Finally, as shown, technique 80 may return to block 84 once again if another one of STBs 22a-22n makes a service request.

  While the invention is amenable to various modifications and alternative forms, specific embodiments have been shown by way of example in the accompanying drawings and will be described in detail herein. It is not intended, however, to limit the invention to the particular forms described. On the contrary, the invention is intended to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the invention as defined by the claims.

1 is a block diagram of an exemplary satellite television over IP system according to one embodiment of the present invention. FIG. FIG. 3 illustrates another embodiment of the exemplary satellite television over IP system shown in FIG. 2 is a block diagram of an exemplary satellite gateway of the present invention. FIG. FIG. 4 is a flow diagram illustrating an exemplary technique for grouping program identifiers into multicast groups, according to an embodiment of the present invention.

Claims (17)

A method,
Receiving a request for satellite service from a requesting device, wherein the request includes at least one program identifier;
Comparing the at least one program identifier in the received request with each set of first pre-requested program identifier groups stored on a satellite service providing device;
A program in the first program identifier group when a program identifier in the set of program identifiers in the first program identifier group matches a program identifier in the at least one program identifier in the received request. Moving a program identifier of the set of identifiers to a set of conflicting program identifiers;
Creating a new set of program identifiers, wherein the new set of program identifiers comprises a requested program identifier that did not match a program identifier in any set in the first program identifier group; ,
Responding to the request with the first set of program identifiers including the new set of program identifiers and the set of conflicting program identifiers.   The method of claim 1, comprising the step of transmitting a service associated with the set of program identifier collisions to the requesting device.   The method of claim 2, wherein transmitting the service comprises multicasting the service over an IP distribution network.   4. The method of claim 3, comprising storing the new set of program identifiers on the satellite service providing device.   The method of claim 1, wherein receiving a request for satellite service from a requesting device comprises receiving a request for a DirecTV satellite program.   2. The method of claim 1, wherein receiving a request for satellite service from a requester comprises receiving a request for satellite television from a set top box. A system,
Receiving a request for satellite service from a requesting device, wherein the request includes at least one program identifier;
Comparing the at least one program identifier in the received request with each set of first pre-requested program identifier groups stored on a satellite service providing device;
A program in the first program identifier group when a program identifier in the set of program identifiers in the first program identifier group matches a program identifier in the at least one program identifier in the received request. Move a program identifier of the set of identifiers to a set of conflicting program identifiers;
Creating a new set of program identifiers, the set of new program identifiers comprising a requested program identifier that did not match a program identifier in any set in the first set of program identifiers;
A system comprising a headend device adapted to respond to the request by means of the first set of program identifiers including the new set of program identifiers and the set of conflicting program identifiers.   8. The system of claim 7, wherein the headend device is configured to transmit a service associated with a program identifier in the program identifier collision set to the requesting device.   8. The system of claim 7, wherein the headend device is configured to transmit a service associated with a program identifier in the set of program identifier collisions to a set top box.   8. The system of claim 7, wherein the headend device is configured to multicast the service to the set top box via an IP distribution network.   8. The system of claim 7, wherein the headend device is configured to receive a request for a directory TV satellite program. A headend device,
Means for receiving a request for satellite service from a requesting device, wherein the request includes at least one program identifier;
Means for comparing the at least one program identifier in the received request with each set of first pre-requested program identifier groups stored on a satellite service providing device;
A program in the first program identifier group when a program identifier in the set of program identifiers in the first program identifier group matches a program identifier in the at least one program identifier in the received request. Means for moving a program identifier of the set of identifiers to a set of conflicting program identifiers;
Means for creating a new set of program identifiers, wherein the new set of program identifiers comprises a requested program identifier that did not match a program identifier in any set in the first program identifier group; ,
A head end device comprising: the first program identifier group including the new set of program identifiers; and means for responding to the request by a set of conflicting program identifiers.   13. A headend device according to claim 12, comprising means for transmitting a service associated with a program identifier in the set of program identifier collisions to the requesting device.   13. The headend device according to claim 12, wherein the means for transmitting the service comprises means for multicasting the service via an IP distribution network.   13. The head end device according to claim 12, further comprising means for storing the new set of program identifiers on the head end device.   13. The headend device according to claim 12, wherein the means for receiving a request for satellite service from the requesting device comprises means for receiving a request for a directory TV satellite program.   13. The headend device according to claim 12, wherein means for receiving a request for satellite service from a requester is configured to receive the request from a set top box.

Images