1. Field of the Disclosure
The field of the disclosure relates to a sensor included in a component for sensing information relating to or surrounding the component location. The component can be attached to an article of manufacture and configured to be mated with a mating component. The component may include radio-frequency (RF) communication capability for communicating information, including the sensed information.
2. Technical Background
Conditions surrounding or proximate to articles of manufacture can be important for a number of reasons. One example of such an article of manufacture includes electrical and fiber optic-based equipment used for data transmission. It may be important that equipment operate according to desired performance guidelines. For example, if equipment is used to establish voice connections and transmit voice data, strict Quality of Service (QoS) requirements must be met. As an example, voice switching equipment may be required to meet a QoS rating of no more than two hours of failure for every forty years of use. However, conditions surrounding the equipment may negatively affect equipment performance. Examples of such conditions include temperature, pressure, and air flow. Other articles of manufacture may also have requirements relating to performance that can be affected by surrounding conditions.
In this regard, sensors may be employed in areas in and around the articles of manufacture to detect conditions that can affect performance. The sensed condition information may then be reported. For example, the sensed condition information may be environmental and/or physical information. The sensed condition information may be used to alert service personnel when remedial measures are required to either reduce the risk of equipment failure or when equipment has failed for repair dispatch. The condition information may also be used to automatically shut down equipment operation and re-route data transmission. Further, monitoring and reporting of security-based conditions may also be desired to detect potential disturbances of equipment that may negatively affect desired operation. The condition information detected by the sensors can also be reported to surveillance systems, including both on-site and remote systems.
Although a sensor may detect and report surrounding conditions, the location of the sensor may be unknown and thus the location of the sensed information is unknown. If the sensor is attached to an article of manufacture, the sensed condition information may also not be able to be associated with a particular location when reported. The article of manufacture may be portable or removable. Further, conditions that can affect performance may be localized to a particular component of equipment rather than to the equipment as a whole. For example, a malfunctioning circuit or wire in one component of the equipment may be detected as an increase in temperature. The malfunctioning circuit or wire may be localized to a particular fixed component of the equipment, such as a socket or adapter. Further, a removable component, such as a plug or connector, connected to the fixed component may have the malfunction as opposed to the fixed component. In either case, the sensor may detect and report data indicative of conditions in a general area in which the malfunction is located. However, the location of the sensed information may not be precisely mapped to the malfunctioning component.
Embodiments disclosed in the detailed description include components having one or more sensors adapted to sense and provide localized sensor data. Having the ability to localize sensor data to a specific location rather than generalized areas or locations can assist in quickly pinpointing areas where performance or other condition issues may exist in components and equipment associated with components. In this regard, the components disclosed herein are adapted to communicate with a mating component. Sensor data from the one or more sensors can be associated with identity information of the mating component. The identity information of the mating component can be used to determine the location of the mating component, whether a fixed location or a relative location to another component or particular equipment. In this manner, the sensor data can be associated with the location of the mating component in a “component-to-component” configuration to provide location-specific sensor data. The components may be associated with any type of article of manufacture desired, including but not limited to equipment, including electrical and/or fiber optic equipment.
In certain disclosed embodiments, the component includes an integrated circuit (IC). The IC may be provided in the form of an IC chip. The component also includes one or more electrical leads coupled to the IC. One or more sensors are provided and adapted to communicate sensor data regarding environmental and/or physical conditions or information relating to and/or in proximity to the component. The IC is configured to communicate with a mating component when the one or more electrical leads are coupled to one or more electrical leads provided in the mating component. When connected, the communication between the component and the mating component allows the identity information of the component, the mating component, or both to be associated with the sensor data. In this manner, the identity information can be used to associate a specific location to the sensor data to provide location-specific sensor data. The specific location may be to a resolution down to centimeters (cm) scale as an example. The association of the sensor data with a location can be performed by the component or mating component, or a communication system coupled to the components, including a radio-frequency (RF) identification (RFID) reader and/or component management system.
In certain embodiments, the IC is configured to communicate the sensor data over the one or more electrical leads to the mating component to associate the sensor data with the identity information of the component, the mating component, or both. In other embodiments, the IC is configured to receive the identity information of the mating component over the one or more electrical leads to associate the sensor data with the identity information of the mating component. In other embodiments, the IC is RFID-enabled and is coupled to an antenna to provide an RFID transponder. The information provided to the RFID transponder, including the sensor data, identity information, and any information received from the mating component, can be communicated to an RFID reader via RF communications. The RFID transponder may be an active, semi-passive, or passive device. Passive RFID transponder devices may be desired when providing a power supply is not desired or otherwise impractical due to cost or size limitations. Passive RFID devices can be powered by an interrogation signal transmitted by an RFID reader. RFID-enabled components are not required.
The components disclosed herein are adapted to associate sensor data with identity information of a component to provide location-specific sensor data. The components disclosed herein can be any type of component and for any type of article of manufacture, including equipment. For example, the component may be used to establish a connection with equipment. Examples include electrical or fiber optic components, an electrical plug or fiber optic connector, or an electrical socket or fiber optic adapter. The equipment adapted to be coupled or connected to the components can be any type of equipment, including but not limited to electrical and fiber optic equipment. The equipment or articles of manufacture can be located in equipment housings or racks and in range of RFID readers and associated systems.
The embodiments for associating location with sensor data to provide location-specific sensor data can be applied to any collection of articles that are physically arranged in close proximity with each other. Examples include, but are not limited to, RFID tags associated with electrical or optical network equipment, utility equipment and systems, power distribution systems, modular building structures that are mated together during construction, including but not limited to flooring, roofing, walls, and any other type of interconnection systems. Additional features and advantages of the embodiments will be set forth in the detailed description which follows, and in part will be readily apparent to those skilled in the art from that description or recognized by practicing the embodiments as described herein, including the detailed description that follows, 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, and are intended to provide an overview or framework for understanding the nature and character of the embodiments. The accompanying drawings are included to provide a further understanding of the embodiments, and are incorporated into and constitute a part of this specification. The drawings illustrate various embodiments of the embodiments and together with the description serve to explain the principles and operation of the embodiments.
Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings, in which some, but not all embodiments are shown. Indeed, the embodiments may be embodied in many different forms and should not be construed as limiting herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Whenever possible, like reference numbers will be used to refer to like components or parts.
Embodiments disclosed in the detailed description include components having one or more sensors adapted to sense and provide localized sensor data. Having the ability to localize sensor data to a specific location rather than generalized areas or locations can assist in quickly pinpointing areas where performance or other condition issues may exist in components and equipment associated with components. In this regard, the components disclosed herein are adapted to communicate with a mating component. Sensor data from the one or more sensors can be associated with identity information of the mating component. The identity information of the mating component can be used to determine the location of the mating component, whether a fixed location or a relative location to another component or particular equipment. In this manner, the sensor data can be associated with the location of the mating component in a “component-to-component” configuration to provide location-specific sensor data. The specific location may be to a resolution down to centimeters (cm) scale as an example. The association of the sensor data with a location can be performed by the component or mating component, or a communication system coupled to the components, including a radio-frequency (RF) identification (RFID) reader and/or component management system. The components may be associated with any type of article of manufacture desired, including but not limited to equipment, including electrical and/or fiber optic equipment.
As further illustrated in
Both the component 12(1) and mating component 12(2) are contained in respective component housings 30(1), 30(2). The component housings 30(1), 30(2) may be attached to or comprise articles of manufacture, equipment, or other components. The component housing 30(1) of the component 12(1) includes the sensor 28 and an integrated circuit (IC) in the form of an IC chip 32(1). The mating component 12(2) also contains an IC chip 32(2) in the component housing 30(2). The IC chips 32(1), 32(2) provide circuitry for enabling certain functionality and communication with each other as well as other systems or devices. In this embodiment, the IC chip 32(1) in the component 12(1) is also coupled to the sensor 28 to receive sensor data regarding the component 12(1) and/or the surrounding area. The IC chips 32(1), 32(2) may be entirely or partially located in the components 12(1), 12(2).
The IC chips 32(1), 32(2) may or may not be RFID-enabled. In this embodiment, the IC chips 32(1), 32(2) are RFID-enabled and may be referred to generally as IC chips or as an “RFID chip,” “RFID-enabled chip,” or “RFID-enabled IC chip.” The RFID-enabled IC chips 32(1), 32(2) include respective associated RFID transponder circuitry which is coupled to respective antennas 34(1), 34(2) to provide RFID transponders 18(1), 18(2). As used herein, the term “RFID transponder” includes at least an RFID-enabled IC and an antenna. The RFID transponders 18(1), 18(2) allow for RF communications including to the RFID reader 20. The RFID transponders 18(1), 18(2) may employ passive, semi-passive, or active RFID-enabled IC chips 32(1), 32(2), and may be designed to respond and/or communicate at the frequency desired via respective antennas 34(1), 34(2). In this embodiment, the RFID transponders 18(1), 18(2) are passive devices. Passive RFID devices do not require their own power source. Power can be harvested from an interrogation signal 24 transmitted by the RFID reader 20 in the RFID reader system 22 and received by the antennas 34(1), 34(2). Thus, passive RFID devices may be desired when providing a power supply is not desired or otherwise impractical due to cost or size limitations. The antennas 34(1), 34(2) may be any type of antenna that is tuned to the desired reception and/or transmission frequency(s), including but not limited to a dipole and monopole antenna. The antennas 34(1), 34(2) can be external to or integrated in the IC chips 32(1), 32(2). In this embodiment, the sensor 28 can also be external to or integrated in the IC chip 32(1) or the component 12(1).
Also in this embodiment, both the component 12(1) and mating component 12(2) contain one or more electrical leads each coupled to their respective IC chips 32(1), 32(2). When the electrical leads 36(1), 36(2) come into electrical contact with each other as a result of a connection, a connection event occurs. In response, the IC chips 32(1), 32(2) of the components 12(1), 12(2), respectively, initiate communications with each other over the electrical leads 36(1), 36(2). Identity information regarding the identity of the component 12(1) and mating component 12(2) stored in memory 38(1), 38(2) provided in the IC chips 32(1), 32(2) of the RFID transponders 18(1), 18(2) can be exchanged and stored to signify the connection of the component 12(1) with the mating component 12(2). Either or both the component 12(1) and the mating component 12(2) can also communicate their own identity information as well as exchanged identity information with the other component 12(2), 12(1), respectively, to the RFID reader 20. The components 12(1), 12(2) may communicate other information stored in memory, such as serial number, type of connector, cable type, manufacturer, manufacturing date, installation date, location, lot number, performance parameters (such as attenuation measured during installation), identification of what is at other end of the cable, etc. Such information could be preloaded on the memory 38(1), 38(2) of the RFID transponders 18(1), 18(2) at manufacture or upon installation via the RFID reader 20.
The RFID reader system 22 coupled to the RFID reader 20 receives identity information pairs signifying component(s) 12(1) mated to mating component(s) 12(2) within the range of the RFID reader 20 and processes the information in a component management system 26. The component management system 26 may include control systems and related software for processing the information received from the components 12 to perform a number of tasks. These tasks include, but are not limited to, recording the identity information pairs, providing identity information pairs information to a technician, recording which components 12 are not mated, and providing other troubleshooting and diagnostic information, as will be described in greater detail below. Furthermore, the component management system 26, and any associated database and/or processing element, includes stored information relating to one or more RFID transponders 18(1), 18(2) in order to facilitate identification, mapping, or other processing of the information received from one or more RFID transponders 18(1), 18(2). More specifically, the RFID reader 20 includes information that correlates a unique identification number of an RFID transponder 18 to a particular component 12, to other portions of the component 12, to past and/or current mating components 12, and to any other parameter, connection, association, or other information that a technician may want to know or record when working with and/or monitoring the one or more components 12.
In this embodiment, the component 12(1) can also exchange and/or communicate the sensor data from the sensor 28 to the mating component 12(2) and/or the RFID reader 20. The component 12(1) can communicate the sensor data to the RFID reader 20 in response to a poll via the interrogation signal 24 generated and received by the antennas 34(1), 34(2). If the sensor data is communicated to the mating component 12(2), the mating component 12(2) could also communicate the sensor data to the RFID reader 20. In either case, the sensor data can be associated with the identity information of the component 12(1) and the mating component 12(2) when connected. If the location of the mating component 12(2) is known, the location of the sensor 28 is known and thus the location relevant to the sensor data. In this manner, the sensor data will be location-specific sensor data. Thus, the location can be more specific to a narrower area range than the read range of the RFID reader 20, for example down to centimeter (cm) scale resolution. In this manner, the sensor data can be associated precisely to a particular component 12 rather than a general area, which may have a number of components 12, and in some cases a high density of components 12. This identity information-to-location association may be performed within the mating component 12(2) itself if aware of its location, the RFID reader 20, the RFID reader system 22, and/or the component management system 26. Further, the components 12, the RFID reader 20, and/or the component management system 26 may determine if the sensor data exceeds programmed threshold level, and if so, generate an alarm or report. The alarm or report can include display information on displays associated with the components 12, as will be discussed in more detail below.
Even if the fixed location of the mating component 12(2) is not known, the relative location of the component 12(1) and mating component 12(2) will be known as being located together due to their mating. Thus, the embodiments disclosed herein allow for both fixed and relative location association with sensor data. Further, the embodiments disclosed herein allow for the location of the sensor data to be dynamically updated by detecting the mating of both removable and fixed components 12. Even if the component 12(1) is not connected with mating component 12(2), the component 12(1) can still communicate its identity information and the sensor data to the RFID reader 20. Also, the mating component 12(2), by only communicating its own identity information to the RFID reader 20, can provide an indication that a component 12(1) is not connected to the mating component 12(2), or that a component 12(1) connected to the mating component 12(2) is not capable of exchanging identity information.
As examples, the ability to associate a specific location to sensor data relating to a component 12 may be useful for a number of reasons and applications. For example, if the sensor data includes air flow and/or air temperature data, the sensor data can be used to determine if the air flow or temperature level surrounding a given component is sufficient to achieve desired performance and/or to prevent potential failures of components due to lack of air flow and overheating. As another example, the sensor data may include humidity level data indicative of whether the moisture level is too high for components 12 or articles of manufacture 14, which risks failures. If the sensor data includes movement data, human contact with components 12 can be detected when human contact may be forbidden. For example, the components 12 may connect links carrying highly sensitive data or information. If the sensor data includes impact data, damage or potential damage to fragile components 12 and articles of manufacture 14 may be detected so that testing and replacement of components 12 can be performed to avoid potential failures and/or reduce downtime attributed to failed components 12.
It may also be important to confirm that a component 12 is out-of-service before its removal by service personnel. The sensor data may also allow recording of timing associated with sensor data to show where certain environmental and/or physical data occurred for investigation reasons. Further, by tracking changes in location in regard to components 12, inventory of the components 12 can be tracked and maintained. Open slots within the articles of manufacture 14 can also be tracked by lack of identity information exchange with a mating component 12(2). As another example, the sensor 28 could detect velocity or acceleration to track the velocity or acceleration of moving components, such as disk drive components as an example, wherein the sensor data is associated with a specific location of a component 12. Other examples of sensors 28 that produce sensor data of interest and may be included in a component 12(1) or mating component 12(2) include, but are not limited to, voltage level sensors, current level sensors, pressure sensors, audible sensors, stress sensors, wavelength sensors, signal strength sensors, phase shift sensors, impedance sensors, shock sensors, input voltage standing wave ratio (VSWR) sensors, signal quality sensors, orientation sensors, light level (both ambient and optical fiber light levels) sensors, and contact sensors, including switches, and flow sensors for air or liquid flow, or both, etc. Sensors 28 may detect sensor data on installation, removal, re-installation, and/or operation of components 12. Any type of sensor 28 that can be integrated or coupled to a component 12 and provide sensor data can be employed.
To provide further detail regarding how RFID transponders 18(1), 18(2) may be communicatively coupled together by example,
Each IC chip 32(1), 32(2) contains RF inputs in the form of RF input pins 40(1), 40(2) configured to couple to an antenna 34(1), 34(2) (see
As further illustrated in
In this embodiment, the RFID-enabled IC chip 32(1) also contains a sense function that activates the IC chip 32(1) in response to an activation of sense pins 52, 54. Although not illustrated in
Also in this embodiment, the sensor 28 is coupled to the other sense pin 54 as part of the component 12(1). The sensor 28 is configured to provide sensor data to the IC chip 32(1) via the sense pin 54, which in turn causes the IC chip 32(1) to communicate with the IC chip 32(2). Activating the RFID-enabled IC chips 32(1), 32(2) also allows information to be provided to the RFID reader 20 in response to the interrogation signal 24. However, note that if the IC chips 32(1), 32(2) are connected together, an electrical connection between the IC chips 32(1), 32(2) is still made and information between the IC chips 32(1), 32(2) can be exchanged. In response to a condition change or activation, the RFID reader 20 may also communicate to the RFID transponder 18(2) to cause a light source 58, such as a light emitting diode (LED) or other light source coupled to an LED pin 59, to light up to indicate to the technician which mating component 12(2) to connect to the component 12(1). Other examples of light sources that may comprise the light source 58 include a liquid crystal display (LCD), and an electroluminescent display. The light source 58 may be powered by energy from the interrogation signal 24 transmitted by the RFID reader 20. A capacitor bank 60 may also be provided in the RFID transponder 18(2) to be charged during interrogation by the RFID reader 20 and to provide reserve power to the light source 58 when not being interrogated by the RFID reader 20 or when energy from the RFID reader 20 is sporadic or otherwise not strong enough to power the RFID transponder 18(2).
The remainder of this description and
In this regard,
Alternatively or in addition, the sensor data from the sensor 28 could be communicated over the electrical leads 36(1), 36(2) to the RFID transponder 18(1) in the component 12(1). The component 12(1) could then associate the received identity information of the mating component 12(2) with the received sensor data and communicates such to the RFID reader 20. This is because the RFID transponder 18(1) in the component 12(1) can communicate the sensor data via RF communications, as previously discussed. The sensor data can be associated with the component 12(1) and/or mating component 12(2) just as if the mating component 12(2) communicated the sensor data to the RFID reader 20. If the location of the mating component 12(2) is known, that location can be associated with the sensor data such that it becomes location-specific sensor data. Also, both the component 12(1) and mating component 12(2) could communicate their identity information along with exchanged identity information of the other and the sensor data to the RFID reader 20. In this manner, the RFID reader system 22 could determine if both the component 12(1) and mating component 12(2) communicated the same identity connectivity and sensor data as a redundancy check. If not the same, this may be an indication of a failure of the component 12(1), mating component 12(2), or both.
The sensor data can be associated with the component 12(1) and the mating component 12(2). If the location of the component 12(1) or mating component 12(2) is known, that location can be associated with the sensor data such that it becomes location-specific sensor data. Even if a component 12(1) is not connected to the mating component 12(2), the mating component 12(2) can still communicate its identity information and the sensor data to the RFID reader 20, in which case the sensor data can still be associated with the mating component 12(2). If the location of the mating component 12(2) is known, that location can be associated with the sensor data such that it becomes location-specific sensor data. All other functionalities and possibilities that exist for the component mating system 10(3) of
The sensor data can be associated with the component 12(1) and the mating component 12(2). If the location of the component 12(1) or mating component 12(2) is known, that location can be associated with the sensor data such that it becomes location-specific sensor data. Even if a mating component is not connected to component 12(1), the component 12(1) can still communicate its identity information and the sensor data to the RFID reader 20, in which case the sensor data can still be associated with the component 12(1). If the location of the component 12(1) is known, that location can be associated with the sensor data such that it becomes location-specific sensor data. All other functionalities and possibilities that exist for the component mating system 10(4) of
The display 72 may be activated manually such as in response to a switch coupled to the IC chip 32(1). An example is the switch 56 illustrated in
To further illustrate the ability of the component 12(1) to be activated by a switch, such as the switch 56 in
As soon as the component 12(1) is connected to the mating component 12(2), the sensor data from the sensor 28(1) can be communicated to the IC chip 32(2) of RFID transponder 18(2), in which case the sensor data can then be associated with the mating component 12(2). If the location of the mating component 12(2) is known, the location of the mating component 12(2) can be associated with the sensor data from both sensors 28(1), 28(2) such that the sensor data becomes location-specific for the mating component 12(2). Even if a component 12(1) is not connected to the mating component 12(2), the sensor data from sensor 28(2) can still be associated with the identity information of the mating component 12(2) and communicated to the RFID reader 20. Again, if the location of the mating component 12(2) is known, the location of the mating component 12(2) can be associated with the sensor data from the sensor 28(2) such that the sensor data becomes location-specific for the mating component 12(2). All other functionalities and possibilities that exist for the component mating system 10(4) of
Even if a component 12(1) is not connected to the mating component 12(2), the sensor data from the sensor 28 can still be associated with the identity information of the mating component 12(2) and communicated to the RFID reader 20. Again, if the location of the mating component 12(2) is known, the location of the mating component 12(2) can be associated with the sensor data from the sensor 28(2) such that the sensor data becomes location-specific for the mating component 12(2). All other functionalities and possibilities that exist for the component mating system 10(7) of
Providing an additional RFID transponder 18(3) can serve as a backup function in case the RFID transponder 18(2) and/or antenna 34(2) becomes inoperable, so that sensor data relating to the mating component 12(2) can still be reported to the RFID reader 20. The additional RFID transponder 18(3) may be dedicated to sensing of sensor data from the sensor 28(3) and/or data logging while the RFID transponder 18(2) is dedicated to receiving sensor data from sensor 28(2) and communicating with a component 12(1). The RFID transponders 18(2), 18(3) may also be configured to communicate with each other to exchange information via communications with the RFID reader 20 when it is impractical or impossible to provide a direct electrical communication link between the IC chips 32(2), 32(3) of the RFID transponders 18(2), 18(3). Further, the RFID reader 20 can check the sensor data from both sensors 28(2), 28(3) against each other as a redundancy feature and to ensure no discrepancies exist indicative of a failure in the mating component 12(2). All other functionalities and possibilities that exist for the component mating systems 10(2) of
If the additional sensor 28(3) is not needed or desired, or if a third party transponder is provided as part of the mating component 12(2) that does not contain the additional sensor 28(3), a component mating system 10(13) like that illustrated in
In this embodiment, the communication bus 82 is an Inter-IC® (I2C) communication bus that follows the I2C protocol; however, any type of bus and communication protocol is possible. In this embodiment, the IC chip 32(2) incorporates an I2C interface that allows communication over the communication bus 82. Two additional ICs 84, 86 are provided that each contain circuitry or logic and an I2C interface and can communicate on the communication bus 82 with each other and the IC chip 32(2). Since an I2C communication bus is a multi-master bus, any of the IC chip 32(2) and the ICs 84, 86 can control the bus by initiating data transfer. However, one IC 84 is designated as the master controller, wherein the IC chip 32(2) and other IC 86 are considered slave controllers. Providing additional ICs 84, 86 in the mating component 12(2) may alleviate the IC chip 32(2) from having to include complex functionality that is desired. The additional functionality can be moved to the other ICs 84, 86. Further, if the mating component 12(2) includes a wired interface to the article of manufacture 14, the ICs 84, 86 may provide that interface so that identity information and/or sensor data can be communicated over wired communications, including on the communication bus 82, rather than limiting communications to the RF communications to the RFID reader 20.
The equipment 14(1) may be electrical or fiber optic equipment as examples, and may include patch panels for a network or other types of equipment, including a router or a server, as examples. As illustrated in
Components 12 can be placed on the equipment rack 90 in known locations to sense information regarding environment and/or physical conditions. Also, when a removable component 12(1) is connected to a fixed component 12(2), a connection condition event is triggered such that the IC chips 32(1), 32(2), RFID-enabled or not, or a combination of each, and/or other components coupled to electrical leads 36(1), 36(2), like shown in
The disclosed technologies can be configured in different ways, resulting in different functionalities. In addition to the examples provided above, the components may be located on a plug (such as a connector), a socket (such as an adapter), a housing, a cabinet, an equipment rack, a component or patch panel, a separate object, or other components (or portions thereof). The sensors may be responsive to detect one or more conditions and/or changes in environmental and/or physical conditions.
Although
It should also be understood that elements of the embodiments below may be mixed in different ways to achieve still further embodiments and functionality within the scope of the embodiments herein.
Any functionalities disclosed in any embodiments may be incorporated or provided in any other embodiments with suitable circuitry and/or devices. Although the illustrated embodiments are directed to components, wherein RFID-enabled versions of the components, including ICs and IC chips, employ passive RFID transponders, further embodiments include one or more semi-passive or active RFID transponders depending upon the particular functionality of the RFID transponder system desired.
Although the embodiments described herein are directed to components used with components in general, the embodiments are applicable to any type of component. Examples include fiber optic connectors and adapters or copper connectors and adapters and other fiber optic and/or copper components. Embodiments disclosed herein can be used in non-telecommunications equipment, particularly regarding components that interconnect and/or are exposed to various conditions for which it is desirable to know the location, connectivity, and/or conditions of the components. The terms “plug” and “socket” are generally used herein to define portions of components that are adapted for connecting to one another, such as a connector that is received by an adapter, and are not necessarily limited to standard plugs and sockets.
Many modifications and other embodiments set forth herein will come to mind to one skilled in the art to which the embodiments pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings.
Therefore, it is to be understood that the description and claims are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. It is intended that the embodiments cover the modifications and variations of these embodiments provided they come within the scope of the appended claims and their equivalents. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.
Number | Name | Date | Kind |
---|---|---|---|
4889977 | Haydon | Dec 1989 | A |
5483467 | Krupka et al. | Jan 1996 | A |
5528222 | Moskowitz et al. | Jun 1996 | A |
5821510 | Cohen et al. | Oct 1998 | A |
5910776 | Black | Jun 1999 | A |
5914862 | Ferguson et al. | Jun 1999 | A |
5995006 | Walsh | Nov 1999 | A |
6002331 | Laor | Dec 1999 | A |
6025725 | Gershenfeld et al. | Feb 2000 | A |
6100804 | Brady et al. | Aug 2000 | A |
6118379 | Kodukula et al. | Sep 2000 | A |
6127929 | Roz | Oct 2000 | A |
6133835 | De Leeuw et al. | Oct 2000 | A |
6164551 | Altwasser | Dec 2000 | A |
6232870 | Garber et al. | May 2001 | B1 |
6424263 | Lee et al. | Jul 2002 | B1 |
6424315 | Glenn et al. | Jul 2002 | B1 |
6496113 | Lee et al. | Dec 2002 | B2 |
6496382 | Ferguson et al. | Dec 2002 | B1 |
6522308 | Mathieu | Feb 2003 | B1 |
6618022 | Harvey | Sep 2003 | B2 |
6693513 | Tuttle | Feb 2004 | B2 |
6784802 | Stanescu | Aug 2004 | B1 |
6808116 | Eslambolchi et al. | Oct 2004 | B1 |
6829427 | Becker | Dec 2004 | B1 |
6847586 | Chen | Jan 2005 | B1 |
6847856 | Bohannon | Jan 2005 | B1 |
6857897 | Conn | Feb 2005 | B2 |
6897374 | Garber et al. | May 2005 | B2 |
6898368 | Colombo et al. | May 2005 | B2 |
6899626 | Luciano et al. | May 2005 | B1 |
6915050 | Koyasu et al. | Jul 2005 | B2 |
6924997 | Chen et al. | Aug 2005 | B2 |
6968994 | Ashwood Smith | Nov 2005 | B1 |
6971895 | Sago et al. | Dec 2005 | B2 |
6973243 | Koyasu et al. | Dec 2005 | B2 |
6999028 | Egbert | Feb 2006 | B2 |
7014100 | Zierolf | Mar 2006 | B2 |
7061366 | Bell et al. | 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 |
7102520 | Liu et al. | Sep 2006 | B2 |
7151455 | Lindsay et al. | Dec 2006 | B2 |
7158031 | Tuttle | Jan 2007 | B2 |
7158033 | Forster | Jan 2007 | B2 |
7165728 | Durrant et al. | Jan 2007 | B2 |
7170393 | Martin | Jan 2007 | B2 |
7194180 | Becker | Mar 2007 | B2 |
7205898 | Dixon et al. | Apr 2007 | B2 |
7209042 | Martin et al. | Apr 2007 | B2 |
7210858 | Sago et al. | May 2007 | B2 |
7221277 | Caron 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 |
7243837 | Durrant et al. | Jul 2007 | B2 |
7249705 | Dudley | Jul 2007 | B2 |
7253735 | Gengel et al. | Aug 2007 | B2 |
7265674 | Tuttle | Sep 2007 | B2 |
7275970 | Hoshina | Oct 2007 | B2 |
7297028 | Daikuhara et al. | Nov 2007 | B2 |
7298266 | Forster | Nov 2007 | B2 |
7298330 | Forster | Nov 2007 | B2 |
7306489 | Werthman et al. | Dec 2007 | B2 |
7336883 | Scholtz | Feb 2008 | B2 |
7348884 | Higham | Mar 2008 | B2 |
7349605 | Noonan et al. | Mar 2008 | B2 |
7352285 | Sakama et al. | Apr 2008 | B2 |
7352289 | Harris | Apr 2008 | B1 |
7356208 | Becker | Apr 2008 | B2 |
7554448 | Tomioka | Jun 2009 | B2 |
20020092347 | Niekerk et al. | Jul 2002 | A1 |
20030021580 | Matthews | Jan 2003 | A1 |
20030061393 | Steegmans et al. | Mar 2003 | A1 |
20030179073 | Ghazarian | Sep 2003 | A1 |
20040041714 | Forster | Mar 2004 | A1 |
20040114879 | Hiereth et al. | Jun 2004 | A1 |
20040117515 | Sago et al. | Jun 2004 | A1 |
20040149736 | Clothier | Aug 2004 | A1 |
20040253874 | Plishner | Dec 2004 | 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 |
20050215119 | Kaneko | Sep 2005 | A1 |
20050224585 | Durrant et al. | Oct 2005 | A1 |
20050232636 | Durrant et al. | Oct 2005 | A1 |
20050242950 | Lindsay et al. | Nov 2005 | A1 |
20050259930 | Elkins et al. | Nov 2005 | A1 |
20050285718 | Enguent | Dec 2005 | A1 |
20060006999 | Walczyk et al. | Jan 2006 | A1 |
20060015233 | Olsen, III et al. | Jan 2006 | A1 |
20060019540 | Werthman et al. | Jan 2006 | A1 |
20060044148 | Daniels et al. | Mar 2006 | A1 |
20060139149 | Faro et al. | Jun 2006 | A1 |
20060145863 | Martin et al. | Jul 2006 | A1 |
20060148279 | German et al. | Jul 2006 | A1 |
20060166546 | Ashizawa et al. | Jul 2006 | A1 |
20060232419 | Tomioka et al. | Oct 2006 | A1 |
20060233506 | Noonan et al. | Oct 2006 | A1 |
20060267737 | Colby | Nov 2006 | A1 |
20060267778 | Gengel et al. | Nov 2006 | A1 |
20070001807 | Malone et al. | Jan 2007 | A1 |
20070018787 | Martinez de Velasco Cortina et al. | Jan 2007 | A1 |
20070023525 | Son et al. | Feb 2007 | A1 |
20070057771 | Tomioka | Mar 2007 | A1 |
20070120684 | Utaka et al. | May 2007 | A1 |
20070152828 | Mohalik | Jul 2007 | A1 |
20070205897 | Forster | Sep 2007 | A1 |
20070205902 | Cote et al. | Sep 2007 | A1 |
20070216534 | Ferguson et al. | Sep 2007 | A1 |
20070236355 | Flaster et al. | Oct 2007 | A1 |
20070247284 | Martin et al. | Oct 2007 | A1 |
20070273507 | Burchell et al. | Nov 2007 | A1 |
20080030353 | O'Toole et al. | Feb 2008 | A1 |
20080048826 | Agrawal et al. | Feb 2008 | A1 |
20080100440 | Downie et al. | May 2008 | A1 |
20080100456 | Downie et al. | May 2008 | A1 |
20080122641 | Amidi | May 2008 | A1 |
20080240724 | Aguren | Oct 2008 | A1 |
Number | Date | Country |
---|---|---|
19841738 | Mar 2000 | DE |
10249414 | May 2004 | DE |
1455550 | Sep 2004 | EP |
2371211 | Jul 2002 | GB |
03242795 | Oct 1991 | JP |
2003148653 | Oct 1991 | JP |
2002264617 | Sep 2002 | JP |
2003172827 | Jun 2003 | JP |
2003229215 | Aug 2003 | JP |
2004039389 | Feb 2004 | JP |
2004142500 | May 2004 | JP |
2004152543 | May 2004 | JP |
2004245963 | Sep 2004 | JP |
2004247090 | Sep 2004 | JP |
2004264901 | Sep 2004 | JP |
2004265624 | Sep 2004 | JP |
2004317737 | Nov 2004 | JP |
2004349184 | Dec 2004 | JP |
2005018175 | Jan 2005 | JP |
2005033857 | Feb 2005 | JP |
2005050581 | Feb 2005 | JP |
2005084162 | Mar 2005 | JP |
2005086901 | Mar 2005 | JP |
2005087135 | Apr 2005 | JP |
2005092107 | Apr 2005 | JP |
2005134125 | May 2005 | JP |
2005216698 | Aug 2005 | JP |
2005302403 | Oct 2005 | JP |
2005315980 | Nov 2005 | JP |
2005339983 | Dec 2005 | JP |
2006054118 | Feb 2006 | JP |
2006245983 | Sep 2006 | JP |
2006279650 | Oct 2006 | JP |
2007087849 | Apr 2007 | JP |
2007088957 | Apr 2007 | JP |
2007158993 | Jun 2007 | JP |
2007189774 | Jul 2007 | JP |
2007221400 | Aug 2007 | JP |
0155991 | Aug 2001 | WO |
03098175 | Nov 2003 | WO |
2004030154 | Apr 2004 | WO |
2005069203 | Jul 2005 | WO |
2006058119 | Jun 2006 | WO |
2008000656 | Jan 2008 | WO |
Number | Date | Country | |
---|---|---|---|
20100245057 A1 | Sep 2010 | US |