Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
  • H04N21/47—End-user applications
  • H04N21/472—End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N7/00—Television systems
  • H04N7/20—Adaptations for transmission via a GHz frequency band, e.g. via satellite
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
  • H04L65/60—Network streaming of media packets
  • H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
  • H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
  • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
  • H04N21/24—Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
  • H04N21/2408—Monitoring of the upstream path of the transmission network, e.g. client requests
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
  • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
  • H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
  • H04N21/2668—Creating a channel for a dedicated end-user group, e.g. insertion of targeted commercials based on end-user profiles
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
  • H04N21/61—Network physical structure; Signal processing
  • H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
  • H04N21/6143—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via a satellite
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
  • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
  • H04N21/64—Addressing
  • H04N21/6405—Multicasting
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
  • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
  • H04N21/643—Communication protocols
  • H04N21/64322—IP

Definitions

• the present invention relates generally to transmitting 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 such a way as to provide uninterrupted service to clients.
• PIDs program identifiers
• IP Internet Protocol
• An improved system and/or method for providing satellite TV to a multi-dwelling unit is desirable.
• the disclosed embodiments relate to a system and method for grouping program identifiers into multicast groups. More specifically, there is provided a method comprising receiving a request for satellite services from a requester device (22), wherein the request includes at least one program identifier, creating a second group of program identifiers, comparing the requested program identifier with a first group of previously requested program identifiers stored on a satellite service providing device (14), and moving the matching program identifier from the first group of program identifiers to the second group of program identifiers if the requested program identifier matches one of the program identifiers in the first group of program identifiers, wherein a multicast of the second group of program identifiers is adapted to be shared by the requester device (22) and another device.
• FIG. 1 is a block diagram of an exemplary satellite television over IP system in accordance with one embodiment of the present invention
• FIG. 2 is another embodiment of the exemplary satellite television over IP system illustrated in FIG. 1 ;
• FIG. 3 is a block diagram of an exemplary satellite gateway of the present invention.
• FIG. 4 is a flow chart illustrating an exemplary technique for grouping program identifiers into multicast groups in accordance with embodiments of the present invention.
• FIG. 1 a block diagram of an exemplary satellite television over IP system in accordance with one embodiment is illustrated and generally designated by a reference numeral 10.
• the system 10 may include one or more satellite dishes 12a through 12m, a head-end unit, such as a satellite gateway 14, an IP distribution network 20, and one or more set top boxes ("STBs") 22a through 22n.
• STBs set top boxes
• FIG. 1 is merely one potential embodiment of the system 10.
• the illustrated components of the system 10 may be rearranged or omitted or additional components may be added to the system 10.
• the system 10 may configured to distributed non-satellite video and audio services.
• the satellite dishes 12a-12m may be configured to receive video, audio, or other types of television-related data that is transmitted from satellites orbiting the earth. As will be described further below, in one embodiment the satellite dishes 12a-12m are configured to receive DirecTV programming over KU band from 10.7 to 12.75 Gigahertz ("GHz"). In alternate embodiments, however, the satellite dishes 12a- 12m may be configured to receive other types of direct broadcast satellites ("DBS") or television receive-only (“TVRO”) signal, such as Dish Network signals, ExpressVu signals, StarChoice signals, and the like. In still other non-satellite based systems, the satellite dishes 12a- 12m may be omitted from the system 10.
• DBS direct broadcast satellites
• TVRO television receive-only
• the satellite dishes 12a- 12m may be omitted from the system 10.
• a low noise-block converter (“LNC") within the satellite dishes 12a-12m receives the incoming signal from the earth- orbiting satellite and converts these incoming signals to a frequency in the L band between 950 and 2150 Megahertz ("MHz").
• LNC low noise-block converter
• each of the satellites 12a-12m may be configured to receive one or more incoming satellite TV signals on a particular frequency (referred to as a transponder) and with a particular polarization and to convert these satellite signals to L band signals, each of which may contain a plurality of video or audio signals.
• the satellite dishes 12a-12m may be configured to transmit the L band signals to a head-end unit or gateway server, such as the satellite gateway 14.
• the head-end unit may be a cable television receiver, a high definition television receiver, or other video distribution system
• the satellite gateway 14 includes a satellite tuning, demodulating, and demultiplexing module 16 and an IP wrapper module 18.
• the module 16 may contain a plurality of tuners, demodulators, and demultiplexers to convert the modulated and multiplexed L band signals transmitted from the satellites 12a-12m into a plurality single program transport streams ("SPTS"), each of which carries a service (e.g., television channel video, television channel audio, program guides, and so forth).
• SPTS program transport streams
• the module 16 is configured to produce a single program transport stream for all of the services received by the satellite dishes 12a-12m. In an alternate embodiment, however, the module 16 may produce transport streams for only a subset of the services received by the satellite dishes 12a-12m.
• the satellite tuning, demodulating, and demultiplexing module 16 may transmit the SPTS to the IP wrapper module 18.
• the IP wrapper module 18 repackages the data within the SPTS into a plurality of internet protocol ("IP") packets suitable for transmission over the IP distribution network 20.
• IP internet protocol
• the IP wrapper module 18 may convert DirecTV protocol packets within the SPTS into IP packets.
• the IP wrapper module 18 may be configured to receive server requests from the STBs 22a-22n and to multicast (i.e., broadcast to one or more of the STBs 22a-22n over an IP address) the IP SPTS to those STBs 22a-22n that had requested the particular service.
• the IP wrapper module 18 may also be configured to multicast IP protocol SPTS for services not requested by one of the STBs 22a-22n.
• the modules 16 and 18 are merely one exemplary embodiment of the satellite gateway 14. In alternate embodiments, such as the one described below in regard to FIGS. 2 and 3, the functions of the modules 16 and 18 may be redistributed or consolidated amongst a variety of suitable components or modules.
• the IP distribution network 20 may include one or more routers, switches, modem, splitters, or bridges.
• the satellite gateway 14 may be coupled to a master distribution frame ("MDF") that is coupled to an intermediate distribution frame (“IDF") that is coupled to a coax to Ethernet bridge that is coupled to a router that is coupled to one or more of the STBs 22a-22n.
• MDF master distribution frame
• IDF intermediate distribution frame
• the IP distribution network 20 may be an MDF that is coupled to a Digital Subscriber Line Access Multiplexer (“DSLAM”) that is coupled to a DSL modem that is coupled to a router.
• DSL modem Digital Subscriber Line Access Multiplexer
• the IP distribution network may include a wireless network, such as 802.11 or WiMax network.
• the STBs 22a-22n may include a wireless receiver configured to receive the multicast IP packets.
• a wireless receiver configured to receive the multicast IP packets.
• the IP distribution network 20 may 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 the IP SPTS, over the IP distribution network 20.
• IP IP packets
• STB set top box
• the STBs 22a-22n may encompass not only devices that sit upon televisions. Rather the STBs 22a-22n may be any device or apparatus, whether internal or external to a television, display, or computer, that can be configured to function as described herein - including, but not limited to a video components, computers, wireless telephones, or other forms video recorder.
• the STBs 22a-22n may also be known as an integrated receiver decoder ("IRD").
• the STBs 22a-22n may be a DirecTV receiver configured to receive services, such as video and/or audio, through an Ethernet port (amongst other inputs).
• the STBs 22a-22n may be designed and/or configured to receive the multicast transmission over coaxial cable, twisted pair, copper wire, or through the air via a wireless standard, such as the I.E.E.E. 802.11 standard.
• FIG. 2 is another embodiment of the exemplary satellite television over IP system 10 in accordance with one embodiment.
• FIG. 2 illustrates three exemplary satellite dishes 12a-12c.
• Each of the satellite dishes 12a-12c may be configured to receive signals from one or more of the orbiting satellites.
• the satellites and the signals that are transmitted from the satellites are often referred to by the orbital slots in which the satellites reside.
• the satellite dish 12a is configured to receive signals from a DirecTV satellite disposed in an orbital slot of 101 degrees.
• the satellite dish 12b receives signals from a satellite disposed at 119 degrees
• the satellite dish 12c receives signals from a satellite disposed at orbital slot of 110 degrees.
• the satellite dishes 12a-12c may receive signals from a plurality of other satellites disclosed in a variety of orbital slots, such as the 95 degree orbital slot.
• the satellite dishes 12a-12c may also be configured to receive polarized satellite signals.
• the satellite dish 12a is configured to receive signals that are both left polarized (illustrated in the figure as "101 L") and right polarized (illustrated as "101 R").
• the satellite dishes 12a- 12c may receive satellite signals in the KU band and convert these signals into L band signals that are transmitted to the satellite gateway 14.
• the L band signals produced by the satellite dishes 12a-12c may be merged into fewer signals or split into more signals prior to reaching the satellite gateway 14.
• L band signals from the satellite dishes 12b and 12c may be merged by a switch 24 into a single L band signal containing the L band signals from both the satellite at 110 degrees and the satellite at 119 degrees.
• the system 10 may also include a plurality of 1:2 splitters 26a, 26b, 26c, and 26d to divide the L band signals transmitted from the satellite dishes 12a-12c into two L band signals, each of which include half of the services of the pre-split L band signal.
• the 1 :2 splitters 26a-26b may be omitted or integrated into the satellite gateways 14a and 14b.
• the newly split L band signals may be transmitted from the 1:2 splitters 26a-26d into the satellite gateways 14a and 14b.
• the embodiment of the system 10 illustrated in FIG. 2 includes two of the satellite gateways 14a and 14b. In alternate embodiments, however, 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 may then further subdivide the L band signals and then tune to one or more services on the L band signal to produce one or more SPTS that may be repackaged into IP packets and multicast over the IP distribution network 20.
• one or more of the satellite gateways 14a, 14b may also be coupled to a public switch telephone network ("PSTN") 28. Because the satellite gateways 14a, b are coupled to the PSTN 28, the STBs 22a-22n may be able to communicate with a satellite service provider through the IP distribution network 20 and the satellite gateways 14a, b. This functionality may advantageously eliminate the need to have each individual STBs 22a-22n coupled directly to the PSTN 28.
• PSTN public switch telephone network
• the IP distribution network 20 may also be coupled to an internet service provider ("ISP") 30.
• ISP internet service provider
• the IP distribution network 20 may be employed to provide internet services, such as highspeed data access, to the STBs 22a-22n and/or other suitable devices (not shown) that are coupled to the IP distribution network 20.
• the satellite gateways 14a, b may be configured to receive the plurality of L band signals, to produce a plurality of SPTS, and to multicast requested SPTS over the IP distribution network 20.
• FIG. 3 a block diagram of an exemplary satellite gateway 14 is shown.
• the satellite gateway 14a, b includes a power supply 40, two front-ends 41a and 41b and a back-end 52.
• the power supply 40 may be any one of a number of industry-standard AC or DC power supplies configurable to enable the front-ends 41a, b and the back-end 52 to perform the functions described below.
• the satellite gateway 14a, b may also include two front-ends 41a, b.
• each of the front-ends, 41a, b may be configured to receive two L band signal inputs from the 1 :2 splitters 26a-26d that were described above in regards to FIG. 2.
• the front-end 41a may receive two L band signals from the 1:2 splitter 26a and the front-end 41 b may receive two L band signals from the 1 :2 splitter 26b.
• each of the L band inputs into the front-end 41a, b includes eight or fewer services.
• the front-ends 41a, b may then further sub-divide the L band inputs using 1 :4 L band splitters 42a, 42b, 42c, and 42d.
• the L band signals may pass into four banks 44a, 44b, 44c, and 44d of dual tuner links.
• Each of the dual tuner links within the banks 44a-44d may be configured to tune to two services within the L band signals received by that individual dual tuner links to produce SPTS.
• Each of the dual tuner links may then transmit the SPTS to one of the low-voltage differential signaling ("LVDS") drivers 48a, 48b, 48c, and 48d.
• the LVDS drivers 48a-48d may be configured to amplify the transport signals for transmission to the back-end 52.
• the front-ends 41a, b may also include microprocessors 46a and 46b.
• the microprocessors 46a, b may control and/or relay commands to the banks 44a-44d of dual tuner links and the 1 :4 L band splitters 42a-42d.
• the microprocessors 46a, b may comprise ST10 microprocessors produce by ST
• the microprocessors 46a, b may be coupled to LVDS receiver and transmitter modules 50a and 50b.
• the LVDS receiver/transmitter modules 50a, b may facilitate communications between the microprocessors 46a, b and components on the back-end 52, as will be described further below.
• the back-end 52 includes LVDS receivers 54a, 54b, 54c, and 54d, which are configured to receive transport stream signals transmitted by the LVDS drivers 48a-48d.
• the back-end 52 also includes LVDS receiver/transmitter modules 56a and 56b which are configured to communicate with the LVDS receiver/ transmitter modules 50a, b.
• the LVDS receivers 54a-54d and the LVDS receiver/transmitters 56a, b are configured to communicate with transport processors 58a and 58b.
• the transport processors 58a, b are configured to receive the SPTS produced by the dual tuner links in the front-ends 41a, b.
• the transport processors 58a, b may be configured to produce 16 SPTS.
• the transport processors 58a, b may be configured to repack the SPTS into IP packets which can be multicast over the IP distribution network 20.
• the transport processors 58a, b may repackage DirecTV protocol packets into IP protocol packets and then multicast these IP packets on an IP address to one or more of the STBs 22a-22n
• the transport processors 58a, b may also be coupled to a bus 62, such as a 32 bit, 66 MHz peripheral component interconnect ("PCI") bus. Through the bus 62, the transport processors 58a, b may communicate with a network processor 70, an Ethernet interface 84, and/or an expansion slot 66.
• the network processor 70 may be configured to receive requests for services from the STBs 22a-22n and to direct the transport processors 58a, b to multicast the requested services.
• the network processor is an IXP425 network processor produced by Intel. While not illustrated, the network processor 70 may also be configured to transmit status data to a front panel of the satellite gateway 14a, b or to support debugging or monitoring of the satellite gateway 14a, b through debug ports.
• the transport processors 58a, b may also be coupled to the Ethernet interface 68 via the bus 62.
• the Ethernet interface 68 is a gigabit Ethernet interface that provides either a copper wire or fiber-optic interface to the IP distribution network 20.
• the bus 62 may also be coupled to an expansion slot, such as a PCI expansion slot to enable the upgrade or expansion of the satellite gateway 14a, b.
• the transport processors 58a, b may also be coupled to a host bus
• the host bus 64 is a 16-bit data bus that connects the transport processors 58a, b to a modem 72, which may be configured to communicate over the PSTN 28, as described above.
• the modem 72 may also be coupled to the bus 62.
• the satellite gateways 14 may be configured to receive services, such as television video, audio, or other data and to multicast these services to the STBs 22a-22n across the IP distribution network 20.
• the satellite gateways 14 multicast services by grouping related services into a single multicast. For example, if one of the STBs 22a-22n requests the video and audio for an ABC television broadcast, one of the satellite gateways 14 may group a program identifier for the video portion of the ABC broadcast along with a program identifier for the audio portion of the ABC broadcast into a multicast group that the satellite gateway 14 can multicast at a particular IP address. If another one of the STBs 22a-22n wishes to view the same ABC broadcast with the same audio, the satellite gateway 14 can direct that STB 22a-22n to access the IP address associated with the previously created multicast group.
• the above described technique works well for creating multicast groups when the program identifiers have static relationships.
• additional techniques may be advantageous if program identifier relationships become more complex.
• the above-described ABC broadcast may be requested by one of the STBs 22a-22n requesting just the ABC broadcast as well as one of the STBs 22a-22n requesting an NBC broadcast split-screened with the ABC broadcast as well as another one of the STBs 22a-22n requesting a CBS split-screened with the ABC broadcast.
• creating one multicast group containing just the ABC broadcast, another multicast group containing the NBC broadcast and the ABC broadcast, and yet another multicast group containing the ABC broadcast and the CBS broadcast may be an inefficient use of bandwidth.
• FIG. 4 is a flowchart illustrating an exemplary technique 80 for grouping program identifiers into multicast groups in accordance with one embodiment.
• the technique 80 may begin by setting a counter SPTSNum equal to zero and emptying a set of system program identifiers ("PIDs"), referred to as the system PIDset.
• the system PIDset may be an array of PIDsets currently being multicast or previously multicast by the satellite gateway 14.
• the satellite gateway may create a collision PIDset, as indicated by block 83.
• the satellite gateway 14 may create one collision PIDset for each transponder being received by the satellite gateway 14. In alternate embodiments, however, different criteria may be used to create collision PIDsets.
• 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, as indicated in block 84. Once the satellite gateway 14 has received the PID request, it may group the requested PIDs into a temporary PIDset for the requesting STB, which is referred to as the client PIDset, as indicated in block 86.
• the satellite gateway 14 may determine whether the number of SPTS is greater than zero, as indicated in block 88. If the number of SPTS is equal to zero (i.e., not greater than zero), the technique 80 will proceed to block 102, as described below. If, however, the number of SPTS is greater than zero, the satellite gateway 14 will determine whether the client PIDset intersects with the system PIDset (i.e., whether any of the PIDs within the client PIDset are in any of the PIDsets within the system PIDset array), as indicated in block 90. If the client PIDset does not intersect with the system PIDset, the technique 80 will proceed to block 102, as will be described further below.
• the satellite gateway 14 will determine whether the client PIDset intersects more than one system PIDset at more than one PID, as indicated in block 92. If the client PIDset intersects at only one PID, the satellite gateway 14 may add the PID within the client PIDset that was not already in the intersecting system PIDset into the intersecting system PIDset, as indicated in block 94. In alternate embodiments, block 92 may be omitted from the technique 80, and the satellite gateway 14 may proceed to block 98 regardless of the number of intersections.
• the satellite gateway 14 may respond to the requesting STB 22a-22n with the IP address of the multicast group containing the intersecting system PIDset (which now includes the one additional PID from the client PIDset). Further, even though the collision PIDset is empty, the satellite gateway 14 may also respond with a multicast for the collision PIDset for the transponder associated with the client PIDset so that the STB 22a-22n can monitor the collision multicast in the event of a later collision involving the one of the PIDs in the intersecting system PIDset. After responding, the technique may loop back to block 84 when another one of the STBs 22a- 22n makes a request for services.
• the satellite gateway 14 may move the intersecting PIDs from both the client PIDset and the intersecting system PIDset for each intersecting system PIDset, as indicated in block 98. Next, the satellite gateway 14 may add the intersecting PIDs to the collision PIDset, as indicated in block 100. After creating the collision PIDset, the satellite gateway 14 may add the client PIDset into the system PIDset array, as indicated in block 102 and increment the counter SPTSNum, as indicated in block 104.
• the satellite gateway 14 may respond to the requesting STB 22a-22n with a multicast group that contains the PIDs from the system PIDset array at array location SPTSNum minus one (i.e., the former client PIDset minus the PIDs in the collision PIDset) and a multicast group containing the PIDs from the collision PIDset.
• the satellite gateway 14 respond with a multicast group for the collision PIDset associated with the transponder associated with the Client PIDset so that the STB can monitor the collision multicast in the event of a later collision involving the one of the PIDs in the client PIDset.
• the technique 80 may loop back to block 84 when another one of the STBs 22a-22n makes a request for services.

Landscapes

• Engineering & Computer Science (AREA)
• Multimedia (AREA)
• Signal Processing (AREA)
• General Physics & Mathematics (AREA)
• Physics & Mathematics (AREA)
• Astronomy & Astrophysics (AREA)
• Databases & Information Systems (AREA)
• Computer Networks & Wireless Communication (AREA)
• Human Computer Interaction (AREA)
• Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Radio Relay Systems (AREA)
• Mobile Radio Communication Systems (AREA)

Applications Claiming Priority (1)

Publications (1)

Family

ID=35907002

Family Applications (1)

Country Status (7)

Families Citing this family (2)

Citations (1)

Family Cites Families (10)

• 2005
  • 2005-10-26 KR KR1020077015303A patent/KR101243194B1/ko active IP Right Grant
  • 2005-10-26 BR BRPI0519749-0A patent/BRPI0519749A2/pt not_active IP Right Cessation
  • 2005-10-26 JP JP2008537672A patent/JP4848426B2/ja not_active Expired - Fee Related
  • 2005-10-26 MX MX2007008244A patent/MX2007008244A/es active IP Right Grant
  • 2005-10-26 EP EP05818206A patent/EP1941728A1/de not_active Withdrawn
  • 2005-10-26 CN CN2005800458362A patent/CN101095353B/zh not_active Expired - Fee Related
  • 2005-10-26 WO PCT/US2005/038990 patent/WO2007050080A1/en active Application Filing

Patent Citations (1)

Also Published As

Similar Documents

Legal Events