In today's television content distribution systems, customers are provided an expansive array of television content. Given the overwhelming amount of television content available to customers, service providers and/or network operators are confronted with various challenges relating to television content distribution. For example, service providers and/or network operators may manage large amounts of television content transfers, as well as deal with time constraints, distribution issues, resource constraints, etc., associated with television content distribution.
The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention.
The term “television content,” as used herein, may include content displayable on a television or other form of a display. For example, television content may include television shows, movies, documentaries, sports, news, on-demand television, pay-per-view programming, local programming, national programming, premium channels, podcasts, and/or other types of content (e.g., television guides, free programming, free events, games, etc.). In an exemplary implementation, television content may be delivered via a television distribution system.
The term “boosting factor,” as used herein, may include a value representing a level of importance of television content relative to other television content. The boosting factor may have a value within a predetermined numerical range (e.g., 1-100). In an exemplary implementation, the boosting factor may be calculated based on viewership data (e.g., local viewership data, national viewership data, etc.) associated with the television content in which local boosting factors and/or a national boosting factor may be derived. Additionally, or alternatively, the boosting factor may be manually assigned (e.g., by a television network administrator).
As will be described herein, a television content distribution system may assign a boosting factor to television content. The boosting factor may be used as a determinant in which television content may be presented to customers, for example, when customers are browsing, searching, etc., for television content. By way of example, but not limited thereto, television content assigned a higher boosting factor may be presented to a customer before (e.g., in terms of time, in terms of order (e.g., in a list, within a category, etc.), etc.) television content assigned a lower boosting factor.
As previously described, a boosting factor may be calculated based on viewership data and/or may be manually assigned. In an exemplary implementation, geographic boosting factors (e.g., local, national) corresponding to geographic viewership (e.g., local, national) may be utilized to calculate the boosting factor. In an exemplary implementation, boosting factor assignment heuristics may be utilized to select an appropriate boosting factor based on the geographic boosting factors. As will be described in greater detail below, the boosting factor assignment heuristics may utilize a relationship between a maximum local boosting factor value and a national boosting factor value to determine the boosting factor for particular television content. Given the time and resources needed to generate and publish boosting factors for television content, the boosting factor assignment heuristics may minimize overhead and resource utilization by assigning the same boosting factor for particular television content in different television distribution site regions.
Home 105 may correspond to a customer site. As illustrated, home 105 may include exemplary customer premise equipment, such as, for example, set top box 110, TV 115, and ONT 120. Set top box 110 may include a device to provide television content to TV 115. Set top box 110 may include a DVR and/or a DVR client. TV 115 may include a device to display television content to a customer. ONT 120 may include a device that provides an interface between an optical distribution network and the customer site. For example, ONT 120 may provide an interface between home 105 and TSO 125.
TSO 125 may correspond to an intermediary television distribution site between home 105 and TDS 140. As illustrated, TSO 125 may include exemplary television distribution devices, such as, for example, OLT 130 and router 135. OLT 130 may include a device that serves as a point of origination for fiber-to-the-premises (FTTP) transmissions coming into and out of TDS 140. Router 135 may include a device that routes television content.
TDS 140 may correspond to a television distribution site. As illustrated, TDS 140 may include exemplary television distribution devices, such as, for example, a DVR management server 145, load balancer 150, search servers 155 and DB cluster 160. “Television distribution device,” as used herein, is intended to be broadly interpreted to include a device that, for example, facilitates the delivery of television content. DVR management server 145 may include a device that manages the recording of television content between customers' DVRs. Load balancer 150 may include a device that manages a load (e.g., the provisioning and delivering of television content to customers) among search servers 155. Load balancer 150 may distribute the processing load associated with delivering television content among search servers 155 in an equally distributed fashion. Search servers 155 may include devices that deliver television content to customers. DB cluster 160 may include a device that stores various types of data, such as, for example, an interactive programming guide (IPG), set top box configuration data, and/or customer profile data.
Data center 165 may correspond to a television distribution site that receives and manages television content. As illustrated, data center 165 may include exemplary television distribution devices, such as, for example, database center 170, publication server 175, and a boosting factor assigner 180. Database center 170 may include a device that stores television content. For example, a television service provider may receive and/or generate updated television content and store the updated television content in database center 170. Publication server 175 may include a device that publishes or pushes the updated television content stored in database center 170 to TDS 140. Boosting factor assigner 180 may include a device that assigns boosting factors to television content.
Referring to
Additionally, or alternatively, boosting factor assigner 180 may be provided with boosting factor assignment data 190. Boosting factor assignment data 190 may include boosting factors to be assigned to television content. For example, a television distribution administrator may provide boosting factor assignment data 190 to boosting factor assigner 180 via a web interface or some other type of interface. In some instances, the television distribution administrator may formulate the boosting factor based on data provided by a third party (e.g., television content provider). For example, the television content provider may be introducing a new television show in which case a boosting factor may be manually assigned by the television distribution administrator.
Boosting factor assigner 180 may calculate boosting factors for television content based on viewership data 185. In an exemplary implementation, boosting factor assigner 180 may determine the number of television content (e.g., the number of television programs) (N), a maximum value of viewership (Max) of television content, and a minimum value of viewership (Min) of television content. Boosting factor assigner 180 may determine (N), (Max), and (Min) for each of the local viewership data associated with TDSs 140-1 through 140-X, and the national viewership data included in viewership data 185. Boosting factor assigner 180 may then utilize the following exemplary expression:
to compute local boosting factors and a national boosting factor. In this exemplary expression, (i) may represent a numerical ranking for the particular television content relative to the other television content, in which the ranking is based on viewership. For example, if N=200 (e.g., 200 television programs), (i) may have a value between 1 through 200. That is, if the particular television content was the most watched television content, the particular television content may be assigned i=200, if the least watched television content, i=1, etc. Based on the above, boosting factor assigner 180 may calculate X number of local boosting factors (e.g., {10, 10, 11 . . . 13}) in correspondence to X number of TDSs 140 (assuming the particular television content was watched by customers in each of TDSs 140-1 through 140-X), and a national boosting factor (e.g., {15}).
Boosting factor assigner 180 may then apply boosting factor assignment heuristics in view of the local and national boosting factors to assign a boosting factor to the particular television content. For example, if a maximum value of the local boosting factors is greater than three times the national boosting factor, then the respective local boosting factors may be assigned as the boosting factor for the particular television content in each TDS 140. On the other hand, if a maximum value of the local boosting factors is less than or equal to three times the national boosting factor, then the national boosting factor may be assigned as the boosting factor for the particular content in each TDS 140.
Referring to
TDSs 140 may apply boosting factors 195 to television content. In this way, when customers search for television content via an interface, the television content may be presented to customers based on boosting factors 195 associated with the television content. For example, as previously described, television content assigned a higher boosting factor 195 (e.g., 100) may be presented to a customer before (e.g., in terms of time, in terms of order (e.g., in a list, within a category, etc.), etc.) television content assigned a lower boosting factor 195 (e.g., 10).
As a result of the foregoing, resource utilization, time, overhead, etc., may be significantly minimized in a television distribution system when applying the boosting factor assignment heuristics described herein. Additionally, or alternatively, television content, which may or may not be considered equally important to customers associated with different television distribution sites (e.g., different TDSs 140), may be presented to the customers according to boosting factors representing an importance of the television content to those customers. For example, Boston Red Sox games may be assigned a higher boosting factor in the Boston region compared to White Sox games. Conversely, White Sox games may be assigned a higher boosting factor in the Chicago region compared to Boston Red Sox games. This may be useful given the amount of television content available to the customer vis-à-vis the limited display screen area of TV 115. Since the exemplary implementation has been broadly described, a more detailed description is provided below.
Processing system 205 may include one or more processors, microprocessors, data processors, co-processors, application specific integrated circuits (ASICs), controllers, programmable logic devices, chipsets, field programmable gate arrays (FPGAs), or some other component that may interpret and/or execute instructions and/or data. Processing system 205 may control the overall operation, or a portion thereof, of device 200, based on, for example, an operating system and/or various applications (e.g., applications 215).
Memory/storage 210 may include one or more memories and/or one or more secondary storages. For example, memory/storage 210 may include a random access memory (RAM), a dynamic random access memory (DRAM), a read only memory (ROM), a programmable read only memory (PROM), a flash memory, and/or some other type of memory. Memory/storage 210 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid state disk, etc.) or some other type of computer-readable medium, along with a corresponding drive. The term “computer-readable medium” is intended to be broadly interpreted to correspond to, for example, a memory, a storage, a compact disc (CD), a digital versatile disc (DVD), or the like. The computer-readable medium may be implemented in a single device, in multiple devices, in a centralized manner, or in a distributed manner. Memory/storage 210 may store data, application(s), and/or instructions related to the operation of device 200. For example, applications 215 may include one or more applications to calculate boosting factors and/or information used to calculate boosting factors.
Communication interface 220 may permit device 200 to communicate with other devices, networks, systems and/or the like. For example, communication interface 220 may include a cable interface, a fiber optic interface, a radio interface, and/or some other type of wireless interface and/or wired interface.
Input 225 may permit a user and/or another component or device to input information into device 200. For example, input 225 may include a keyboard, a keypad, a display, a touchpad, a mouse, a button, a switch, a microphone, an input port, a drive, voice recognition logic, and/or some other type of visual, auditory, and/or tactile input component. Output 230 may permit device 200 to output information from device 200 (e.g., to a user and/or to another component or device). For example, output 230 may include a display, a speaker, light emitting diodes (LEDs), an output port, and/or some other type of visual, auditory, and/or tactile output component.
As described herein, device 200 may perform certain operations in response to processing system 205 executing software instructions contained in a computer-readable medium, such as memory/storage 210. The software instructions may be read into memory/storage 210 from another computer-readable medium or from another device via communication interface 220. The software instructions contained in memory/storage 210 may cause processing system 205 to perform processes described herein. Alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.
Boosting factor assigner 180 may calculate boosting factors for television contents. In an exemplary implementation, boosting factor assigner 180 may calculate numerous local boosting factors and a national boosting factor. In an exemplary case, assume a television content W aired and was watched by customers in each TDS 140. Boosting factor assigner 180 may calculate X+1 boosting factors corresponding to X number of local boosting factors (associated with TDSs 140-1 through TDS 140-X) and one national boosting factor for the television content W.
VC 305 may calculate (N). As previously described, (N) may represent the total number of television contents watched by customers. For example, if in TDS 140-1, 510 television contents were watched by customers, then N=510. When calculating the national boosting factor, (N) may represent the total number of television contents aired and watched by customers on a national level. The value of (N) may be the same or may be different between TDSs 140.
MMVS 310 may select (Max) and (Min) values. As previously described, (Max) may represent a maximum viewership of television content within the local viewership data and the national viewership data, respectively, and (Min) may represent a minimum viewership of television content within the local viewership data and the national viewership data, respectively. For example, if in TDS 140-1, the most watched television content Z had 50,000 customer viewers, then (Max) may have a value of 50,000, and if in TDS 140-1, the least watched television content X had 1,000 customer viewers, then (Min) may have a value of 1,000. It will be appreciated that in some instances, television content W may be selected for (Max) or (Min) values.
LNBF 315 may calculate factor. For example, as described above, a boosting factor may be calculated according to the following exemplary expression:
In this exemplary expression, (i) may represent a numerical ranking for the particular television content (e.g., television content W) relative to the other television content. For example, if N=510 (e.g., 510 television contents), (i) may have a value between 1 through 510. The numerical ranking may be based on the viewership associated with television content W relative to the other television content. Once the variable factor is calculated, the boosting factor may be calculated according to the following exemplary expression:
Math.floor(factor+0.5)=boosting_factor. (2)
In exemplary implementation, the function Math floor may round down (factor+0.5) to the nearest integer. For example, if factor=1.25, adding 0.5 provides Math.floor (1.25+0.5)=1.00. In other implementations, Math.floor may round up (factor+0.5) to the nearest integer. For example, if factor=1.25, adding 0.5 provides Math.floor (1.25+0.5)=2.00.
BFA 320 may assign boosting factors to television content based on the boosting factor assignment heuristics. In an exemplary implementation, the assignment of the boosting factor to television content may be based on differences between the national boosting factor and the local boosting factors. That is, the assignment may include selecting the national boosting factor as the boosting factor or the local boosting factors as the boosting factors for various regions based on the following boosting factor assignment heuristics.
For example, if the maximum of the local boosting factors is greater than three times the national boosting factor, then the respective local boosting factors may be assigned to its corresponding region (e.g., each TDS 140) as the boosting factor. By way of example, assume that for the television content W, six regions have local boosting factors of {3, 4, 5, 6, 7, 30}, respectively, and the national boosting factor is 9. Since the maximum of the local boosting factors is 30, and 30 is greater than three times the national boosting factor 9, the local boosting factors {3, 4, 5, 6, 7, 30} may be assigned to the six regions, respectively, as the boosting factor.
On the other hand, if the maximum of the local boosting factors is less than or equal to three times the national boosting factor, then the national boosting factor may be assigned to each region (e.g., each TDS 140) as the boosting factor. By way of example, assume that for the television content W, six regions have local boosting factors of {3, 4, 5, 6, 7, 8} and the national boosting factor is {7}. Since the maximum of the local boosting factors is 8, and 8 is less than three times the national boosting factor 7, the national boosting factor 7 may be assigned to each of the six regions as the boosting factor (i.e., {7, 7, 7, 7, 7, 7}). BFA 320 may select the boosting factors for television contents based on results of the applied boosting factor assignment heuristics. It will be appreciated that in other implementations, the mathematical relationship between maximum local boosting factors and the national boosting factor may be a value other than three times.
BFP 325 may publish boosting factors 195 to TDSs 140. For example, boosting factor assigner 180 may publish boosting factors 195 via publication server 175 or directly to TDSs 140. In an exemplary implementation, TDSs 140 may obtain boosting factors 195 on a regular basis (e.g., daily or weekly, etc.). Based on the boosting factor assignment heuristics described herein, publication of boosting factors to different regions may be minimized. For example, boosting factors {3, 4, 5, 6, 7, 8} between the six regions are not significantly different in value from the national boosting factor. In such instances, assigning the same boosting factor for each region may significantly reduce resource utilization, time, overhead, etc. associated with publication of the six boosting factors, which is in contrast to when the six regions may be assigned distinct boosting values and these six distinct boosting values are published.
Although
In an exemplary implementation, television content database 405 may include a television content field 410 and a boosting factor field 415. In other implementations, television content database 405 may include additional database fields and/or different database fields.
Television content field 410 may include information identifying a particular television content. For example, television content field 410 may include the name of the television content (e.g., “Boston Legal”) or some other type of identifier. Boosting factor field 415 may include a corresponding boosting factor associated with the particular content. For example, boosting factor field may include a numerical value (e.g., 0-100). As previously described, the boosting factor may be used as a determinant in which television content may be presented to customers, for example, when customers are browsing, searching, etc., for television content.
Process 600 may include receiving viewership data (block 605). For example, boosting factor assigner 180 may receive local viewership data from TDSs 140. Boosting factor assigner 180 may compile national viewership data based on the local viewership data. Viewership data 185 may include the local viewership data and/or the national viewership data.
Boosting factor assignment data may be received (block 610). For example, a television distribution administrator may provide boosting factor assignment data 190 to boosting factor assigner 180 via a web interface or some other type of interface. Boosting factor assignment data 190 may include boosting factors for television content. In an exemplary implementation, boosting factor assignment data 190 may overwrite boosting factors calculated based on viewership data 185.
Local and national boosting factors for television content may be calculated (block 615). For example, boosting factor assigner 180 may calculate local and national boosting factors. In an exemplary implementation, the local and national boosting factors may be calculated based on expressions (1) and (2) above, which is described in more detail with respect to
Boosting factor assignment heuristics may be applied (block 620). For example, BFA 320 may assign boosting factors to television content based on the boosting factor assignment heuristics. In an exemplary implementation, the assignment of the boosting factor to television content may be based on differences between the national boosting factor and the local boosting factors. That is, the assignment may include selecting the national boosting factor as the boosting factor or selecting the local boosting factors as the boosting factors based on the following boosting factor assignment heuristics. For example, as previously described, if the maximum of the local boosting factors is greater than three times the national boosting factor, then the local boosting factors may be assigned to the respective regions (e.g., each TDS 140) as the boosting factor. On the other hand, if the maximum of the local boosting factors is less than or equal to three times the national boosting factor, then the national boosting factor may be assigned to each region (e.g., each TDS 140) as the boosting factor. It will be appreciated that in other implementations, the mathematical relationship between maximum local boosting factors and the national boosting factor may be a value other than three times. That is, the difference may be a value greater than three times or less than three times.
Boosting factors may be selected for television content (block 625). For example, BFA 320 may select the boosting factors for television contents based on results of the applied boosting factor assignment heuristics.
Boosting factors may be published to television distribution sites (block 630). BFP 325 may publish boosting factors 195 to TDSs 140. For example, boosting factor assigner 180 may publish boosting factors 195 via publication server 175 or directly to TDSs 140. BFP 325 may publish boosting factors 195 on a regular basis (e.g., daily or weekly, etc.).
Although
Process 700 may include computing a viewership value (N) (block 705). For example, VC 305 may calculate (N). (N) may represent the total number of television contents aired and watched by customers. When calculating the national boosting factor, (N) may represent the total number of television contents aired and watched by customers on a national level. The value of (N) may be the same or may be different between TDSs 140.
A maximum viewership value (Max) may be selected (block 710). For example, MMVS 310 may select (Max) values within the local viewership data and the national viewership data (i.e., viewership data 185), respectively. (Max) may represent a maximum viewership of television content.
A minimum viewership value (Min) may be selected (block 715). For example, MMVS 310 may select (Min) values within the local viewership data and the national viewership data (i.e., viewership data 185), respectively. (Min) may represent a minimum viewership of television content.
A ranking value (i) may be selected (block 720). For example, LNBF 315 may select an (i) value for a particular television content. As previously described, (i) may represent a numerical ranking for the particular television content (e.g., television content W) relative to the other television content. The numerical ranking may be based on the viewership associated with the particular television content relative to the other television content.
A boosting factor may be computed (block 725). For example, LNBF 315 may calculate factor according to the following exemplary expression:
Once the variable factor is calculated, the boosting factor may be calculated according to the following exemplary expression:
Math.floor(factor+0.5)=boosting_factor. (2)
In exemplary implementation, the function Math floor may round down (factor+0.5) to the nearest integer, which may correspond to a local boosting factor or a national boosting factor.
Although
The foregoing description of implementations provides illustration, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Accordingly, modifications to the implementations described herein may be possible.
The terms “a,” “an,” and “the” are intended to be interpreted to include one or more items. Further, the phrase “based on” is intended to be interpreted as “based, at least in part, on,” unless explicitly stated otherwise. The term “and/or” is intended to be interpreted to include any and all combinations of one or more of the associated items.
In addition, while series of blocks have been described with regard to the processes illustrated in
It will be apparent that devices, methods, and/or systems, described herein may be implemented in many different forms of software or firmware in combination with hardware in the implementations illustrated in the figures. The actual software code (executable by hardware) or specialized control hardware used to implement the device, method, and/or system does not limit the disclosure of the invention. Thus, the operation and behavior of the devices and/or systems, or the performing of the methods was described without reference to the specific software code—it being understood that software and control hardware can be designed to implement the device, method, and/or system based on the description herein.
Further certain features described above may be implemented as “logic” that performs one or more functions. This logic may include hardware, such as one or more processors, one or more microprocessors, one or more ASICs, one or more FPGAs, etc., software, or a combination of hardware and software.
In the preceding specification, various preferred embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded as illustrative rather than restrictive.
No element, act, or instruction used in the present application should be construed as critical or essential to the implementations described herein unless explicitly described as such.
Number | Name | Date | Kind |
---|---|---|---|
4977455 | Young | Dec 1990 | A |
5151789 | Young | Sep 1992 | A |
5253066 | Vogel | Oct 1993 | A |
5307173 | Yuen et al. | Apr 1994 | A |
5335079 | Yuen et al. | Aug 1994 | A |
5353121 | Young et al. | Oct 1994 | A |
5382983 | Kwoh et al. | Jan 1995 | A |
5479266 | Young et al. | Dec 1995 | A |
5479268 | Young et al. | Dec 1995 | A |
5499103 | Mankovitz | Mar 1996 | A |
5512963 | Mankovitz | Apr 1996 | A |
5515173 | Mankovitz et al. | May 1996 | A |
5532732 | Yuen et al. | Jul 1996 | A |
5532754 | Young et al. | Jul 1996 | A |
5541738 | Mankovitz | Jul 1996 | A |
5550576 | Klosterman | Aug 1996 | A |
5553123 | Chan et al. | Sep 1996 | A |
5559550 | Mankovitz | Sep 1996 | A |
5600711 | Yuen | Feb 1997 | A |
5619274 | Roop et al. | Apr 1997 | A |
5640484 | Mankovitz | Jun 1997 | A |
5684525 | Klosterman | Nov 1997 | A |
5701383 | Russo et al. | Dec 1997 | A |
5706145 | Hindman et al. | Jan 1998 | A |
5727060 | Young | Mar 1998 | A |
5734786 | Mankovitz | Mar 1998 | A |
5790198 | Roop et al. | Aug 1998 | A |
5801787 | Schein et al. | Sep 1998 | A |
5808608 | Young et al. | Sep 1998 | A |
5809204 | Young et al. | Sep 1998 | A |
5812205 | Milnes et al. | Sep 1998 | A |
5828945 | Klosterman | Oct 1998 | A |
5870150 | Yuen | Feb 1999 | A |
5886746 | Yuen et al. | Mar 1999 | A |
5915026 | Mankovitz | Jun 1999 | A |
5923362 | Klosterman | Jul 1999 | A |
5940073 | Klosterman et al. | Aug 1999 | A |
5949954 | Young et al. | Sep 1999 | A |
5959688 | Schein et al. | Sep 1999 | A |
5969748 | Casement et al. | Oct 1999 | A |
5970206 | Yuen et al. | Oct 1999 | A |
5974222 | Yuen et al. | Oct 1999 | A |
5987213 | Mankovitz et al. | Nov 1999 | A |
5988078 | Levine | Nov 1999 | A |
5991498 | Young | Nov 1999 | A |
6002394 | Schein et al. | Dec 1999 | A |
6016141 | Knudson et al. | Jan 2000 | A |
6028599 | Yuen et al. | Feb 2000 | A |
6049652 | Yuen et al. | Apr 2000 | A |
6052145 | Macrae et al. | Apr 2000 | A |
6072983 | Klosterman | Jun 2000 | A |
6075551 | Berezowski et al. | Jun 2000 | A |
6075575 | Schein et al. | Jun 2000 | A |
6078348 | Klosterman et al. | Jun 2000 | A |
6091882 | Yuen et al. | Jul 2000 | A |
6118492 | Milnes et al. | Sep 2000 | A |
6133909 | Schein et al. | Oct 2000 | A |
6137950 | Yuen | Oct 2000 | A |
6144401 | Casement et al. | Nov 2000 | A |
6151059 | Schein et al. | Nov 2000 | A |
6167188 | Young et al. | Dec 2000 | A |
6177931 | Alexander et al. | Jan 2001 | B1 |
6216265 | Roop et al. | Apr 2001 | B1 |
6239794 | Yuen et al. | May 2001 | B1 |
6247176 | Schein et al. | Jun 2001 | B1 |
6262722 | Allison et al. | Jul 2001 | B1 |
6263501 | Schein et al. | Jul 2001 | B1 |
6323911 | Schein et al. | Nov 2001 | B1 |
6341195 | Mankovitz et al. | Jan 2002 | B1 |
6341374 | Schein et al. | Jan 2002 | B2 |
6388714 | Schein et al. | May 2002 | B1 |
6396546 | Alten et al. | May 2002 | B1 |
6412110 | Schein et al. | Jun 2002 | B1 |
6430358 | Yuen et al. | Aug 2002 | B1 |
6430359 | Yuen et al. | Aug 2002 | B1 |
6453471 | Klosterman | Sep 2002 | B1 |
6460181 | Donnelly | Oct 2002 | B1 |
6466734 | Yuen et al. | Oct 2002 | B2 |
6469753 | Klosterman et al. | Oct 2002 | B1 |
6477705 | Yuen et al. | Nov 2002 | B1 |
6498895 | Young et al. | Dec 2002 | B2 |
6505348 | Knowles et al. | Jan 2003 | B1 |
6538701 | Yuen | Mar 2003 | B1 |
6549719 | Mankovitz | Apr 2003 | B2 |
6564379 | Knudson et al. | May 2003 | B1 |
6567606 | Milnes et al. | May 2003 | B2 |
6588013 | Lumley et al. | Jul 2003 | B1 |
6668133 | Yuen et al. | Dec 2003 | B2 |
6687906 | Yuen et al. | Feb 2004 | B1 |
6732369 | Schein et al. | May 2004 | B1 |
6742183 | Reynolds et al. | May 2004 | B1 |
6745391 | Macrae et al. | Jun 2004 | B1 |
6756997 | Ward et al. | Jun 2004 | B1 |
6760537 | Mankovitz | Jul 2004 | B2 |
6799326 | Boylan et al. | Sep 2004 | B2 |
6799327 | Reynolds et al. | Sep 2004 | B1 |
6850693 | Young et al. | Feb 2005 | B2 |
6859799 | Yuen | Feb 2005 | B1 |
7039935 | Knudson et al. | May 2006 | B2 |
7069576 | Knudson et al. | Jun 2006 | B1 |
7487529 | Orlick | Feb 2009 | B1 |
8006259 | Drake et al. | Aug 2011 | B2 |
20010029610 | Corvin et al. | Oct 2001 | A1 |
20010047298 | Moore et al. | Nov 2001 | A1 |
20010054181 | Corvin | Dec 2001 | A1 |
20020073424 | Ward et al. | Jun 2002 | A1 |
20020124255 | Reichardt et al. | Sep 2002 | A1 |
20030005445 | Schein et al. | Jan 2003 | A1 |
20030056219 | Reichardt et al. | Mar 2003 | A1 |
20030110495 | Bennington et al. | Jun 2003 | A1 |
20030110499 | Knudson et al. | Jun 2003 | A1 |
20030115599 | Bennington et al. | Jun 2003 | A1 |
20030115602 | Knee et al. | Jun 2003 | A1 |
20030163813 | Klosterman et al. | Aug 2003 | A1 |
20030164858 | Klosterman et al. | Sep 2003 | A1 |
20030188310 | Klosterman et al. | Oct 2003 | A1 |
20030188311 | Yuen et al. | Oct 2003 | A1 |
20030196201 | Schein et al. | Oct 2003 | A1 |
20030204847 | Ellis et al. | Oct 2003 | A1 |
20030208756 | Macrae et al. | Nov 2003 | A1 |
20040010806 | Yuen et al. | Jan 2004 | A1 |
20040045025 | Ward et al. | Mar 2004 | A1 |
20040107437 | Reichardt et al. | Jun 2004 | A1 |
20040168189 | Reynolds et al. | Aug 2004 | A1 |
20040194138 | Boylan et al. | Sep 2004 | A1 |
20040261098 | Macrae et al. | Dec 2004 | A1 |
20050010949 | Ward et al. | Jan 2005 | A1 |
20050028201 | Klosterman et al. | Feb 2005 | A1 |
20050125823 | McCoy et al. | Jun 2005 | A1 |
20050149964 | Thomas et al. | Jul 2005 | A1 |
20050155056 | Knee et al. | Jul 2005 | A1 |
20050216936 | Knudson et al. | Sep 2005 | A1 |
20050251824 | Thomas et al. | Nov 2005 | A1 |
20060156336 | Knudson et al. | Jul 2006 | A1 |
20060212894 | Knudson et al. | Sep 2006 | A1 |
20060277574 | Schein et al. | Dec 2006 | A1 |
20060288366 | Boylan et al. | Dec 2006 | A1 |
20070016926 | Ward et al. | Jan 2007 | A1 |
20070033613 | Ward et al. | Feb 2007 | A1 |
20070107010 | Jolna et al. | May 2007 | A1 |
20100125351 | Davydov | May 2010 | A1 |
Number | Date | Country | |
---|---|---|---|
20110131594 A1 | Jun 2011 | US |