The present invention relates generally to communications services, and more particularly, to methods, systems, and computer program products for implementing bandwidth control services.
Digital Subscriber Line (DSL) technology is a copper loop transmission technology that provides increased bandwidth in the last mile between communication service providers and the users of these services. DSL technology provides broadband speed over a conventional phone wire, which in turn, allows service providers to provide multimedia applications, e.g., video, VoIP, Internet, etc., to their customers over their existing outside plant infrastructure.
Various services (e.g., television services), however, typically consume large amounts of bandwidth on a DSL connection. When multiple services (e.g., television, video/music downloading, gaming, etc.) are simultaneously utilized for a single account (e.g., household), the overall quality of these services can be negatively impacted due to strain on the available bandwidth (e.g., transmission delays or dropped packets), resulting in loss of quality, such as reduced VoIP voice quality. Customers may have some rudimentary knowledge of these issues and attempt to troubleshoot by activating and deactivating various services. However, they may not be able to resolve the issues unless they are given specific information about the nature of the issues and suggested courses of action for correcting the issues, and even then the complexities associated with potential solutions may be overwhelming to the user/customer. Further, the customer may not have direct control over various aspects of resources or the network which could be used to resolve or minimize such problems, such as packet priority, or other session flow control parameters.
What is needed, therefore, is a way to automatically monitor the various services and/or communications sessions, determine when negative interference or impacts between them may occur, and to control aspects of one or more services and/or resources and/or the communications network such that appropriate quality levels are maintained for the various services/sessions/users.
Exemplary embodiments include a method for implementing bandwidth management services. The method includes assigning a quality of service preference to a device. The method also includes associating a service session with the device. The method further includes executing a control action for at least one other simultaneously occurring service session when a quality of service level of the service session differs from the quality of service preference by a specified degree. The control action is operable for producing and maintaining the quality of service preference.
Additional embodiments include a system for implementing bandwidth management services. The system includes a processor executing a bandwidth control application. The bandwidth management application performs a method. The method includes assigning a quality of service preference to a device. The method also includes associating a service session with the device. The method further includes executing a control action for at least one other simultaneously occurring service session when a quality of service level of the service session differs from the quality of service preference by a specified degree. The control action is operable for producing and maintaining the quality of service preference.
Further embodiments include a computer program product for implementing bandwidth management services. The computer program product includes instructions for implementing a method. The method includes assigning a quality of service preference to a device. The method also includes associating a service session with the device. The method further includes executing a control action for at least one other simultaneously occurring service session when a quality of service level of the service session differs from the quality of service preference by a specified degree. The control action is operable for producing and maintaining the quality of service preference.
Other systems, methods, and/or computer program products according to embodiments will be or become apparent to one with skill in the art upon review of the following drawings and detailed description. It is intended that all such additional systems, methods, and/or computer program products be included within this description, be within the scope of the present invention, and be protected by the accompanying claims.
Referring now to the drawings wherein like elements are numbered alike in the several FIGURES:
The detailed description explains the exemplary embodiments, together with advantages and features, by way of example with reference to the drawings.
In accordance with exemplary embodiments, bandwidth control services are provided, which include monitoring traffic and traffic types transiting a network connection, analyzing the traffic measurements, determining approximately when, and in what manner, simultaneously provided services (e.g., services provided over multiple simultaneous data sessions) are likely to interfere with, or otherwise impact each other, and to automatically adjust traffic policing or shaping or other control mechanisms in the network and/or to automatically adjust service parameters such as the level and timing of device/application requests or service/server responses or other service-related activity so as to correct the problem or avoid its occurrence, and further to automatically determine and implement the best coordinated combination of control via the above.
Turning now to
The server may be implemented using one or more processors operating in response to a computer program stored in a storage medium accessible by the server. The server may operate as a network server (e.g., a web server) to communicate with communications elements such as devices 118-124 and gateway 126. The server handles sending and receiving information to and from one or more communications elements and can perform associated tasks.
The server of host system 102 may also operate as an application server. The server executes one or more computer programs to implement the bandwidth control processes and related functions described herein. These one or more applications are referred to herein as a bandwidth control application 110. It will be understood that separate servers may be utilized to implement the network server functions and the application server functions.
The bandwidth control application 110 comprises a network policy controller/operating mode controller (NPC/OMC) 112 and a delta analysis engine (DAE) 114. Policies refer to rules that may be implemented via network elements (also referred to as ‘resources’), such as routers, switches, gateways, firewalls, border controllers, edge devices, access node points, etc. under the direction of NPC/OMC 112. Policies may also be implemented via a network application programming interface (API) or network system accessed via a definable interface.
Operating modes refer to operations including parameter and/or control settings that may be implemented via an application or device for handling, e.g., video, audio, data, or multimedia under the direction of NPC/OMC 112. NPC/OMC 112 receives and processes deltas from DAE 114, translates the deltas into policy or control updates, and transmits these policy/control updates to one or more of devices 118-124, either directly or via a network connection and session controller (NCSC) 128. DAE 114 receives measurements, consults with relevant databases (e.g., databases 132-136), and performs analysis to determine problem situations, select a suitable mix of control measures, and determine updates. These elements are described further herein.
As shown in the system of
In exemplary embodiments, storage device 106 stores a user preferences database 132, a user/device sensitivity database 134, a device/application modes and capabilities database 136, and other related data. User/device sensitivities database 134 stores data indicating the importance, or potential ramifications, of an item or event to a user or device. This may include the relative ability to leverage a particular control action or change in order to achieve a desired result, e.g., to achieve or preserve a particular quality level. For example, changing one parameter may have a larger effect than changing another parameter, thus the “sensitivity” associated with the first parameter is larger than that associated with the second parameter. Further, user/device sensitivities database 134 may store data affecting the desirability of exerting control via network policies versus device or application capabilities.
Device/application modes and capabilities database 136 may store specified needs, specified capabilities, associated operating parameter values/settings/ranges, associated limits, associated interface details, associated data formats, etc. For example, each of the devices may have associated service needs, such as minimum bandwidth requirements. For some devices, such as a personal computer, there may be different minimum bandwidth requirements depending upon the application utilized for a given session (e.g., video conferencing, music or file downloading, etc.). Device/application modes and capabilities database 136 may also store error conditions, compatibility data, and settings including parameter values that are determined to be useful in avoiding specified issues or problems. In an exemplary embodiment, the server of host system 102 operates as a database server and coordinates access to application data including data stored within the storage device 106.
Network 108 may be any type of known network including, but not limited to, a Local Area Network (LAN), a Wide Area Network (WAN), a global network (e.g., Internet), or other network configuration known in the art. These networks may be implemented using a wireless network or may be physically connected to each other in a state of the art configuration. Further, the network 108 may include wireless connections, radio based communications, telephony based communications, optical communications, and other network-based communications. If the network 108 is a LAN, then the bandwidth control application 110 and CSM 116 may reside within the customer premise 104.
Customer premises 104 may comprise, e.g., a residential entity or business establishment. Customer premises 104 include various devices that utilize DSL services provided by a service provider (e.g., host system 102) via one or more pathways (e.g., 125). These devices, in turn, may communicate with one another via, e.g., a local area network (LAN) implemented within customer premises 104. The network of customer premises 104 may be wireline, wireless, or a combination thereof. Devices residing in customer premises 104 may include, e.g., one or more computer systems (e.g., device 122), one or more televisions (e.g., devices 118 and 124), one or more personal video recorders (PVRs) (e.g., PVR 120), one or more telephony devices (not shown), and one or more applications (e.g., video chat, file download, video conferencing, interactive gaming, multi-media applications, etc.) executing on the aforementioned devices, to name a few.
Computer system 122 may comprise a personal computer, laptop, or other similar type of processing device. Computer system 122 may implement a variety of network-enabled applications, such as Internet gaming, interactive applications, video chat, graphical/pictorial applications, encryption tools, interactive multi-media applications, multi-media content, etc. In accordance with exemplary embodiments, computer system 122 utilizes a user control interface (UCI) 130 provided by the bandwidth control application 110, as will be described further herein. Television devices 118 and 124 may include a standard broadcast, cable, and/or premium channel-viewing device. Television devices 118 and 124 may also comprise network elements that support, e.g., Web TV. In addition, television devices 118 and 124 may include peripheral components, such as a set top box, remote control, personal video recorder (PVR) 120, or other suitable elements. It will be understood that any of these components may provide computing functions or operations. Telephony devices may comprise a wireline telephone, a cellular telephone, or other suitable voice communications device. Further, telephony devices may implement multi-media applications such as video/text messaging and related functions.
Customer premises 104 also includes a gateway, e.g., residential gateway (RG) 126 that may serve as a DSL modem and, optionally, a routing device to allow one or more of devices 118-124 to communicate via a DSL interface. The residential gateway 126 may also be used to provide a firewall to inhibit viruses from affecting the devices in the customer premises 104. In exemplary embodiments, the residential gateway 126 includes the network connection and session controller (NCSC) 128. In alternative exemplary embodiments, the NCSC 128 may reside in network 108, e.g., in a switch/router or access controller. NCSC 128 controls, limits and/or shapes traffic for each separate session present on a connection at the customer premises 104.
The residential gateway 126 of customer premises 104 communicates with network 108 via, e.g., a digital subscriber line access multiplexor (DSLAM) (not shown). The DSLAM concentrates traffic from multiple DSL loops onto a backbone network, which is part of the network 108. The DSLAM may, in some embodiments, operate on packets, frames, and/or messages passing therethrough. For example, to support dynamic IP address assignment, the DSLAM may inspect the IP address of packets to direct the packets to their proper destination.
It will be understood that one or more of the elements described with respect to customer premise 104 (e.g., 118-128) may perform the functions of ‘resources’ when tasked by the bandwidth control application 110 to implement a control action, as will be described further herein.
Also residing in the network 108 is connection and session monitor (CSM) 116, which is in the path of the network connection that supports the customer premises 104, in order to be able to perform bandwidth usage measurements and/or other traffic measurements relevant to the customer or user. For example, the CSM 116 may be running in a router or access concentrator of the network 108. The CSM 116 monitors bandwidth usage for customer premises 104.
The CSM 116 and NCSC 128 form a comprehensive monitoring and control system. For illustrative purposes, two monitoring/control devices 116 and 128 are shown in the system of
Turning now to
At step 204, device data is obtained and analyzed in order to determine the sensitivities and/or capabilities of the devices (e.g., 118-124) at customer premises 104. This information may be stored in databases 134 and 136, respectively. The device data may be acquired via, for example, the UCI 130, or may be determined by polling, queries, etc. For example, the bandwidth control application 110 may query devices and/or applications associated with a user. The polling, or querying, may occur continuously, periodically, randomly, as needed (e.g., triggered by an event such as a user logging in or signing off of a device or application), or conditionally (e.g., when pre-configured data is not found).
While the bandwidth control services are described herein with reference to end-user devices and service sessions, it will be understood that the functionality of the bandwidth control services may also be applied to servers, equipment, resources, etc., of a provider of the communication sessions. The operations of the servers, equipment, resources, etc., may be controlled via the bandwidth control application 110 in a manner similar to that described above with respect to the end user devices and sessions of customer premises 104.
At step 206, the CSM 116 monitors the connection at customer premises 104, including individual, simultaneously occurring sessions therein (e.g., one active PC 122 and related applications, one high definition TV 118, etc.). The CSM 116 monitors, for example, bandwidths, throughput, delay/latency, percent utilization, errors, etc. This information is provided to the DAE 114, e.g., on a periodic basis or continuous basis.
The DAE 114 consults with one or more databases 132-136 to determine previous policy settings and operating mode settings (i.e., current state information) at step 208. The DAE 114 analyzes the measurements to determine the desired state (e.g., a quality of service level specified in the preferences) and whether there exist any differences between, e.g., specified aspects of the current state and the desired state at step 210. The differences, or deltas, may be weighted based upon user and/or device/application sensitivities derived from database 134, current conditions, allowable contingencies, limits, rules/tables, etc., and evaluated with respect to the desirability of implementing a policy change (also referred to as control action) versus implementing a operating mode change (also referred to as control action). These deltas are then provided to the NPC/OMC 112.
The NPC/OMC 112 converts the deltas into policy changes or control actions, operating mode changes or control actions, or a combination of both at step 212. This may be implemented via mapping the deltas to desired policies or operating modes using pre-defined rules or tables. The NPC/OMC 112 then selects an appropriate policy and/or operating mode resource at step 214. The selected policy and/or operating mode changes are then provided to the selected resource controller for implementation at step 216. For example, the selected changes may be transmitted to NCSC 128 via CSM 116 and network 108.
The receiving controller (e.g., NCSC 128) executes the changes in accordance with the selected policy and/or operating mode at step 218. The NCSC 128 may be prompted to verify the success of the implemented change at step 220, and provide notification of said success to the NPC/OMC 112 via CSM 116 and network 108 at step 222.
Optionally, the change may be logged in storage device 106 (e.g., in one or more of databases 132-136) at step 224. Changes may be logged at a customer premises (e.g., 104) for use by a local device or application. A user of one or more devices 118-124 may be notified of the change that has been implemented via one of devices 118-124 or other suitable means of communication at step 226.
Turning now to
DEVICE option 302 includes a drop down field for selecting from a pre-defined list of devices (e.g., TVs, computers, cell phones, etc.) residing in the customer premises 104. In alternative embodiments, the user may be presented with a field for manual entry of a device. DEVICE option 302 enables a user to individually select quality settings based upon policies and/or operating modes for each device in customer premises 104. The priorities may be implemented using a numerical system (e.g., priority 1 is highest to priority 10 lowest). The user would then assign priorities for each device in the customer premises 104. To ensure that a device assigned a high priority achieves optimal quality of service levels, a policy may be defined, for example, that specifies that the device is to be allocated the highest acceptable bandwidth as compared to other simultaneously operating devices in the premises 104. The policies applied to each of the established priority levels may be defined commensurate with the nature of the applicable device and/or application. Operating mode settings may be selected for the devices via option 302 as well.
The quality priorities may be assigned based upon the type of user of the devices. This is implemented via the USER option 304. For example, a user-based priority for policy-based control may specify that activities conducted on devices assigned to one or more users at customer premises 104 are to be given a lower priority. The devices may be assigned to users by a user identification, a device location (e.g., PC in teenager's bedroom), or other suitable means of association. Likewise, operating modes may be selected for each user via option 304 as well.
The quality priorities may also be assigned based upon the type of service executing on the devices. This is implemented via the SERVICE option 306. For example, a service-based priority may specify that voice traffic for all devices (or users) be given a higher priority than web browsing. In another example, a priority may specify that video traffic for all devices (or users) be given a higher priority than any other application. These services may be ranked in order of priority among multiple devices and/or users. These policy-based priority assignments may result in a greater allocation of bandwidth to high-priority services.
In addition to assigning quality priorities according to device, user, and service, the bandwidth control application 110 may enable a user to prioritize quality controls within each category. For example, as shown in user interface screen 300, a user has selected the SERVICE option 306 and has further selected a policy-based assignment rather than an operating mode-based assignment. A subwindow 308 appears. The user has made policy-based assignments based upon services, namely audio=1, video=2, and data=3. Within each service category, the user may further establish policy-based priority assignments. Thus, as shown in the subwindow 308, for example, the user has selected OFCPC (office computer) to receive a higher priority than BDRM1TV. In addition, BDRM1TV has been selected to receive a higher priority than BDRM2TV.
A user may also select settings that further define quality priority assignments via the LIMITS option 309. For example, a user may specify that video traffic on OFCPC shall not exceed 80% of connection bandwidth and web browsing shall not exceed 10% of connection bandwidth. In another example, a user may specify that data traffic on a device shall not exceed 20% of connection bandwidth when video is present; otherwise, the data traffic shall not exceed 60% of connection bandwidth. In yet another example, a user may specify that specified traffic shall be implemented on a first come first serve basis, e.g., where devices have equal priority.
Policy changes or updates to existing devices or services may be designated by a user or may be automatically implemented by the bandwidth control application 110 as needed. If designated by a user, these changes may be entered via POLICY UPDATES option 310. For example, a policy update may specify that quality of service shall be increased or decreased by, e.g., a number of units. Alternatively, a policy update may specify that a bandwidth limit shall be increased or decreased by a percentage of the total bandwidth or by a number of Mbps, etc.
Likewise, operating mode changes or updates to existing devices or services may be designated by a user or may be automatically implemented by the bandwidth control application 110 as needed. If designated by a user, these changes may be entered via OPERATING MODE UPDATES option 312. For example, an operating mode update may specify that a compression ratio shall be made higher or lower. In another example, an operating mode update may specify that a parameter be changed, e.g., immediately, or at a selected rate until a condition is met or event is reached. In yet another example, an operating mode update may specify that a device or application be turned off or on, or to a particular state (e.g., standby, dormant) until a condition is met or trigger occurs. In addition, an operating mode may specify a change in time in which a service is provided. For example, a user of PVR 120 wishes to record a program, however, the current state of bandwidth utilization is high due to other sessions implemented by various resources. An operating mode may specify a later time in which to record the program (e.g., via a lower priority established for PVR 120), thereby limiting or controlling the bandwidth utilization for the connection.
In exemplary embodiments, the bandwidth control application 110 may include a training model or learning algorithm for each customer premises such that customer preferences may be implied by the bandwidth control application 110 based upon customer history and patterns. The bandwidth control application 110 may record information regarding typical customer usage patterns, translate this information into a situational description (e.g., via rule selection and parameter settings), and periodically update this information.
As indicated above, the bandwidth control services monitor customer traffic in terms of bandwidth and/or other communications characteristics or aspects, analyze the traffic measurements, determine approximately when, and in what manner, simultaneously provided services (e.g., services provided over multiple simultaneous data sessions) are likely to interfere with or otherwise impact each other, and to automatically adjust traffic policing or shaping or other control mechanisms in the network and/or to automatically adjust device and/or service provider-related and/or service parameters such as the level and timing of device/application requests or service/server responses or other service-related activity so as to correct the problem or avoid its occurrence, and further to automatically determine and implement the best coordinated combination of control via the above.
In exemplary embodiments, user preferences may be established presenting the user with an available fixed quantity of graphical objects or icons, each of which represents an amount of traffic capacity, the number of objects increasing or decreasing according to the capacity of the data connection. The user may then place a desired number of “bandwidth objects” into an area on the user interface screen representing a specific device or session, or general type of session (e.g., video, telephony, music downloading). In this way, the user is provided with a visual indication of the relative capacity assignments. Other methods may also be used, including, for example, adjusting the segments of a pie chart.
As described above, the exemplary embodiments can be implemented in the form of computer-implemented processes and apparatuses for practicing those processes. The exemplary embodiments can also be implemented in the form of computer program code containing instructions embodied in tangible media, such as floppy diskettes, CD ROMs, hard drives, or any other computer-readable storage medium, wherein, when the computer program code is loaded into and executed by a computer, the computer becomes an apparatus for practicing the embodiments. Exemplary embodiments can also be implemented in the form of computer program code, for example, whether stored in a storage medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, loaded into and/or executed by a computer, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the computer program code is loaded into an executed by a computer, the computer becomes an apparatus for practicing the embodiments. When implemented on a general-purpose microprocessor, the computer program code segments configure the microprocessor to create specific logic circuits.
While the invention has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the scope of the invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the essential scope thereof. Therefore, it is intended that the invention not be limited to the particular embodiments disclosed for carrying out this invention, but that the invention will include all embodiments falling within the scope of the claims. Moreover, the use of the terms first, second, etc. do not denote any order or importance, but rather the terms first, second, etc. are used to distinguish one element from another. Furthermore, the use of the terms a, an, etc. do not denote a limitation of quantity, but rather denote the presence of at least one of the referenced item.
This application claims priority to U.S. Provisional Application No. 60/667,018, filed on Mar. 31, 2005. This application is related to commonly assigned U.S. patent application Ser. No. 11/304,264, entitled METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR PROVIDING TRAFFIC CONTROL SERVICES, filed on Dec. 14, 2005. These applications are incorporated by reference herein in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
4017676 | Rabeler et al. | Apr 1977 | A |
4380687 | Stewart | Apr 1983 | A |
4439784 | Furukawa et al. | Mar 1984 | A |
4769697 | Gilley et al. | Sep 1988 | A |
4802022 | Harada | Jan 1989 | A |
4903130 | Kitagawa et al. | Feb 1990 | A |
4907079 | Turner et al. | Mar 1990 | A |
5255180 | Shinoda et al. | Oct 1993 | A |
5278654 | Yang | Jan 1994 | A |
5313282 | Hayashi | May 1994 | A |
5331354 | Koyama et al. | Jul 1994 | A |
5731764 | Tanaka | Mar 1998 | A |
5793409 | Tetsumura | Aug 1998 | A |
5844600 | Kerr | Dec 1998 | A |
5874986 | Gibbon et al. | Feb 1999 | A |
5892856 | Cooper et al. | Apr 1999 | A |
5892859 | Grote | Apr 1999 | A |
5995153 | Moeller et al. | Nov 1999 | A |
6014694 | Aharoni et al. | Jan 2000 | A |
6025869 | Stas et al. | Feb 2000 | A |
6052734 | Ito et al. | Apr 2000 | A |
6057872 | Candelore | May 2000 | A |
6078589 | Kuechler | Jun 2000 | A |
6147992 | Giroir et al. | Nov 2000 | A |
6177931 | Alexander et al. | Jan 2001 | B1 |
6216956 | Ehlers et al. | Apr 2001 | B1 |
6237022 | Bruck | May 2001 | B1 |
6240460 | Mitsutake et al. | May 2001 | B1 |
6260111 | Craig et al. | Jul 2001 | B1 |
6315668 | Metke et al. | Nov 2001 | B1 |
6324182 | Burns | Nov 2001 | B1 |
6400687 | Davison et al. | Jun 2002 | B1 |
6480753 | Calder et al. | Nov 2002 | B1 |
6591423 | Campbell | Jul 2003 | B1 |
6594826 | Rao et al. | Jul 2003 | B1 |
6609253 | Swix et al. | Aug 2003 | B1 |
6631118 | Jones | Oct 2003 | B1 |
6647411 | Towell | Nov 2003 | B2 |
6717507 | Bayley et al. | Apr 2004 | B1 |
6741563 | Packer | May 2004 | B2 |
6757796 | Hofmann | Jun 2004 | B1 |
6771661 | Chawla et al. | Aug 2004 | B1 |
6796787 | Okada | Sep 2004 | B2 |
6810528 | Chatani | Oct 2004 | B1 |
6816903 | Rakoshitz et al. | Nov 2004 | B1 |
6839052 | Kramer | Jan 2005 | B1 |
6870463 | Dresti et al. | Mar 2005 | B2 |
6889382 | Anderson | May 2005 | B1 |
6961341 | Krishnan | Nov 2005 | B1 |
6973066 | Gutowski | Dec 2005 | B2 |
7000246 | Takao | Feb 2006 | B1 |
7065586 | Ruttenberg et al. | Jun 2006 | B2 |
7151939 | Sheynblat | Dec 2006 | B2 |
7277894 | Kondo et al. | Oct 2007 | B2 |
7284201 | Cohen-Solal | Oct 2007 | B2 |
7437073 | Kim et al. | Oct 2008 | B2 |
7512650 | Richardson | Mar 2009 | B2 |
7519703 | Stuart et al. | Apr 2009 | B1 |
20010031633 | Tuomela et al. | Oct 2001 | A1 |
20010043571 | Jang et al. | Nov 2001 | A1 |
20020002708 | Arye | Jan 2002 | A1 |
20020018645 | Nakamatsu et al. | Feb 2002 | A1 |
20020046099 | Frengut et al. | Apr 2002 | A1 |
20020080721 | Tobagi et al. | Jun 2002 | A1 |
20020083443 | Eldering et al. | Jun 2002 | A1 |
20020104087 | Schaffer et al. | Aug 2002 | A1 |
20020108127 | Lew | Aug 2002 | A1 |
20020133830 | Kim et al. | Sep 2002 | A1 |
20020144259 | Gutta et al. | Oct 2002 | A1 |
20020164987 | Caronni et al. | Nov 2002 | A1 |
20020178440 | Agnihotri et al. | Nov 2002 | A1 |
20020194586 | Gutta et al. | Dec 2002 | A1 |
20030002642 | Jorasch et al. | Jan 2003 | A1 |
20030002862 | Rodriguez et al. | Jan 2003 | A1 |
20030004743 | Callegari | Jan 2003 | A1 |
20030028872 | Milovanovic et al. | Feb 2003 | A1 |
20030046704 | Laksono et al. | Mar 2003 | A1 |
20030061619 | Giammaressi | Mar 2003 | A1 |
20030067554 | Klarfeld et al. | Apr 2003 | A1 |
20030088878 | Rogers et al. | May 2003 | A1 |
20030118029 | Maher et al. | Jun 2003 | A1 |
20030135544 | Richardson | Jul 2003 | A1 |
20030154242 | Hayes et al. | Aug 2003 | A1 |
20030154246 | Ollikainen | Aug 2003 | A1 |
20030236745 | Hartsell et al. | Dec 2003 | A1 |
20040009761 | Money et al. | Jan 2004 | A1 |
20040013119 | MeLampy et al. | Jan 2004 | A1 |
20040071085 | Shaham et al. | Apr 2004 | A1 |
20040078814 | Allen | Apr 2004 | A1 |
20040125757 | Mela et al. | Jul 2004 | A1 |
20040183749 | Vertegaal | Sep 2004 | A1 |
20040221304 | Sparrell et al. | Nov 2004 | A1 |
20040226034 | Kaczowka et al. | Nov 2004 | A1 |
20040255336 | Logan et al. | Dec 2004 | A1 |
20040264563 | Inoue et al. | Dec 2004 | A1 |
20040266407 | Lee et al. | Dec 2004 | A1 |
20040268407 | Sparrell et al. | Dec 2004 | A1 |
20040268410 | Barton et al. | Dec 2004 | A1 |
20050002662 | Arpa et al. | Jan 2005 | A1 |
20050007965 | Hagen et al. | Jan 2005 | A1 |
20050022239 | Meuleman | Jan 2005 | A1 |
20050024543 | Ramaswamy et al. | Feb 2005 | A1 |
20050039219 | Cooper et al. | Feb 2005 | A1 |
20050066026 | Chen et al. | Mar 2005 | A1 |
20050081252 | Chefalas et al. | Apr 2005 | A1 |
20050097595 | Lipsanen et al. | May 2005 | A1 |
20050108328 | Berkeland et al. | May 2005 | A1 |
20050120113 | Bunch et al. | Jun 2005 | A1 |
20050144640 | Fritsch et al. | Jun 2005 | A1 |
20050183110 | Anderson | Aug 2005 | A1 |
20050266825 | Clayton | Dec 2005 | A1 |
20060013266 | Vega-Garcia et al. | Jan 2006 | A1 |
20060025151 | Karaoguz et al. | Feb 2006 | A1 |
20060028185 | Hernandez et al. | Feb 2006 | A1 |
20060056389 | Monk et al. | Mar 2006 | A1 |
20060095398 | Bhaskaran | May 2006 | A1 |
20060114360 | Kortum et al. | Jun 2006 | A1 |
20060125959 | Yoshizawa et al. | Jun 2006 | A1 |
20060174266 | Gatto et al. | Aug 2006 | A1 |
20060179466 | Pearson et al. | Aug 2006 | A1 |
20060184780 | Yamada et al. | Aug 2006 | A1 |
20060195866 | Thukral | Aug 2006 | A1 |
20060204214 | Shah et al. | Sep 2006 | A1 |
20060221826 | Bedingfield, Sr. et al. | Oct 2006 | A1 |
20060222015 | Kafka et al. | Oct 2006 | A1 |
20060222110 | Kuhtz | Oct 2006 | A1 |
20060225106 | Bedingfield, Sr. | Oct 2006 | A1 |
20060251116 | Bedingfield, Sr. et al. | Nov 2006 | A1 |
20070133603 | Weaver et al. | Jun 2007 | A1 |
20070136772 | Weaver et al. | Jun 2007 | A1 |
20070169142 | Claassen et al. | Jul 2007 | A1 |
Number | Date | Country |
---|---|---|
WO03058478 | Jul 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20060222008 A1 | Oct 2006 | US |
Number | Date | Country | |
---|---|---|---|
60667018 | Mar 2005 | US |