The present invention relates generally to the use of radio-frequency identification (RFID) systems, and in particular is related to RFID-based systems and methods for collecting information from a telecommunications network.
Typical telecommunications systems include telecommunications data centers that have a large number of optical and electrical cable connections that operably connect various types of network equipment and components. Examples of network equipment and components include electrically powered (active) units such as optical transceivers, servers, switches and routers, and unpowered (passive) units such as fanout boxes and patch panels (collectively, “network equipment”). This network equipment is often installed within cabinets in standard (e.g., 19″) equipment racks. Each piece of equipment typically provides one or more adapters where optical or electrical patch cables can be physically connected to the equipment. These patch cables are generally routed to network equipment located in the same cabinet or to another cabinet. This network equipment is, in turn, connected to other network equipment.
A common problem in telecommunications networks is determining the most current configuration of all the optical and electrical links among all the network equipment. The “physical layer” configuration can be completely determined if the physical locations of all connected patch cable connectors on installed network equipment are known. Information about the physical location and orientation of the adapters and their parent patch panels in data center cabinets is presently manually recorded and added to the network management software database after the adapters and patch panels are installed. However, this process is labor-intensive and prone to errors. Additionally, any changes made to the physical configuration of any network equipment must be followed up with corresponding changes to the network management software database, which delays providing the most up-to-date information about the network configuration. Furthermore, errors from manual recording and entry of configuration data tend to accumulate over time, reducing the trustworthiness of the network management software database.
Another problem in telecommunications data center management is determining or otherwise extracting identity and diagnostic information from network equipment, particularly for that equipment that resides “upstream” of the physical layer. For example, small form-factor pluggable (SFP) optical transceivers (“transceivers”) are used extensively in telecommunications networks. SFP transceivers convert optical signals to electrical signals (O/E conversion) and vice versa (E/O conversion). Such transceivers provide an interface between electronics-based devices (e.g., switches, routers, server blades, etc.) and fiber optic cables (e.g., jumper cables). Likewise, SFP transceivers provide an interface between optical devices (e.g., light sources) and electronic devices such as electrical cables, detectors, etc.
SFP transceivers have a number of important operational (diagnostic) parameters such as the data rate (e.g., 4.25 Gb/s, 10 Gb/s, etc.), temperature, current, voltage, bit-error rate, security status, connectivity information/status, etc. SFP transceivers also have a number of important identity parameters, such as manufacturer, serial number, location, install date, etc. Consequently, SFP transceivers need to be monitored by field technicians, who need to obtain identity and diagnostic information about the transceivers in order to assess the network status and to diagnose network problems.
In addition to SFP transceiver identity and diagnostic information, it would also be desirable to obtain like information from the electronics equipment to which the SFP transceivers are connected or hosted by, such as MAC address, IP address, and data from other network layers. Such information resides “upstream” of the physical layer and so is not otherwise readily accessible to field technicians that monitor the physical layer.
A first aspect of the invention is a radio-frequency identification (RFID)-based system for collecting information from a telecommunications network. The system includes an optical transceiver having transceiver circuitry configured to perform at least one of storing, receiving and communicating information. The system also includes an optical fiber connector having a connector RFID tag configured to store information and communicate with the transceiver circuitry when electrically connected to the transceiver. The connector RFID tag is adapted to generate a connector RFID-tag signal (ST1) that contains information stored in the connector (“connector-stored information”). The system also includes an RF reader adapted to generate a reader signal (SR) that elicits the connector RFID-tag signal and that is configured to store information contained in the connector RFID-tag signal.
A second aspect of the invention is a RFID-based system for collecting information from a telecommunications network. The system includes an optical transceiver having a transceiver circuitry configured to perform at least one of storing, receiving and communicating information, including transceiver information. The system also includes electronics equipment operably connected to the transceiver. The electronics equipment contains electronics-equipment information (e.g., stored in a memory unit therein). The electronics equipment and transceiver are configured to communicate the electronics-equipment information to the transceiver. The transceiver includes a transceiver RFID tag operably supported by the transceiver. The transceiver RFID tag is adapted to generate a transceiver RFID-tag signal that includes the transceiver information and/or the electronics-equipment information. The system also includes a RF reader adapted to produce a reader signal that elicits the transceiver RFID-tag signal and that is configured to store information contained in the transceiver RFID-tag signal.
A third aspect of the invention is information-collection system for collecting information from a telecommunications network. The system includes a transceiver having transceiver circuitry configured to perform at least one of storing, receiving and communicating information, including transceiver information. The system also includes electronics equipment operably connected to the transceiver and that contains electronics-equipment information and a first processor that operably supports information processing software. The electronics equipment and transceiver are configured to communicate the transceiver information and the electronic information to the first processor, which forms processed information. The system includes a database having a second processor in operable communication with the first processor and that operably supports the information processing software. The processed information from the first processor is preferably communicated to the second processor for further processing.
A fourth aspect of the invention is a method of collecting information from a telecommunications network that includes an optical fiber connector and a transceiver. The method includes storing transceiver information in the transceiver, and communicating the transceiver information to the optical fiber connector when the transceiver and optical fiber connector are operably coupled. The method also includes, using a RFID tag in the optical fiber connector to transmit to a RF reader a connector RFID-tag signal that includes the transceiver information.
A fifth aspect of the invention is a method of collecting information from a telecommunications network that includes a transceiver. The method includes storing transceiver information in the transceiver, and then using a RFID tag in the transceiver to transmit to a RF reader a transceiver RFID-tag signal that includes the transceiver information.
A sixth aspect of the invention is a method of collecting information from a telecommunications network that includes a transceiver having a port that connects to an optical fiber connector. The method includes storing transceiver information in transceiver circuitry within the transceiver. The method further includes connecting a portable test device having a memory unit and a RF reader attached to the memory unit to form an electrical connection with the transceiver circuitry. The method also includes communicating the transceiver information from the transceiver circuitry to the memory unit and then to the RF reader.
A seventh aspect of the invention is a method of collecting electronics-equipment information stored in a memory chip of electronics equipment of a telecommunications network. The method includes connecting a portable test device having a memory unit and a RF reader attached to the memory unit to form an electrical connection with the memory chip. The method also includes communicating the electronics-equipment information from the memory chip to the memory unit and then to the RF reader.
An eighth aspect of the invention is a method of collecting information from a telecommunications network that includes a transceiver having a port that connects to an optical fiber connector. The method includes storing transceiver information in transceiver circuitry within the transceiver, and communicating the transceiver information to electronics equipment that includes stored electronics-equipment information and a first processor. The method also includes communicating the transceiver information and the electronics-equipment information to the first processor and forming therein processed information. The processed information is then communicated to a second processor in a database unit.
A ninth aspect of the invention is a RFID-based system for collecting information from a telecommunications network. The system includes a transceiver having a socket configured to connect to an optical fiber connector, the transceiver including transceiver circuitry configured to store information (“transceiver-stored information”). The system also includes a portable test device having a memory unit and a RF reader attached to the memory unit and configured to engage with the transceiver socket to form an electrical connection between the transceiver circuitry and the memory unit. The memory unit and transceiver circuitry are configured to transfer the transceiver-stored information to the memory unit and then to the RF reader.
A tenth aspect of the invention is a RFID-based system for collecting information from electronics equipment of a telecommunications system. The system includes at least one transceiver port in the electronics equipment. The system also includes a memory chip in the electronics equipment that is configured to store electronics-equipment information. The system further includes a portable test device having a memory unit and a RF reader attached to the memory unit. The portable test device is configured to engage with the transceiver port to form an electrical connection between the memory chip and the memory unit. The memory unit and the memory chip are configured to transfer the electronics-equipment information to the memory unit and then to the RF reader.
These and other aspects of the invention are described below. 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 the various exemplary embodiments of the invention, and together with the description serve to explain the principals and operations of the invention.
The present invention is directed to the use of RFID systems, and in particular is directed to RFID-based systems and methods for collecting identity and/or diagnostic information from a telecommunications network.
Collecting Transceiver Identity and/or Diagnostic Information
Transceiver
Example embodiments of transceiver 10 are disclosed in U.S. Pat. Nos. 5,047,835; 6,878,875; 7,264,405; and 7,287,916, all of which are incorporated by reference herein. A two-fiber transceiver 10 is described below by way of illustration. One skilled in the art will recognize that the present invention applies to the myriad types of transceivers available today, including single-fiber transceivers, and multi-fiber transceivers.
In one example embodiment shown by way of illustration, transceiver 10 of
Transceiver 10 includes a printed circuit board PCB that operably supports a number of electrical, optical and opto-electronic components. Such components include, for example, transceiver opto-electronics 38 that include an input receiver optical subassembly (ROSA) 40R and an output transmitter optical subassembly (TOSA) 40T. ROSA 40R comprises a photodiode 46 for detecting optical signals and sensing circuitry 48 connected thereto for converting the optical signals to digital signals compatible with other network equipment. TOSA 40T comprises a laser 52 for transmitting optical signals and control circuitry 54 connected thereto for modulating the laser according to an input digital data signal.
Photodiode 46 of ROSA 40R is optically coupled to a receive optical fiber 60R that terminates at optical port 24R. Likewise, laser 56 of TOSA 40T is optically coupled to a transmit optical fiber 60T that terminates at optical port 24T. ROSA 40R and TOSA 40T are electrically connected to transceiver circuitry 90, which is electrically connected to back-end electrical connector 36. Transceiver circuitry 90 is discussed in greater detail below. Connector 36 is used to connect transceiver 10 to “electrical equipment” 400, which may be for example, a computer, server, router or other network equipment. The design of transceiver 10 is typically standards-based so that it can connect with network equipment such as electrical equipment 400 without significant customization. An example embodiment of transceiver 10 includes a DC power source 80 connected to transceiver circuitry 90, as shown. Other embodiments of transceiver 10 do not have a DC power source and instead receive their DC power externally (e.g., via electronics equipment 400).
Various types of and functionalities for transceiver circuitry 90 are contemplated by the present invention. In an example embodiment, transceiver circuitry 90 comprises a memory chip 92 adapted to store information. In an example embodiment, memory chip 92 is configured to receive and store information, and in particular identity and diagnostic transceiver information.
In an example embodiment, transceiver circuitry 90 includes an existing IC chip in transceiver 10 (e.g., part of transceiver opto-electronics 38). In another example embodiment, transceiver circuitry 90 is added to transceiver 10 to provide the additional information-collection and inter-chip communication capabilities described below. In an example embodiment, transceiver circuitry 90 has both memory and digital diagnostic capability as well as chip-to-chip communication capability. In an example embodiment, transceiver circuitry 90 is an IC chip that includes the above-mentioned information-collection and chip-to-chip communication capabilities. Information stored in transceiver circuitry 90 is referred to herein as “transceiver-stored information” to distinguish from the more specific instance where information about the transceiver itself (“transceiver information”) is stored in the transceiver circuitry and/or elsewhere.
In an example embodiment, transceiver circuitry 90 includes transceiver information, such as identity information in the form of, for example, an identification number (e.g., a 32-bit unique identifier), that in turn may include one or more pieces of data, such as a transceiver serial number, component type, component manufacturer, manufacturing date, installation date, location, lot number, performance parameters (such as attenuation measured during installation), identification of what component is at the other end of the transceiver and the status of that component, etc. In an example embodiment, the identify information is stored (e.g., pre-installed) in transceiver circuitry 90.
In an example embodiment, transceiver circuitry 90 also stores transceiver information in the form of diagnostic information (e.g., in 16-bit diagnostic words) relating to the operation of transceiver 10, such as transmit power, receive power, back-fact monitor current, temperature, loss-of-signal, etc.).
Note that transceiver 10 is thus adapted not only for communicating optical information via ROSA 40R and TOSA 40T, but is also adapted to store information in transceiver electronics 90 and electrically communicate this transceiver-stored information as described below.
Connector
Optical fiber connector 200 is attached to an end of a fiber optic cable 206 that in an example embodiment includes receive and transmit optical fibers 210R and 210T. Connector 200 includes a modular plug-type connector housing 220 having an input end 230 configured to engage with transceiver socket 20. Socket 20 is configured so that fibers 210R and 210T optically connect with respective transceiver receive and transmit fibers 60R and 60T at respective receive and transmit connector plug ends 212R and 212T that engage respective transceiver receive and transmit optical ports 24R and 24T.
In an example embodiment, optical fiber connector 200 also includes a RFID tag 250. RFID tag 250 includes a substrate 251 that supports electrical leads 252A and 252B, which lead to electrical contacts 254A and 254B at input end 230. Electrical contacts 254A and 254B are configured to mate with or otherwise establish contact with transceiver electrical contacts 30A and 30B.
Electrical leads 252A and 252B are connected to a RFID integrated circuit (RIC) chip 280 within RFID tag 250. RFID tag 250 also includes a RFID antenna system 284 that is preferably supported by substrate 251 and that is electrically connected to RIC chip 280. RFID antenna system 284 is adapted to generate tag signals ST1 that includes information received by or in stored in RIC chip 280. In an example embodiment, RFID tag 250 is passive and receives a reader signal (discussed below) and “generates” tag signals ST1 by reflecting or backscattering the reader signal in a manner than imparts information onto the tag signals.
RIC chip 280 is configured (e.g., with a memory unit 286) to store information (“connector-stored information”), such as identification (ID) numbers N1, N2, . . . Nj (e.g., 32-bit unique identifiers) that in turn may include one or more pieces of data, such as a connector serial number, component type, component manufacturer, manufacturing date, installation date, location, lot number, performance parameters (such as attenuation measured during installation), identification of what is at the other end of the component and the status of that component, etc. In general, RIC chip 280 can store any information capable of being stored in an IC chip. RIC chip 280 is configured (e.g., programmed) to receive and/or exchange information (and generally engage in chip-to-chip communication) with another IC chip or circuitry, and in particular with transceiver circuitry 90. Information stored in connector 200 (e.g., in RIC chip 280) is referred to as “connector-stored information” to distinguish from the more specific instance where information about the connector (called “connector information”) is stored in the connector. For example, the connector-stored information can include transceiver information communicated between transceiver circuitry 90 and RIC-chip 280. Likewise, transceiver-stored information can include connector information communicated from RIC-chip 280 to transceiver circuitry 90.
An exemplary RFID tag 250 is disclosed in U.S. patent application Ser. No. 61/011,194, entitled “RFID systems and methods for automatically detecting and/or directing the physical configuration of a complex system,” filed on Jan. 15, 2008 and assigned to Corning Cable Systems LLC, and which patent application is incorporated by reference herein. In an example embodiment, RFID tag 250 (which is also referred to in the art as an “RFID transponder”) includes a switch (e.g., a push-button-type switch) 260 (
In another embodiment, switch 260 provides a latchable signal to RIC chip 280 as an IC input rather than or in addition to connecting or activating the antenna. For example, a field technician can activate the RFID tag to cause it to generate a tag signal ST1 representative of the type of component or network equipment to which the RFID tag is attached, and where the network equipment is to be connected. An example of such a RFID tag 250 is described in U.S. patent application Ser. No. 11/590,377, entitled “Radio Frequency Identification Transponder for Communicating the Condition of a Component,” which patent application is assigned to Corning Cable Systems, LLC, and which patent application is incorporated by reference herein. An example RFID tag 250 is compliant with RFID communication standards such as EPC Global class 1, and is a “Gen2” type of RFID tag.
With reference again to
RFID-based information-collection system 4 further includes an information processing system 320, such as a computer, operably connected to RF reader 300 and adapted to store and process information from the RF reader. In an example embodiment, information processing system 320 is adapted to receive wired or wireless data signals SD from RF reader 300. Information processing system 320 includes a database unit 340 adapted (e.g., via database unit software stored on a computer-readable medium) to store and process information, particularly information about RFID tags 250 provided to the information processing system from RF reader 300. In an example embodiment, database unit 340 includes basic (e.g., background or general) information about connector 200 and/or transceiver 10.
In an example embodiment, this basic information is inputted into database unit 340 (e.g., manually, or via an external computer-readable medium 342 (
In an example embodiment, information processing system 320 includes a display 360, such as a standard LCD monitor or personal digital assistant (PDA), that displays (e.g., using graphics and/or alphanumerics) the system configuration information stored in database unit 340.
Database unit 340 within information processing system 320 stores and process the information from RFID tag 250. In an example embodiment, the network management software in database unit 340 combines (e.g., processes) the information received from RF reader 300 with previously stored basic information about transceiver 10. This combined information is then optionally displayed on display 360 to provide a user with a (real-time) view of transceiver 10. Example embodiments of the role of the network management software of system 4 in managing identity and/or diagnostic information relating to connector 200, transceiver 10 and/or electronics equipment 400 is discussed in greater detail below.
Example Methods of Operation
In an example embodiment of the operation of RFID-based information-collection system 4, connector 200 is connected to transceiver 10 at socket 20. This causes the receive and transmit optical fibers 210R and 210T in connector 200 to optically connect to their transceiver 10 counterparts 60R and 60T, thereby establishing an optical connection between the connector and the transceiver. Likewise, RFID tag electrical contacts 254A and 254B electrically connect to their transceiver counterparts 30A and 30B, thereby establishing electrical connection between RIC chip 280 and transceiver circuitry 90.
At this point, transceiver-stored information can be communicated from transceiver circuitry 90 to RIC chip 280. As mentioned above, such information can include transceiver information, such as transceiver identity information (serial numbers, manufacturer, date installed, etc.) and/or transceiver diagnostic information. The diagnostic information may include, for example, connectivity status, temperature, laser power, receiver/detector power, data rate, power consumption, operational status, error information, loss of signal, back-face monitor current, etc. Likewise, connector-stored information can be communicated from RIC chip 280 to transceiver circuitry 90. Such information can include the aforementioned connector information, as well as any other information provide to the RIC chip 280, such as from reader signals SR from RF reader 300.
In an example embodiment, the circuit-to-chip (or chip-to-chip) communication is carried out using, for example, a one-wire or two-wire serial interface running in the range of 10-100 kB/sec, using a method such as pulse-width modulation, IIC, parallel digital interface, or other methods and chip-to-chip signal protocols known in the art. The transceiver-stored information communicated from transceiver 10 to connector 200 is stored in RIC chip 280. Likewise, connector-stored information communicated from connector 200 to transceiver 10 is stored in transceiver circuitry 90 (e.g., in memory chip 92).
In an example embodiment where transceiver diagnostic information is communicated from transceiver circuitry 90 to RIC chip 280, the diagnostic information is communicated one diagnostic word at a time from digital diagnostic unit 93 in the transceiver circuitry to the RIC chip and stored in the RIC chip (e.g., in memory unit 286) using one of the known digital signal protocols. Each diagnostic word is assigned a specific number, known in advance, which number associates the numbered word with the parameter it represents. The diagnostic word number is communicated along with the word itself, so that RF reader 300 knows what information it has received from RFID tag 250.
Once the identity and/or the diagnostic information is communicated from transceiver 10 to RIC chip 280, this information (and optionally connector information) is communicated to RF reader 300 via a tag signal ST1 elicited by reader signals SR from the RF reader. Some or all of the received information is then communicated to information processing system 320 and database unit 340 therein. In an example embodiment, information processing system 320 is part of or is otherwise incorporated into RF reader 300.
As discussed above, database unit 340 preferably includes network management software adapted to process information and determine the current (i.e., real-time) configuration of telecommunications network portion 5 as well as the other portions of the network (not shown). Thus, the network configuration can be constantly updated as changes, such as network equipment being mated (connected) and unmated (disconnected) are made to the network and transmitted to database unit 340 via RF reader 300. This eliminates the need to manually record and enter physical location data on network equipment into the network management software both during set-up as well as during maintenance or when changing the network configuration for any reason. It also ensures that database 340 is completely accurate, even while new network equipment is being added or removed.
Collecting Upstream Identifier and/or Diagnostic Information
With continuing reference to
EIC memory chip 426 is electrically connected to transceiver ports 460 via electrical connectors 462 and is configured for chip-to-chip communication. In particular, EIC memory chip 426 is configured to communicate the stored electronics-equipment information to transceiver circuitry 90, which are also configured for chip-to-chip communication. In example embodiments discussed in greater detail below, transceiver-stored information in transceiver circuitry 90 is communicated to EIC memory chip 426. The communication of information between EIC chip 426 and transceiver circuitry 90 uses, for example, known parallel or serial digital communication protocols at data rates from 10 kB/s to 10 Mb/s.
In an example embodiment, the electronics-equipment information stored in transceiver circuitries 90 in transceivers 10 is then communicated to RIC chips 280 of connectors 200 and then to RF reader 300 using the methods discussed above when connectors 200 are connected to the corresponding transceivers. This process allows for system 4 to extract information from a telecommunications network beyond (i.e., upstream of) the initial physical layer represented by connectors 200.
In an example embodiment, the communication of electronics-equipment information to transceiver 10 occurs automatically when the transceiver is electrically connected to electronics equipment 400. In another example embodiment, the communication is initiated by electronics equipment 400 when it initializes a port identifier, and/or each time it changes a port identifier.
In another example embodiment, transceiver circuitry 90 is configured to initiate the communication of information periodically after the initial information transfer that occurs when the transceiver is first connected to electronics equipment 400.
In yet another example embodiment, the information transfer is initiated by RF reader 300 and reader signal SR after connector 200 is connected to transceiver 10, wherein RIC chip 280 sends a signal to transceiver circuitry 90 that causes the transceiver circuitry to initiate the information communication to the RIC chip. Various combinations of the above-described embodiments are also contemplated. Also, multiple communications may be used to transfer all of the electronics-equipment information to RIC chip 280 and then to RF reader 300.
Transceiver with RFID Tag
In the example embodiments shown in
This transceiver RFID tag embodiment allows for transceiver information and electronics-equipment information to be communicated to RF reader 300 without the need for a RFID-based connector 200. Also, in the case where connector 200 does not include a RFID tag or an RIC chip with connector information, the connector information can be inputted into database unit 340 directly by a system user such as a field technician. Further, once a connector 200 is connected to transceiver 10, connector information from RIC chip 280 can be communicated to transceiver circuitry 90 and then communicated via tag signal ST2 to RF reader 300. RF reader 300 then communicates some or all of the information it collects to information processing system 320 for further processing in database unit 340.
Portable Test Device
The present invention includes example embodiments that allow for a portable test device to directly electrically connect to a transceiver 10 or to electronics equipment 400 in order to obtain information about the transceiver and/or the electronics equipment.
In an example embodiment, portable test device 600 includes RF reader 300 and also includes electrical leads 252A and 252B that lead to electrical contacts 254A and 254B at input end 230. Input end 230 is configured to engage transceiver socket 20 so that the test equipment electrical contacts 254A and 254B electrically contact transceiver electrical contacts 30A and 30B. Housing 620 may include “dummy” plug ends 212R and 212T that engage respective transceiver receive and transmit optical ports 24R and 24T to facilitate the connection between portable test device 600 and transceiver 10.
Housing 620 contains a memory unit 610 that is electrically connected to electrical leads 252A and 252B and to RF reader 300. In an example embodiment, memory unit 610 is used for storing information (e.g., MAC, IP addresses, etc.) for electronics equipment ports 450 (
Collecting Downstream Identifier and/or Diagnostic Information
In one example embodiment, connector information from connector 200 is communicated to transceiver 10 as discussed above in connection with
Information Processing and Mapping
As discussed above, database unit 340 of information processing system 320 stores and process the information via RF reader 300 collected using one or more of the above-mentioned systems and methods. In an example embodiment, the network management software in database unit 340 is configured to combine (e.g., process) the information received from RF reader 300 with previously stored basic information about transceiver 10, connector 200 and/or electronics equipment 400. In another example embodiment, database unit 340 is in operable communication with EIC processor 427 in equipment electronics 400 so that information sent downstream to the electronics equipment can be processed in the electronics equipment and then combined in the database with information obtained via RF reader 300 or previously stored in the database. The network management software operating in database unit 340 operates to output associations or relationships (“mappings”) between one or more connectors 200, one or more transceivers 10 and one or more electronics equipment 400 for the given telecommunications network 5. Note that in the case where information is processed in EIC processor 427 and database processor
In an example embodiment, information processed by database unit 340 is displayed on display 360 to provide a user with a (real-time) view of the mapping of telecommunications network 5. In a particular example embodiment, the various associations and relationships amongst connectors 200, transceivers 10 and/or electronics equipment 400 is displayed on display 360.
In an example embodiment of RFID-based information-collection system 4, the network management software obtains identification information relating to ports 450 of electronics equipment 400, such as port addresses (e.g., MAC addresses or IP addresses). The information may be provided via transceiver 10 directly using RFID tag 500, or via connector RFID tag 250, or via portable test device 600, as discussed above. This allows the network management software to match the port identifier information (e.g., IP address or MAC address) with transceiver serial numbers. This further enables the connector identity to be associated with the transceiver serial number and/or the port identifier information in the network management software, thereby providing a port-connector map. Other maps can be created that associate one piece of telecommunications network information with another, such as connector-connector maps, transceiver-connector maps, etc.
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.
This application is a continuation application of U.S. patent application Ser. No. 12/229,964 filed on Aug. 28, 2008, the content of which is relied upon and incorporated herein by reference in its entirety, and the benefit of priority under 35 U.S.C. §120 is hereby claimed.
Number | Name | Date | Kind |
---|---|---|---|
3052842 | Frohman, Jr. 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 et al. | 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 et al. | 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 et al. | 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 et al. | 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 |
6924781 | Gelbman | Aug 2005 | B1 |
6924997 | Chen et al. | Aug 2005 | B2 |
6961675 | David | Nov 2005 | B2 |
6968994 | Ashwood 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 |
6992567 | Cole et al. | Jan 2006 | 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 et al. | 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 |
7411500 | Hamerly et al. | Aug 2008 | B2 |
7468669 | Beck et al. | Dec 2008 | B1 |
7504945 | Cox et al. | Mar 2009 | B2 |
7757936 | Aguren et al. | Jul 2010 | B2 |
7760094 | Kozischek et al. | Jul 2010 | B1 |
7772975 | Downie et al. | Aug 2010 | B2 |
7782202 | Downie et al. | Aug 2010 | 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 |
20040052471 | Colombo et al. | 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 |
20050040241 | Raskar | 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 |
20050098630 | Nakazawa | May 2005 | A1 |
20050111491 | Caveney | May 2005 | A1 |
20050215119 | Kaneko | Sep 2005 | A1 |
20050219050 | Martin | Oct 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, II et al. | Nov 2005 | A1 |
20050260884 | Yueh | Nov 2005 | A1 |
20050280511 | Yokoyama et al. | Dec 2005 | A1 |
20060039136 | Probasco et al. | Feb 2006 | A1 |
20060042984 | Suzuki | Mar 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 |
20060292311 | Kilburn et al. | 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 |
20070055470 | Pietrzyk et al. | Mar 2007 | A1 |
20070059975 | Walsh | Mar 2007 | A1 |
20070116411 | Benton et al. | May 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 |
20080100456 | Downie et al. | May 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 |
20080240724 | Aguren | Oct 2008 | A1 |
20090032577 | Aguren et al. | Feb 2009 | A1 |
20090079544 | Noble | Mar 2009 | A1 |
20090096581 | Macauley et al. | Apr 2009 | A1 |
20090224039 | Hause et al. | Sep 2009 | A1 |
20090240945 | Aronson | Sep 2009 | A1 |
20090261955 | Moore et al. | Oct 2009 | A1 |
20100080554 | Aguren | Apr 2010 | A1 |
Number | Date | Country |
---|---|---|
101095152 | Dec 2007 | CN |
101268497 | Sep 2008 | CN |
19841738 | Mar 2000 | DE |
19920452 | Nov 2000 | DE |
10244304 | Mar 2004 | DE |
10249414 | May 2004 | DE |
1455550 | Sep 2004 | EP |
1467232 | Oct 2004 | EP |
1686025 | Aug 2006 | EP |
1696680 | Aug 2006 | EP |
2347508 | Sep 2000 | GB |
2371211 | Jul 2002 | GB |
03242795 | Oct 1991 | JP |
04039483 | Feb 1992 | JP |
04174406 | Jun 1992 | JP |
08191257 | Jul 1996 | JP |
2001069625 | Mar 2001 | JP |
2001099946 | Apr 2001 | JP |
2002264617 | Sep 2002 | JP |
2003148653 | May 2003 | JP |
2003172827 | Jun 2003 | JP |
2003229215 | Aug 2003 | JP |
2003284213 | Oct 2003 | JP |
2004038583 | Feb 2004 | JP |
2004039389 | Feb 2004 | JP |
2004142500 | May 2004 | JP |
2004245963 | Sep 2004 | JP |
2004247090 | Sep 2004 | JP |
2004247134 | Sep 2004 | JP |
2004264901 | Sep 2004 | JP |
2004265624 | Sep 2004 | JP |
2004265860 | Sep 2004 | JP |
2004265861 | Sep 2004 | JP |
2004266886 | Sep 2004 | JP |
2004317737 | Nov 2004 | JP |
2004349184 | Dec 2004 | JP |
2004361896 | 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 |
2005234620 | Sep 2005 | JP |
2005302403 | Oct 2005 | JP |
2005315980 | Nov 2005 | JP |
2005339983 | Dec 2005 | JP |
2005341738 | Dec 2005 | JP |
2006054118 | Feb 2006 | JP |
2006101630 | Apr 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 |
03098175 | Nov 2003 | WO |
2004030154 | Apr 2004 | WO |
2006063023 | Jun 2006 | WO |
2007033294 | Mar 2007 | WO |
2008000656 | Jan 2008 | WO |
2008054742 | May 2008 | WO |
2008075123 | Jun 2008 | WO |
2008076235 | Jun 2008 | WO |
2008112169 | Sep 2008 | WO |
Entry |
---|
Office Action for Chinese patent application 200980105750.2 mailed Aug. 31, 2012, 25 pages. |
Decision of rejection for Japanese patent application 2009-541316 issued Aug. 7, 2012, 10 pages. |
Official Letter for Taiwanese patent application 098134450 mailed Oct. 3, 2012, 8 pages. |
European Search Report for application 07867312.6 mailed Sep. 12, 2012, 12 pages. |
European Search Report for application 07867314.2 mailed Sep. 12, 2012, 11 pages. |
First Office Action for Chinese Patent application 200980131993.3 mailed Feb. 1, 2013, 8 pages. |
First Office Action for Chinese Patent application 200980139124.5 mailed Mar. 4, 2013, 24 pages. |
Examination Report for European Patent Application 09701815.4 mailed Mar. 21, 2013, 4 pages. |
Non-final Office Action for U.S. Appl. No. 13/588,079 mailed May 14, 2013, 13 pages. |
Non-final Office Action for U.S. Appl. No. 12/229,964 mailed Aug. 5, 2013, 10 pages. |
First Office Action for Chinese patent application 200780050180.2 mailed Nov. 15, 2011, 11 pages. |
Third Office Action for Chinese patent application 200780050180.2 mailed Oct. 25, 2012, 7 pages. |
Second Office Action for Chinese patent application 200980105750.2 mailed May 9, 2013, 5 pages. |
First Office Action for Chinese patent application 200980144859.7 mailed Jun. 20, 2013, 9 pages. |
Examination Report for European Patent Application 09701815.4 mailed Apr. 14, 2011, 6 pages. |
International Search Report and Written Opinion for PCT/US2007/025136 mailed Jun. 2, 2008, 13 pages. |
International Search Report and Written Opinion for PCT/US2009/060151 mailed Dec. 17, 2009, 14 pages. |
International Search Report and Written Opinion for PCT/US2009/031099 mailed Apr. 1, 2009, 15 pages. |
International Search Report and Written Opinion for PCT/US 09/04087 mailed Aug. 27, 2009, 10 pages. |
International Search Report and Written Opinion for PCT/US2009/004566 mailed Feb. 1, 2010, 19 pages. |
Japanese Office Action for patent application 2009-541316 mailed Jan. 10, 2012, 10 pages. |
Examination Report for European patent application 09740228.3-2415 mailed Mar. 13, 2012, 12 pages. |
Examination Report for European patent application 09701815.4 mailed Apr. 3, 2012, 4 pages. |
Examination Report for European patent application 07853287.6 mailed May 15, 2012, 10 pages. |
Examination Report for European Patent application 09789099.0 mailed Jun. 14, 2012, 7 pages. |
Office Action for Chinese patent application 200780050180.2 mailed Jul. 20, 2012, 8 pages. |
Wilson, Brian et al., “Multiwavelength Optical Networking Management and Control,” Journal of Lightwave Technology, IEEE Dec. 1, 2000, vol. 18, No. 12, pp. 2038-2057. |
Examination Report for European patent application 07867312.6 mailed Sep. 16, 2013, 6 pages. |
Examination Report for European patent application 07867314.2 mailed Sep. 16, 2013, 5 pages. |
Second Office Action for Chinese patent application 200980139124.5 mailed Sep. 12, 2013, 7 pages. |
Notice of Allowance for U.S. Appl. No. 12/229,964 mailed Mar. 7, 2014, 5 pages. |
Advisory Action for U.S. Appl. No. 13/588,079 mailed Jan. 13, 2014, 4 pages. |
Third Office Action for Chinese patent application 200980139124.5 mailed Mar. 11, 2014, 19 pages. |
Third Office Action for Chinese patent application 200980105750.2 mailed Nov. 14, 2013, 8 pages. |
Second Office Action for Chinese patent application 200980131993.3 mailed Oct. 12, 2013, 13 pages. |
Final Office Action for U.S. Appl. No. 13/588,079 mailed Nov. 7, 2013, 16 pages. |
Translation of Third Office Action for Chinese patent application 200980131993.3 mailed Apr. 30, 2014, 4 pages. |
Number | Date | Country | |
---|---|---|---|
20130328666 A1 | Dec 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12229964 | Aug 2008 | US |
Child | 13965484 | US |