1. Field of the Invention
The present invention relates to optical-fiber-based communication systems and networks, and particularly to systems and methods of deploying and maintaining optical fiber networks using radio-frequency identification (RFID) systems and methods.
2. Technical Background
Optical Networks
The typical optical fiber network (OFN) includes one or more central offices (COs), one or more remote nodes (RNs) connected to the COs by corresponding optical fiber links, a number of network interface devices (NIDs) coupled to respective RNs by corresponding optical fiber links, and a number of termination points coupled to the NIDs by additional optical fiber links. There are a number of different types of OFNs. One general type of OFN is called an active point-to-point architecture, which includes the Home Run Fiber (HRF) and Active Star Ethernet (ASE). Another general type of OFN is called a passive point-to-multipoint architecture, which includes the Passive Optical Network (PON). A PON has no active components between the CO and the termination location to which the service is delivered. Because of the different termination options for an OFN, for simplicity the abbreviated expression “fiber to the x” (FTTx) has been adopted, wherein the “x” represents the particular termination point. The termination point may be, for example, a “premise,” a home, the “curb,” or a “node.” Thus, in the acronym-intensive language of OFNs, a PON architecture used to provide service to one or more homes is abbreviated as FTTH-PON. The details of the particular FTTx network architecture used depends on the termination point and the service goals of the network, as well as on network cost and the existing optical fiber related infrastructure (“outside plant” or OSP). The deployment and maintenance of an OFN is an equipment-intensive and labor-intensive undertaking. A network service provider that receives the various components for the network from one or more manufacturers typically installs an OFN. The various OFN components (e.g., cabinets, terminals, enclosures, patch panel ports, optical fiber cable, optical fiber cable connectors, hardware, equipment, etc.) must be received, installed, inventoried, and maintained in an organized manner.
In OFN deployment, there is the need to positively identify and characterize the OFN components. This applies to the cabling (aerial or buried) as well as to the other aforementioned OFN components. Currently this process is carried out by visual identification, using foot markers printed on outside cable jackets, and color-coding and labeling of connectors, ports, enclosures, etc. During the initial installation as well as during operations and maintenance, significant time is spent associating the various OFN components and their characteristics to an inventory database, which is updated manually. Besides the extra time spent, there is a high risk of errors due to misidentification, database entry errors or failures to correctly update the database.
An OFN is typically deployed over a relatively large geographical area, with the optical fiber cables and other ONF components being installed either below ground or above ground. Thus, the ability to quickly locate and identify the various network components and obtain information about their installation and operating status can provide significant labor and cost savings with regard to deploying and maintaining the OFN, and can increase OFN uptime.
Radio-Frequency Identification
Radio-frequency identification (RFID) is a remote recognition technique that utilizes RFID tags having microcircuits adapted to store information and perform basic signal processing. The stored information is retrievable via RF communication between the RFID tag and a RFID tag reader. The typical RFID system utilizes a RFID tag reader (e.g., hand-held) that when brought sufficiently close to a RFID tag is able to read a RFID tag signal emitted by the tag, usually in response to an interrogation signal from the RFID tag reader. One form of RFID tag relies on the interrogation signal from the RFID reader to provide power to the tag. Other forms of RFID tags have internal power sources.
The data encoded into a RFID tag can generally be written at a distance, and some types of RFID tags can be re-written multiple times. Each RFID application has its own unique issues and circumstances that require the RFID system to be engineered accordingly.
In view of the above-described issues associated with the deployment and maintenance of OFNs and the benefits of RFID technology, there is a need for systems and methods that integrate RFID technology with OFNs to facilitate OFN deployment and maintenance.
One aspect of the invention is a RFID method of deploying and/or maintaining an OFN. The method includes providing at least one RFID tag on at least one OFN component of a plurality of OFN components that constitute the OFN. The method also includes writing, to at least one RFID tag, data relating to at least one property of the corresponding OFN component. The method further includes recording and storing the OFN component data in an OFN-component-data database unit.
Another aspect of the invention is a RFID system for deploying and/or maintaining an OFN. The system includes at least one RFID tag affixed to at least one OFN component of a plurality of OFN components that constitute the OFN, wherein the at least one RFID tag affixed to the at least one OFN component contains OFN component data that relates to at least one property of the OFN component. The system also includes at least one RFID tag reader adapted to read the OFN component data from the at least one RFID tag. The system further includes an OFN component data database unit adapted to receive and store OFN component data read by the at least one RFID tag reader.
Another aspect of the invention is a RFID system for deploying and/or maintaining an optical fiber network (OFN) that is optically coupled to a central office (CO). The system includes at least one feeder-cable RFID tag fixed to a feeder cable that is optically coupled to the CO, with the at least one feeder-cable RFID tag having feeder-cable data relating to one or more properties of the feeder cable. The system also includes at least one local convergence point (LCP) RFID tag fixed to a local convergence point (LCP) that is operably connected to the feeder cable, with the at least one LCP RFID tag having LCP data relating to one or more properties of the LCP. The system further includes at least one distribution-cable RFID tag fixed to a distribution cable that is operably coupled to the LCP, with the at least one distribution-cable RFID tag having distribution-cable data relating to one or more properties of the distribution cable. The system also includes at least one network access point (NAP) RFID tag fixed to a NAP that is operably coupled to the LCP via the distribution cable, with the at least one NAP RFID tag having NAP data relating to one or more properties of the NAP. The system additionally includes at least one network interface device (NID) RFID tag fixed to a NID that is operably coupled to the LCP via a drop cable, with the at least one NAP RFID tag having NID data relating to one or more properties of the NID. The system further includes one or more RFID tag readers adapted to read at least one of the feeder-cable RFID tags, the LCP RFID tags, the distribution-cable RFID tags, the NAP RFID tags, and the NID RFID tags, and provide corresponding feeder-cable data, LCP data, distribution-cable data, NAP data, and NID data. The system also includes an OFN component database unit adapted to receive and store the feeder-cable data, the LCP data, the distribution-cable data, the NAP data and the NID data.
Additional features and advantages of the invention will be set forth in the following detailed description, and in part will be readily apparent to those skilled in the art from that description or recognized by practicing the invention as described herein, including the following detailed description, the claims, as well as the appended drawings.
It is to be understood that both the foregoing general description and the following detailed description present embodiments of the invention, and are intended to provide an overview or framework for understanding the nature and character of the invention as it is claimed. The accompanying drawings are included to provide a further understanding of the invention, and are incorporated into and constitute a part of this specification. The drawings illustrate various embodiments of the invention, and together with the description serve to explain the principles and operations of the invention.
Reference is now made to the present preferred embodiments of the invention, examples of which is/are illustrated in the accompanying drawings. Whenever possible, the same reference numbers or letters are used throughout the drawings to refer to the same or like parts.
The term “OFN component” as used herein is generally any component used in any type of OFN, and includes but is not limited to: a feeder cable, a distribution cable, a drop cable, a network access point (NAP), an enclosure, a splice box, a cabinet, a terminal, a patch panel, a patch cord, a fiber connector, an optical splitter, a splitter module, a coupler, an optical amplifier, a wavelength multiplexer, a wavelength demultiplexer, an optical line terminal, a filter, a light source, an optical receiver, an optical transmitter, an intrafacility cable, a local convergence point (LCP), a network interface device (NID), a fiber distribution frame (FDF), an equipment module, or any other OFN-related hardware, including fiber-related hardware.
In the discussion below, the term “data” is used in the singular and represents a collection of one or more pieces of information. The term “RFID tag data” refers to data stored in or to be stored in a RFID tag, which data contains at least one property of the corresponding OFN component associated with the RFID tag.
Also, the term “electromagnetic signals” as used to describe the signals communicated between a RFID tag and a RFID reader includes free-space radio waves as well as magnetic inductive coupling.
For the sake of convenience, the following is a list of the acronyms used in this application:
OFN=optical fiber network
CO=central office
RFID=radio-frequency identification.
PON=passive optical network.
FTTx=“fiber-to-the-x,” where “x” is the fiber cable endpoint.
LCP=local convergence point
NAP=network access point
NID=network interface device
GPS=global positioning system
OLT=optical line terminal
OSP=outside plant
GUI=graphical user interface
FDF=fiber distribution frame
dB=decibels
The OFN-RFID System
With reference to
With reference again to
OFN 10 also includes one or more distribution cables 110 operably coupled to a given LCP 100, with each distribution cable including one or more optical fibers 112. Note that feeder cable(s) 50 and distribution cable(s) 110 may be either buried or supported above ground.
With reference again to
With reference again to
RFID Tags in OFN-RFID System
With continuing reference to
Microcircuit 450 is adapted to receive an electromagnetic RFID-tag interrogation signal SI″ emitted by RFID reader via antenna 480 and to process this signal. The processing includes comparing the received interrogation signal SI″ to a corresponding bit sequence stored value in memory unit 452. In an example embodiment, microcircuit 450 is adapted to use the energy in the interrogation signal to power itself. If the content of the received interrogation signal SI″ is confirmed, then microcircuit 450 is adapted to generate a RFID tag signal STn representative of the stored RFID tag data and to transmit this signal to RFID reader 400 as an electromagnetic tag signal STn″ to be read by RFID tag reader 400.
In an example embodiment, one or more of the RFID tags are adapted to generate electromagnetic RFID tag signals at a frequency that is not significantly affected by soil or water, such as in the frequency range from 100 KHz to 125 KHz. This is so that the RFID tag signal can be read even though the corresponding OFN component is buried underground or covered by water. Here, the electromagnetic RFID tag signals are based on magnetic inductive coupling. Suitable RFID tags and associated RFID tag readers are available from 3M Corporation.
Also in an example embodiment, at least some of the RFID tags are adapted to generate RFID tag signals at a frequency suitable for long-range RFID-tag reading, such at the 915 MHz band or the 2.45 GHz band. Such RFID tags are best suited for aerial or aboveground OFN components, or more generally for OFN components that are not buried or otherwise obstructed by an intervening RF-frequency-absorbing medium. Suitable RFID tags are available from Alien Technologies, Inc., as Model Nos. ALL-9440 and ALL-9350.
In an example embodiment, RFID tag reader 400 and one or more of RFID tags Tn are adapted with encryption capability so that the interrogation signal and the RFID tag signal can be encrypted to prevent third parties from reading or overwriting RFID tag data.
Example RFID Tag Reader
With continuing reference to
Signal processing circuit 482 is adapted to generate interrogation signal SI and transmit it via antenna 480 to RFID tag Tn as an electromagnetic interrogation signal SI″. Signal processing circuit 482 is also adapted to write information to RFID tag Tn based on information either stored in memory unit 484, entered into the RFID tag reader directly by a user, or communicated to it from database unit 410, as described below.
RFID tag reader 400 is also adapted to receive electromagnetic RFID tag signal STn″ via antenna 480, which converts this signal back to electrical RFID tag signal STn. Signal processing circuit 482 is further adapted to extract the RFID tag data from this signal and store this data in memory unit 484 and/or transmit this data to database unit 410.
Example Database Unit
In an example embodiment, RFID tag reader 400 is operably coupled to database unit 410 so that it can transmit information to and receive information from the database unit. In an example embodiment, database unit 410 includes a second transmit/receive antenna 494 used to wirelessly communicate with RFID tag reader 400, through a Wi-Fi network or through the cellular phone network, as examples. In another example embodiment, database unit 410 is operably coupled to RFID tag reader 400 via a non-wireless (e.g., an electrical or optical) communication link 492, such as an Ethernet link.
Database unit 410 includes a microprocessor 500 operably connected thereto, a memory unit 510 operably coupled to the microprocessor, and a display 520 operably coupled to the microprocessor. In an example embodiment, database unit 410 is or otherwise includes a computer, such as a laptop computer, personal computer or workstation. In an example embodiment, database unit 410 is mobile (e.g., as a laptop computer or hand-held device) and is brought out to the field so as to be accessible to those working in the field to deploy or maintain OFN 10. Also in an example embodiment, database unit 410 supports a graphical user interface (GUI) so that a database-unit user can view graphical images and interact with interactive graphical images on display 520.
In an example embodiment, RFID tag reader 400 transmits RFID tag data to database unit 410 either non-wirelessly via a non-wireless data signal SD sent over communication link 492, or wirelessly via electromagnetic data signal SD″. Database unit 410 then stores and processes the RFID tag data, such as described below.
Also in an example embodiment, database unit 410 either wirelessly and/or non-wirelessly transmits write information in respective information signals SW and/or (electromagnetic) signal SW″ to RFID tag reader 400. The write information in signals SW or SW″ is then written by RFID tag reader 400 to one or more RFID tags Tn and stored therein as RFID tag data.
Microprocessor 500 in database unit 410 is adapted to process the RFID tag data to create useful information about the status of OFN 10 and OFN components Cn. In an example embodiment, this information is displayed on display 520. In an example embodiment, the information is represented as graphics, and further is presented by database unit 410 in the form of one or more interactive OFN-RFID maps. The OFN-RFID maps may include, for example, component inventory data, component location data, component connectivity data and/or component status data. Example interactive OFN-RFID maps for facilitating the deployment and maintenance of OFN 10 are discussed in greater detail below.
CO RFID Tags
CO 20 also includes a patch-cord RFID tag T36 attached to patch cord 36 and a intrafacility-cable RFID tag T46. These RFID tags include, for example, information relating to the manufacturer, manufacturer part number, date of installation, the number of connections, type of fiber, etc.
CO 20 also includes an FDF RFID tag T30 attached to FDF 30 and a cabinet RFID tag T40 attached to entrance cabinet 40. These RFID tags include, for example, information relating to the manufacturer, manufacturer part number, date of installation, the number of connections, location of the frame or cabinet, etc.
Feeder Cable RFID Tags
With reference again also to
Feeder cable RFID tags T50 may also include information relating to the installation of feeder cables 50, such as the planned installation destination, installation date, special instructions regarding the installation (e.g., aerial or buried cable), and the like.
LCP RFID Tags
OFN-RFID system 6 also includes a number of LCP RFID tags. In an example embodiment, a main LCP RFID tag T100 is attached to the OSP distribution cabinet 120 and contains information relating to the general properties of LCP 100, such as the cabinet location, operational status of the LCP, manufacturer information, maintenance status, the number and type of internal OFN components, etc. A splitter-module LCP RFID tag T130 is attached to splitter module 130.
In an example embodiment, RFID tag T130 includes a light 560 (e.g., a light-emitting diode (LED)) that activates when the particular RFID tag T130 is interrogated by RFID tag reader 400. This helps identify which one of the RFID tags T130 is being interrogated and read at a given time.
Table 1 below presents an example embodiment of RFID tag data stored in the splitter-module RFID tag T130 for splitter module ID#124290. For the sake of illustration, only the data for the first six ports P1-through P6 is shown.
Table 1 includes the shelf ID number—here, ID number 124290 chosen for illustration purposes—that identifies the splitter-module RFID tag as being located in a particular shelf of splitter module rack 554. Table 1 includes the following information for each port: The 1310 nm loss (dB), the 1550 nm loss (dB), the street name served by the port, the street address served by the port, the pole number associated with the port, the GPS coordinates of the location served by the port, and “other information” that can be added to the RFID tag as needed, such as the operating status or the maintenance status. Generally speaking, data can also be written to the RFID tag via RFID reader 400 so that the data can be updated as needed. In an example embodiment, RFID tags T130 contain default deployment data written to the RFID tag prior to the deployment of LCP 100 or the installation of splitter module 130 in the LCP.
In another example embodiment illustrated in
Table 2 includes the patch-panel ID number—here, ID number 13425, chosen for illustration purposes. Table 2 also includes the patch-panel port number P1 through P6, the loss per port (in dB), and the OSP location information. Other information, such as building name, room number, subscriber location, street address, power levels, maintenance schedules, and the like can be included in Table 2. Alternately, it is possible to have a separate RFID tag, with one for each port number P1 through P6, that contains all of the data pertinent to its associated port.
Here, it is emphasized that the prior art approach to OFN deployment and maintenance involves obtaining such information by inspection and previous written documentation, and then documenting the updated information on paper. The paper documents are then distributed to provide information about the maintenance history of OFN components Cn such as splitter module 130 and patch panel 140. With RFID tags, this paper documentation is replaced by the data written into the RFID tags, and is available instantly at the point of use and at any time it is needed.
Distribution-Cable RFID Tags
With reference again to
Distribution-cable RFID tags T110 may also include information relating to the installation of distribution cables 110, such as the planned installation destination, installation date, special instructions regarding the installation (e.g., aerial or buried cable), and the like.
NAP RFID Tags
OFN-RFID system 6 also includes a number of NAP RFID tags. A main NAP RFID tag T200 is attached to the distribution cabinet 120 and contains information relating to the general properties of NAP 200, such as the cabinet location, operational status of the NAP, manufacturer information, maintenance status, the number and type of internal OFN components, etc.
The other NAP RFID tags for NAP 200 are essentially the same as those for LCP 100 since the NAP typically includes the same OFN components—namely, splitter module(s) 130 and patch panel(s) 140.
Drop-Cable RFID Tags
With reference to
Drop-cable RFID tags T220 may also include information relating to the installation of drop cables 220, such as the planned installation destination, installation date, special instructions regarding the installation (e.g., aerial or buried cable), and the like.
MD RFID Tags
OFN-RFID system 6 also includes a number of NID RFID tags. A main MD RFID tag T300 is attached to cabinet 120 and contains information relating to the general properties of NID 300, such as the cabinet location, operational status of the MD, manufacturer information, maintenance status, the number and type of internal OFN components, etc.
Other NID RFID tags are provided to the corresponding NID OFN components in analogous fashion to the LCP RFID tags described above. In an example embodiment, the other NID RFID tags are essentially the same as those for LCP 100 in the case where the two have the same or similar OFN components.
RFID Mapping of the OFN
As discussed above, an example embodiment of the present invention involves using OFN RFID tags Tn to create one or more OFN-RFID maps of OFN 10 based on the RFID tag data read from the OFN RFID tags. In one example embodiment, OFN RFID tags Tn are provided with data relating to the deployment of the corresponding OFN components Cn prior to OFN 10 being deployed. In one example, the OFN RFID tag data is written to the corresponding RFID tags by the OFN component manufacturer and/or by the OFN installer (service provider). For example, for cable assemblies that are factory terminated and customized for installation in a particular location, the location information can also be written in the RFID tags. RFID tags on the cable reel or cable assembly reel can also contain information about their installation destination, as required.
The OFN RFID tag data is then read from the OFN RFID tags using RFID tag reader 400 prior to or during deployment. In an example embodiment, the service provider receives materials from the OFN component supplier and scans all tagged OFN components. This information is then added to the inventory database unit of database unit 410. At this point, the service provider may choose to replace the manufacturer identification and the identification number written to the RFID tag by the manufacturer with its own identification number, which uniquely identifies this tag within its entire inventory of assets. The original identification number and the manufacturer code can be stored in the inventory database unit so that each entity can still be traced back if necessary. This enables the full capability and capacity of the manufacturing database collection to be searched to determine the characteristics and performance of the component in more detail than can be written into the RFID tag. Such manufacturing data can be retrieved remotely, for example, via the Internet or via a cellular phone network. This information can be further updated at the time of installation, to add additional details of interest to the network operator, such as the association between ports and connectors.
The OFN RFID tag data, which is collected in memory unit 510 of database unit 410, is processed via microprocessor 500 to provide a representation of the OFN RFID tag information from the various OFN RFID tags, such as an OFN map.
In an example embodiment, the information stored in the OFN RFID tags Tn includes positional information (e.g., GPS coordinates) for the OFN components Cn. The positional information is, for example, originally provided by GPS circuit 486 and written to the OFN RFID tags Tn by RFID tag reader 400 during installation of the OFN component. Writing of GPS information can be carried out, for example, by OFN service personnel working in the field while installing, maintaining or repairing the OFN. For example, the GPS information can also be added to the RFID tag data by RFID tag reader 400 during the RFID tag reading process after OFN deployment (e.g., by OFN service personnel) and sent to the database unit along with the read RFID tag data. This allows the map to show in detail the precise locations of the OFN components, as well as the spatial relationships between OFN components in the OFN.
In a similar manner, an OFN inventory map is created that shows the location (e.g., via GPS coordinates) and the corresponding part number for each OFN component Cn in OFN 10. In an example embodiment, the OFN inventory map includes information about not only installed OFN components, but spare OFN components as well, such as availability, location, etc.
In another example embodiment, an OFN maintenance map of OFN 10 is created by writing to one or more of the OFN RFID tags Tn maintenance information for the corresponding OFN components Cn. The maintenance map includes, for example, maintenance that needs to be performed and/or maintenance that has already been performed. By updating OFN RFID tags Tn using one or more RFID tag readers 400 and transmitting the updated OFN RFID tag information from the one or more RFID tag readers to database unit 410, an updated maintenance map is established. Such an updated maintenance map can be viewed on display 520 of database unit 410 and used to plan and schedule OFN maintenance.
In an example embodiment, both inventory and maintenance maps are used in combination when performing OFN maintenance, since inventory issues often arise in connection with performing OFN maintenance.
Each of the RFID tags Tn in interactive map 750 are active icons that can be clicked on to display the corresponding RFID tag data. For example, clicking on RFID tag T130 displays Table 1 as shown and discussed above in connection with splitter module 130. Likewise, clicking on RFID tag T140 displays Table 2 as shown and discussed above in connection with patch panel 140. Interactive map 750 also includes a general LCP RFID tag T120 icon that can be clicked on to display general RFID tag data generally concerning the corresponding LCP 100.
As discussed above, in an example embodiment, database unit 410 is portable, allowing it to be taken into the field by those deploying or maintaining OFN 10. This provides for real-time processing of OFN deployment and maintenance RFID tag data during the deployment or maintenance activity.
The automated tracking of OFN components afforded by the present invention reduces the risk of misidentification and errors that often accompany manual updates of an OFN component inventory database. The present invention also provides for faster and more accurate installation, provisioning operations, fault location and maintenance of the OFN.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit and scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents.
Number | Name | Date | Kind |
---|---|---|---|
3052842 | Frohman et al. | Sep 1962 | A |
3609742 | Burdick | Sep 1971 | A |
3771098 | Dempsey | Nov 1973 | A |
3931574 | Curtis, Jr. et al. | Jan 1976 | A |
3942859 | Korodi | Mar 1976 | A |
4019128 | Chebowski | Apr 1977 | A |
4200862 | Campbell et al. | Apr 1980 | A |
4365238 | Kollin | Dec 1982 | A |
4418333 | Schwarzbach et al. | Nov 1983 | A |
4578636 | Bakke et al. | Mar 1986 | A |
4626633 | Ruehl et al. | Dec 1986 | A |
4630886 | Lauriello et al. | Dec 1986 | A |
4889977 | Haydon | Dec 1989 | A |
4915639 | Cohn et al. | Apr 1990 | A |
4924213 | Decho et al. | May 1990 | A |
4937529 | O'Toole, III et al. | Jun 1990 | A |
4968929 | Hauck et al. | Nov 1990 | A |
4978317 | Pocrass | Dec 1990 | A |
5081627 | Yu | Jan 1992 | A |
5185570 | Fitzpatrick | Feb 1993 | A |
5199093 | Longhurst | Mar 1993 | A |
5222164 | Bass, Sr. et al. | Jun 1993 | A |
5244409 | Guss, III et al. | Sep 1993 | A |
5265187 | Morin et al. | Nov 1993 | A |
5297015 | Miyazaki et al. | Mar 1994 | A |
5305405 | Emmons et al. | Apr 1994 | A |
5337400 | Morin et al. | Aug 1994 | A |
5353367 | Czosnowski et al. | Oct 1994 | A |
5394503 | Dietz, Jr. et al. | Feb 1995 | A |
5418334 | Williams | May 1995 | A |
5448675 | Leone et al. | Sep 1995 | A |
5461693 | Pimpinella | Oct 1995 | A |
5473715 | Schofield et al. | Dec 1995 | A |
5483467 | Krupka et al. | Jan 1996 | A |
5528222 | Moskowitz et al. | Jun 1996 | A |
5588873 | Hamai et al. | Dec 1996 | A |
5601451 | Driones et al. | Feb 1997 | A |
5613873 | Bell, Jr. | Mar 1997 | A |
5638818 | Diab et al. | Jun 1997 | A |
5645440 | Tobler et al. | Jul 1997 | A |
5660567 | Nierlich et al. | Aug 1997 | A |
5666453 | Dannenmann | Sep 1997 | A |
5685737 | Morin et al. | Nov 1997 | A |
5692925 | Bogese, II | Dec 1997 | A |
5700157 | Chung | Dec 1997 | A |
5704802 | Loudermilk | Jan 1998 | A |
5741152 | Boutros | Apr 1998 | A |
5764043 | Czosnowski et al. | Jun 1998 | A |
5782757 | Diab et al. | Jul 1998 | A |
5797767 | Schell | Aug 1998 | A |
5821510 | Cohen et al. | Oct 1998 | A |
5842045 | Nakamura | Nov 1998 | A |
5847557 | Fincher et al. | Dec 1998 | A |
5854824 | Bengal et al. | Dec 1998 | A |
5876239 | Morin et al. | Mar 1999 | A |
5876240 | Derstine et al. | Mar 1999 | A |
5885100 | Talend et al. | Mar 1999 | A |
5910776 | Black | Jun 1999 | A |
5914862 | Ferguson et al. | Jun 1999 | A |
5915993 | Belopolsky et al. | Jun 1999 | A |
5924889 | Wang | Jul 1999 | A |
5934925 | Tobler et al. | Aug 1999 | A |
5984731 | Laity | Nov 1999 | A |
5995006 | Walsh | Nov 1999 | A |
5995855 | Kiani et al. | Nov 1999 | A |
5999400 | Belopolsky et al. | Dec 1999 | A |
6002331 | Laor | Dec 1999 | A |
6025725 | Gershenfeld et al. | Feb 2000 | A |
6068627 | Orszulak et al. | May 2000 | A |
6095851 | Laity et al. | Aug 2000 | A |
6095869 | Wang | Aug 2000 | A |
6100804 | Brady et al. | Aug 2000 | A |
6102741 | Boutros et al. | Aug 2000 | A |
6113422 | Somerville et al. | Sep 2000 | A |
6116946 | Lewis et al. | Sep 2000 | A |
6116962 | Laity | Sep 2000 | A |
6118379 | Kodukula et al. | Sep 2000 | A |
6120318 | Reed et al. | Sep 2000 | A |
6126610 | Rich et al. | Oct 2000 | A |
6127929 | Roz | Oct 2000 | A |
6133835 | De Leeuw et al. | Oct 2000 | A |
6142822 | Wu | Nov 2000 | A |
6152762 | Marshall et al. | Nov 2000 | A |
6164551 | Altwasser | Dec 2000 | A |
6174194 | Bleicher et al. | Jan 2001 | B1 |
6217371 | Wu | Apr 2001 | B1 |
6222908 | Bartolutti et al. | Apr 2001 | B1 |
6222975 | Gilbert et al. | Apr 2001 | B1 |
6224417 | Belopolsky et al. | May 2001 | B1 |
6227911 | Boutros et al. | May 2001 | B1 |
6232870 | Garber et al. | May 2001 | B1 |
6234830 | Ensz et al. | May 2001 | B1 |
6241550 | Laity et al. | Jun 2001 | B1 |
6243654 | Johnson et al. | Jun 2001 | B1 |
6256523 | Diab et al. | Jul 2001 | B1 |
6280213 | Tobler et al. | Aug 2001 | B1 |
6285293 | German et al. | Sep 2001 | B1 |
6298255 | Cordero et al. | Oct 2001 | B1 |
6319051 | Chang et al. | Nov 2001 | B1 |
6319062 | Ma et al. | Nov 2001 | B1 |
6325664 | Someda et al. | Dec 2001 | B1 |
6330307 | Bloch et al. | Dec 2001 | B1 |
6349228 | Kiani et al. | Feb 2002 | B1 |
6350148 | Bartolutti et al. | Feb 2002 | B1 |
6352446 | Ezawa et al. | Mar 2002 | B2 |
6354884 | Yeh et al. | Mar 2002 | B1 |
6368155 | Bassler et al. | Apr 2002 | B1 |
6375362 | Heiles et al. | Apr 2002 | B1 |
6377203 | Doany | Apr 2002 | B1 |
6378111 | Brenner et al. | Apr 2002 | B1 |
6402743 | Orszulak et al. | Jun 2002 | B1 |
6409530 | Zhao et al. | Jun 2002 | B1 |
6424263 | Lee et al. | Jul 2002 | B1 |
6424315 | Glenn et al. | Jul 2002 | B1 |
6424710 | Bartolutti et al. | Jul 2002 | B1 |
6428361 | Imschweiler et al. | Aug 2002 | B1 |
6431906 | Belopolsky | Aug 2002 | B1 |
6439922 | Laurer et al. | Aug 2002 | B1 |
6456768 | Boncek et al. | Sep 2002 | B1 |
6457993 | Espenshade | Oct 2002 | B1 |
6464533 | Ma et al. | Oct 2002 | B1 |
6469404 | Pohjola | Oct 2002 | B1 |
6478610 | Zhou et al. | Nov 2002 | B1 |
6478611 | Hyland | Nov 2002 | B1 |
6496113 | Lee et al. | Dec 2002 | B2 |
6496382 | Ferguson et al. | Dec 2002 | B1 |
6499861 | German et al. | Dec 2002 | B1 |
6522308 | Mathieu | Feb 2003 | B1 |
6522737 | Bartolutti et al. | Feb 2003 | B1 |
6541756 | Schulz et al. | Apr 2003 | B2 |
6543940 | Chu | Apr 2003 | B2 |
6556761 | Jennings et al. | Apr 2003 | B1 |
6574586 | David et al. | Jun 2003 | B1 |
6577243 | Dannenmann et al. | Jun 2003 | B1 |
6580086 | Schulz et al. | Jun 2003 | B1 |
6618022 | Harvey | Sep 2003 | B2 |
6655988 | Simmons et al. | Dec 2003 | B1 |
6663417 | Hung | Dec 2003 | B1 |
6684179 | David | Jan 2004 | B1 |
6685701 | Orszulak et al. | Feb 2004 | B2 |
6688908 | Wallace | Feb 2004 | B2 |
6688910 | Macauley | Feb 2004 | B1 |
6693513 | Tuttle | Feb 2004 | B2 |
6696952 | Zirbes | Feb 2004 | B2 |
6725177 | David et al. | Apr 2004 | B2 |
6729910 | Fuller | May 2004 | B2 |
6733186 | Pfleger | May 2004 | B2 |
6750643 | Hwang et al. | Jun 2004 | B2 |
6773298 | Gutierrez et al. | Aug 2004 | B2 |
6773306 | Plishner | Aug 2004 | B2 |
6784802 | Stanescu | Aug 2004 | B1 |
6798956 | Morrison | Sep 2004 | B2 |
6808116 | Eslambolchi et al. | Oct 2004 | B1 |
6829427 | Becker | Dec 2004 | B1 |
6831443 | Liu | Dec 2004 | B2 |
6846115 | Shang et al. | Jan 2005 | B1 |
6847856 | Bohannon | Jan 2005 | B1 |
6857897 | Conn | Feb 2005 | B2 |
6866424 | Tanaka et al. | Mar 2005 | B2 |
6871156 | Wallace et al. | Mar 2005 | B2 |
6881096 | Brown et al. | Apr 2005 | B2 |
6888996 | Hwang et al. | May 2005 | B2 |
6890197 | Liebenow | May 2005 | B2 |
6896542 | Chang | May 2005 | B2 |
6898368 | Colombo et al. | May 2005 | B2 |
6900629 | Hwang et al. | May 2005 | B2 |
6902433 | Hashimoto et al. | Jun 2005 | B1 |
6910917 | Chen | Jun 2005 | B2 |
6913481 | Marshall et al. | Jul 2005 | B2 |
6915050 | Koyasu et al. | Jul 2005 | B2 |
6917763 | Au et al. | Jul 2005 | B1 |
6921284 | Sirichai et al. | Jul 2005 | B2 |
6923689 | Xue et al. | Aug 2005 | B2 |
6924997 | Chen et al. | Aug 2005 | B2 |
6961675 | David | Nov 2005 | B2 |
6968994 | Smith | Nov 2005 | B1 |
6971895 | Sago et al. | Dec 2005 | B2 |
6973243 | Koyasu et al. | Dec 2005 | B2 |
6975242 | Dannenmann et al. | Dec 2005 | B2 |
6979223 | Chen | Dec 2005 | B2 |
6999028 | Egbert | Feb 2006 | B2 |
7014100 | Zierolf | Mar 2006 | B2 |
7014500 | Belesimo | Mar 2006 | B2 |
7016726 | Picardo et al. | Mar 2006 | B1 |
7018242 | Brown et al. | Mar 2006 | B2 |
7024089 | Weinert et al. | Apr 2006 | B2 |
7027704 | Frohlich et al. | Apr 2006 | B2 |
7028087 | Caveney | Apr 2006 | B2 |
7028202 | Long et al. | Apr 2006 | B2 |
7038135 | Chan et al. | May 2006 | B1 |
7044949 | Orszulak et al. | May 2006 | B2 |
7046899 | Colombo et al. | May 2006 | B2 |
7062139 | Shang | Jun 2006 | B2 |
7068912 | Becker | Jun 2006 | B1 |
7069345 | Shteyn | Jun 2006 | B2 |
7080945 | Colombo et al. | Jul 2006 | B2 |
7081808 | Colombo et al. | Jul 2006 | B2 |
7096077 | Price et al. | Aug 2006 | B2 |
7102520 | Liu et al. | Sep 2006 | B2 |
7123810 | Parrish | Oct 2006 | B2 |
7132641 | Schulz et al. | Nov 2006 | B2 |
7140782 | Frohlich et al. | Nov 2006 | B2 |
7151455 | Lindsay et al. | Dec 2006 | B2 |
7158031 | Tuttle | Jan 2007 | B2 |
7158033 | Forster | Jan 2007 | B2 |
7160143 | David et al. | Jan 2007 | B2 |
7165728 | Durrant et al. | Jan 2007 | B2 |
7168975 | Kuo | Jan 2007 | B2 |
7170393 | Martin | Jan 2007 | B2 |
7173345 | Brandt et al. | Feb 2007 | B2 |
7193422 | Velleca et al. | Mar 2007 | B2 |
7194180 | Becker | Mar 2007 | B2 |
7205898 | Dixon et al. | Apr 2007 | B2 |
7207846 | Caveney et al. | Apr 2007 | B2 |
7210858 | Sago et al | May 2007 | B2 |
7217152 | Xin et al. | May 2007 | B1 |
7221277 | Caron et al. | May 2007 | B2 |
7221284 | Scherer et al. | May 2007 | B2 |
7224278 | Phaneuf et al. | May 2007 | B2 |
7224280 | Ferguson et al. | May 2007 | B2 |
7226217 | Benton et al. | Jun 2007 | B1 |
7233250 | Forster | Jun 2007 | B2 |
7234944 | Nordin et al. | Jun 2007 | B2 |
7243837 | Durrant et al. | Jul 2007 | B2 |
7247046 | Wu | Jul 2007 | B1 |
7252538 | Garrett et al. | Aug 2007 | B2 |
7253735 | Gengel et al. | Aug 2007 | B2 |
7265674 | Tuttle | Sep 2007 | B2 |
7275970 | Hoshina | Oct 2007 | B2 |
7285007 | Barna | Oct 2007 | B2 |
7294786 | Aldereguia et al. | Nov 2007 | B2 |
7297018 | Caveney et al. | Nov 2007 | B2 |
7297028 | Daikuhara et al. | Nov 2007 | B2 |
7298266 | Forster | Nov 2007 | B2 |
7298330 | Forster | Nov 2007 | B2 |
7298946 | Mueller | Nov 2007 | B2 |
7306489 | Werthman et al. | Dec 2007 | B2 |
7307408 | Porcu et al. | Dec 2007 | B2 |
7318744 | Kuo | Jan 2008 | B2 |
7319397 | Chung et al. | Jan 2008 | B2 |
7327278 | Dannenmann et al. | Feb 2008 | B2 |
7336883 | Scholtz | Feb 2008 | B2 |
7349605 | Noonan et al. | Mar 2008 | B2 |
7352285 | Sakama et al. | Apr 2008 | B2 |
7352289 | Harris | Apr 2008 | B1 |
7354298 | James | Apr 2008 | B2 |
7356208 | Becker | Apr 2008 | B2 |
20010008390 | Berquist et al. | Jul 2001 | A1 |
20010027055 | Laity et al. | Oct 2001 | A1 |
20010039140 | Fasold et al. | Nov 2001 | A1 |
20020071394 | Koziy et al. | Jun 2002 | A1 |
20020086584 | Liu | Jul 2002 | A1 |
20020090858 | Caveney | Jul 2002 | A1 |
20020092347 | Niekerk et al. | Jul 2002 | A1 |
20030021580 | Matthews | Jan 2003 | A1 |
20030061393 | Steegmans et al. | Mar 2003 | A1 |
20030100217 | Wu | May 2003 | A1 |
20030100218 | Tsai et al. | May 2003 | A1 |
20030148654 | Kan | Aug 2003 | A1 |
20030154273 | Caveney | Aug 2003 | A1 |
20030154276 | Caveney | Aug 2003 | A1 |
20030162414 | Schulz et al. | Aug 2003 | A1 |
20030211782 | Esparaz et al. | Nov 2003 | A1 |
20040041714 | Forster | Mar 2004 | A1 |
20040114879 | Hiereth et al. | Jun 2004 | A1 |
20040117515 | Sago et al. | Jun 2004 | A1 |
20040123998 | Berglund et al. | Jul 2004 | A1 |
20040149736 | Clothier | Aug 2004 | A1 |
20040184747 | Koyasu et al. | Sep 2004 | A1 |
20040253874 | Plishner | Dec 2004 | A1 |
20050032415 | Sakamoto | Feb 2005 | A1 |
20050052174 | Angelo et al. | Mar 2005 | A1 |
20050052287 | Whitesmith et al. | Mar 2005 | A1 |
20050068179 | Roesner | Mar 2005 | A1 |
20050076982 | Metcalf et al. | Apr 2005 | A1 |
20050093677 | Forster et al. | May 2005 | A1 |
20050111491 | Caveney | May 2005 | A1 |
20050215119 | Kaneko | Sep 2005 | A1 |
20050224585 | Durrant et al. | Oct 2005 | A1 |
20050231325 | Durrant et al. | Oct 2005 | A1 |
20050232636 | Durrant et al. | Oct 2005 | A1 |
20050259930 | Elkins et al. | Nov 2005 | A1 |
20050260884 | Yueh | Nov 2005 | A1 |
20050280511 | Yokoyama et al. | Dec 2005 | A1 |
20060039136 | Probasco et al. | Feb 2006 | A1 |
20060044148 | Daniels et al. | Mar 2006 | A1 |
20060091207 | Chang | May 2006 | A1 |
20060148279 | German et al. | Jul 2006 | A1 |
20060153517 | Reagan et al. | Jul 2006 | A1 |
20060166546 | Ashizawa et al. | Jul 2006 | A1 |
20060206246 | Walker | Sep 2006 | A1 |
20060232419 | Tomioka et al. | Oct 2006 | A1 |
20060233506 | Noonan et al. | Oct 2006 | A1 |
20060257092 | Lu et al. | Nov 2006 | A1 |
20060267778 | Gengel et al. | Nov 2006 | A1 |
20060275007 | Livingston et al. | Dec 2006 | A1 |
20060282529 | Nordin | Dec 2006 | A1 |
20060286856 | Sakamoto | Dec 2006 | A1 |
20070013487 | Scholtz et al. | Jan 2007 | A1 |
20070015410 | Siemon et al. | Jan 2007 | A1 |
20070023525 | Son et al. | Feb 2007 | A1 |
20070032124 | Nordin et al. | Feb 2007 | A1 |
20070059975 | Walsh | Mar 2007 | A1 |
20070117450 | Truxes | May 2007 | A1 |
20070120684 | Utaka et al. | May 2007 | A1 |
20070152828 | Mohalik | Jul 2007 | A1 |
20070155223 | Huang et al. | Jul 2007 | A1 |
20070176745 | Gibson et al. | Aug 2007 | A1 |
20070196058 | Lee et al. | Aug 2007 | A1 |
20070205897 | Forster | Sep 2007 | A1 |
20070216534 | Ferguson et al. | Sep 2007 | A1 |
20070236355 | Flaster et al. | Oct 2007 | A1 |
20070238343 | Velleca et al. | Oct 2007 | A1 |
20070241439 | Chung et al. | Oct 2007 | A1 |
20070247284 | Martin et al. | Oct 2007 | A1 |
20080003867 | Wu | Jan 2008 | A1 |
20080021766 | McElwaine et al. | Jan 2008 | A1 |
20080032546 | Xuan et al. | Feb 2008 | A1 |
20080045075 | Caveney et al. | Feb 2008 | A1 |
20080090451 | Feldman | Apr 2008 | A1 |
20080100467 | Downie et al. | May 2008 | A1 |
20080106415 | Sellew et al. | May 2008 | A1 |
20080139306 | Lutnick et al. | Jun 2008 | A1 |
20080220721 | Downie et al. | Sep 2008 | A1 |
Number | Date | Country |
---|---|---|
19841738 | Mar 2000 | DE |
19920452 | Nov 2000 | DE |
102 44 304 | Mar 2004 | DE |
10249414 | May 2004 | DE |
10 2006 030 077 | Jan 2008 | DE |
1455550 | Aug 2004 | EP |
1 696 680 | Apr 2008 | EP |
2 347 508 | Sep 2000 | GB |
2371211 | Jul 2002 | GB |
03-242795 | Oct 1991 | JP |
04-039483 | Feb 1992 | JP |
04-174406 | Jun 1992 | JP |
2001-099946 | Apr 2001 | JP |
2002-264617 | Sep 2002 | JP |
2003-148653 | May 2003 | JP |
2003-172827 | Jun 2003 | JP |
2003-229215 | Aug 2003 | JP |
2004-039389 | Feb 2004 | JP |
2004-142500 | May 2004 | JP |
2004-152543 | May 2004 | JP |
2004-245963 | Sep 2004 | JP |
2004-247090 | Sep 2004 | JP |
2004-247134 | Sep 2004 | JP |
2004-264901 | Sep 2004 | JP |
2004-265624 | Sep 2004 | JP |
2004-265860 | Sep 2004 | JP |
2004-265861 | Sep 2004 | JP |
2004-2666886 | Sep 2004 | JP |
2004-317737 | Nov 2004 | JP |
2004-349184 | Dec 2004 | JP |
2005-018175 | Jan 2005 | JP |
2005-033857 | Feb 2005 | JP |
2005-050581 | Feb 2005 | JP |
2005-084162 | Mar 2005 | JP |
2005-086901 | Mar 2005 | JP |
2005-087135 | Apr 2005 | JP |
2005-092107 | Apr 2005 | JP |
2005-134125 | May 2005 | JP |
2005-216698 | Aug 2005 | JP |
2005-302403 | Oct 2005 | JP |
2005-315980 | Nov 2005 | JP |
2005-339983 | Dec 2005 | JP |
2006-054118 | Feb 2006 | JP |
2006-245983 | Sep 2006 | JP |
2006-279650 | Oct 2006 | JP |
2007-087849 | Apr 2007 | JP |
2007-088957 | Apr 2007 | JP |
2007-158993 | Jun 2007 | JP |
2007-189774 | Jul 2007 | JP |
2007-221400 | Aug 2007 | JP |
WO 03098175 | Nov 2003 | WO |
WO 2004030154 | Apr 2004 | WO |
WO20040615112 | Jul 2004 | WO |
WO 2005069203 | Jul 2005 | WO |
WO 2008000656 | Jan 2008 | WO |
2008076235 | Jun 2008 | WO |