Login| Sign Up| Help| Contact|

Patent Searching and Data


Title:
RFID SYSTEMS AND METHODS FOR OPTICAL FIBER NETWORK DEPLOYMENT AND MAINTENANCE
Document Type and Number:
WIPO Patent Application WO/2010/042808
Kind Code:
A1
Abstract:
An optical-fiber-network (OFN) radio-frequency identification (RFID) system for deploying and/or maintaining and/or provisioning service and/or locating faults in an OFN. The system includes a plurality of OFN components, and at least one RFID tag that includes RFID tag data that has at least one property of the OFN component associated with the RFID tag. The RFID tag data is written to and read from the RFID tags using one or more mobile RFID readers either prior to, during or after deploying the OFN components. An OFN-component-data database unit is used to store and process the RFID tag data and is automatically updated by the one or more mobile RFID readers. This allows for different maps of the OFN to be made, such as an inventory map and a maintenance map, and for the maps to be automatically updated. The OFN-RFID system allows for mobile automated operations and management of OFN components by service personnel, and provides for faster and more accurate OFN system deployment and maintenance.

Inventors:
DOWNIE JOHN D (US)
KOZISCHEK DAVID R (US)
NEDERLOF LEO (BE)
SUTHERLAND JAMES S (US)
TAYLOR MARK P (US)
WAGNER RICHARD E (US)
WHITING MATTHEW S (US)
Application Number:
PCT/US2009/060151
Publication Date:
April 15, 2010
Filing Date:
October 09, 2009
Export Citation:
Click for automatic bibliography generation   Help
Assignee:
CORNING CABLE SYS LLC (US)
DOWNIE JOHN D (US)
KOZISCHEK DAVID R (US)
NEDERLOF LEO (BE)
SUTHERLAND JAMES S (US)
TAYLOR MARK P (US)
WAGNER RICHARD E (US)
WHITING MATTHEW S (US)
International Classes:
G06K19/00; H04B10/08; H04B10/20; H04J3/14; H04Q11/00
Domestic Patent References:
WO2008076235A12008-06-26
Foreign References:
US20080220721A12008-09-11
US20070176745A12007-08-02
US20060091207A12006-05-04
US6784802B12004-08-31
US20080100467A12008-05-01
US20060153517A12006-07-13
Attorney, Agent or Firm:
ADUSEI-POKU, Kwadjo (Intellectual Property DepartmentSP-TI-3-, Corning New York, US)
Download PDF:
Claims:
HE0347A What is claimed is:

1. A radio-frequency identification (RFID) method of deploying and/or maintaining and/or provisioning service and/or locating faults in an optical fiber network (OFN), comprising: providing at least one RFID tag on at least one OFN component of a plurality of OFN components that constitute the OFN; writing to at least one RFID tag using at least one RFID reader, OFN component data relating to at least one property of the corresponding OFN component; recording and storing the OFN component data in an OFN-component-data database unit; and automatically updating the OFN-component-data database by reading OFN component data from the at least one RFID tag using the one or more RFID tag readers.

2. The method of claim 1, further comprising: installing the OFN components in the OFN; and performing said providing of at least one RFBD tag prior to said installing.

3. The method of claim 1 , wherein reading OFN component-data is performed either during or after deploying the OFN.

4. The method of claim 1, further comprising: including in said OFN component data a location of the corresponding OFN component either as deployed or as to be deployed in the OFN; and using said location data to create a spatial map of the OFN.

5. The method of claim 4, including showing the spatial map of the OFN with a geographical map having geographical features, so as to locate the OFN components relative to geographical features. HE0347A

6. The method of claim 4, further comprising: locating at least one select OFN component based on said spatial OFN map; and reading the corresponding at least one RFID tag associated with the one or more select OFN component.

7. The method of claim 1, further comprising: including inventory data in the OFN component data; and using said inventory data to create an inventory map of the OFN.

8. The method of claim 1 , wherein the OFN includes an optical fiber cable having a length, and including: positioning RFID tags along the length of the optical fiber cable; and including as OFN component data the relative locations of the RFID tags along the optical fiber cable using global position system (GPS) coordinates.

9. The method of claim 1, wherein the plurality of OFN components includes at least one patch panel, and further comprising: including in at least one patch-panel RFID tag corresponding to the at least one patch panel, at least one OFN component data element from the group of OFN component data elements comprising: port identification, loss per port, and connectivity for each port.

10. The method of claim 1 , wherein the plurality of OFN components includes at least one splitter module, and further comprising: including in at least one splitter-module RFID tag corresponding to the at least one splitter module, at least one OFN component data element from the group of OFN component data elements comprising: shelf ID, port identification, loss data at a given wavelength, terminal ID, street name, street address, pole number, and GPS coordinates. HE0347A

11. The method of claim 1 , wherein the at least one RFID reader is mobile, and further comprising: bringing in the at least one mobile RPID reader within a read range of the at least one RPID tag affixed to the at least one OFN component and reading the OFN component data from the at least one RFED tag.

12. A radio-frequency identification (RFED) system for deploying and/or maintaining and/or provisioning service and/or locating faults in an optical fiber network (OFN), comprising: at least one RFID tag affixed to at least one OFN component of a plurality of OFN components that constitute the OFN, wherein the at least one RFID tag affixed to the at least one OFN component contains OFN component data that relates to at least one property of the OFN component; at least one mobile RFID tag reader adapted to be taken within a read range of the at least one RFID tag affixed to the at least one OFN component and adapted to read the OFN component data from the at least one RFID tag; and an OFN component data database unit adapted to receive and store OFN component data read by the at least one mobile RFED tag reader.

13. The RFED system of claim 12, wherein the OFN components include one or more OFN components selected from the group of OFN components comprising: a feeder cable, a distribution cable, a drop cable, a splitter, a splitter module, a network access point (NAP), an enclosure, a cabinet, a terminal, a patch panel, a patch cord, a splice box, a fiber connector, a coupler, an optical amplifier, a wavelength multiplexer, a wavelength demultiplexer, an optical line terminal (OLT), a filter, a light source, an optical receiver, an optical transmitter, an intrafacility cable, a local convergence point (LCP), a network interface device (NID), a fiber distribution frame (FDF), and a fiber equipment module.

14. The RFID system of claim 13, wherein one of the OFN components is a splitter module, and wherein the OFN component data for the splitter module includes at least one HE0347A data element selected from the group of data elements comprising: a shelf location, a port identification, a loss at a given wavelength, a terminal identification, a street name, a street address, and GPS coordinates.

15. The system of claim 13, wherein one of the OFN components is a patch panel having a number of optical fiber connection ports, and wherein the OFN component data for the patch panel include one or more data elements selected from the group of data elements comprising: GPS coordinates, a shelf location, a port identification, a loss for each port, a destination for each port, and a status of each port.

16. The RFID system of claim 12, wherein: the database unit includes a microprocessor having graphical user interface (GUI) capability and adapted to process the OFN component data stored in the database unit; and a display operably coupled to the processor unit and adapted to interactively display the OFN component data as processed by the microprocessor.

17. The RFK) system of claim 12, wherein at least one mobile RFED tag reader is adapted to read RFID tag signals from RFBD tags located underground.

18. The RFID system of claim 12, wherein the at least one mobile RFID tag reader automatically updates the OFN component data database.

19. A radio-frequency identification (RFID) system for deploying and/or maintaining and/or provisioning service and/or locating faults an optical fiber network (OFN) that is optically coupled to a central office (CO), comprising: at least one feeder-cable RFID tag fixed to a feeder cable that is optically coupled to the CO, with the at least one feeder-cable RFID tag having feeder-cable data relating to one or more properties of the feeder cable; at least one local convergence point (LCP) RFID tag fixed to a local convergence point (LCP) that is operably connected to the feeder cable, with the at least one LCP RFID tag having LCP data relating to one or more properties of the LCP; HE0347A at least one distribution-cable RFID tag fixed to a distribution cable that is operably coupled to the LCP, with the at least one distribution-cable RFID tag having distribution- cable data relating to one or more properties of the distribution cable; at least one network access point (NAP) RFID tag fixed to a NAP that is operably coupled to the LCP via the distribution cable, with the at least one NAP RFID tag having NAP data relating to one or more properties of the NAP; at least one network interface device (NID) RFID tag fixed to a NID that is operably coupled to the LCP via a drop cable, with the at least one NAP RFID tag having NID data relating to one or more properties of the NID; one or more mobile RFID tag readers adapted to read at least one of the feeder-cable RFID tags, the LCP RFED tags, the distribution-cable RFID tags, the NAP RFID tags, and the NID RFID tags, and provide corresponding feeder-cable data, LCP data, distribution-cable data, NAP data, and NID data; and an OFN component database unit adapted to receive and store the feeder-cable data, the LCP data, the distribution-cable data, the NAP data and the NID data.

20. The RFID system of claim 19, wherein the at least one mobile RFID tag reader is configured to automatically update the OFN-component-data database.

Description:
HE0347A

RFID SYSTEMS AND METHODS FOR OPTICAL FIBER NETWORK DEPLOYMENT AND MAINTENANCE

BACKGROUND

Cross-Reference to Related Application

[0001] This application claims the benefit of priority to U.S. Application No. 12/248,374, filed on October 9, 2008, which is a continuation-in-part of U.S. Application No. 11/638,812, filed on December 14, 2006.

Technical Field

[0002] The present invention relates to optical-fiber-based communication systems and networks, and particularly to systems and methods of deploying and maintaining and/or provisioning service and/or locating faults in optical fiber networks using radio-frequency identification (RFID) systems and methods.

Technical Background

Optical networks

[0003] The typical optical fiber network (OFN) includes one or more central offices (COs), one or more remote nodes (RNs) connected to the COs by corresponding optical fiber links, a number of network interface devices (NIDs) coupled to respective RNs by corresponding optical fiber links, and a number of termination points coupled to the NIDs by additional optical fiber links. There are a number of different types of OFNs, including long-haul networks that interconnect major metropolitan areas, regional networks that interconnect smaller cities to the long-haul backbone, metropolitan networks that interconnect central offices located within a city, enterprise networks that connect central offices to the buildings of large or small companies, and access networks that connect residential and business subscribers to central offices.

[0004] These networks have a variety of architectures, but each has common characteristics in that they comprise an interconnected set of electronic equipment, cables, hardware, and

I of 31 HE0347A components. For example, in access networks, there are a variety of broadband network architectures, which are described in more detail for illustration purposes. One general type of broadband access OFN is called an active point-to-point architecture, which includes the Home Run Fiber (HRF) and Active Star Ethernet (ASE). Another general type of broadband access OFN is called a passive point-to-multipoint architecture, which includes the Passive Optical Network (PON). A PON has no active components between the CO and the termination location to which the service is delivered.

[0005] Because of the different termination options for a broadband access OFN, for simplicity the abbreviated expression "fiber to the x" (FTTx) has been adopted, wherein the "x" represents the particular termination point. The termination point may be, for example, a "premise," a home, the "curb," or a "node." Thus, in the acronym-intensive language of OFNs, a PON architecture used to provide service to one or more homes is abbreviated as FTTH-PON. The details of the particular FTTx network architecture used depends on the termination point and the service goals of the network, as well as on network cost and the existing optical fiber related infrastructure ("outside plant" or OSP). In other OFN arrangements, some of the OFN components are located inside COs or inside other buildings and structures.

[0006] The deployment and maintenance of an OFN is an equipment-intensive and labor- intensive undertaking. A network service provider that receives the various components for the network from one or more manufacturers typically installs an OFN. The various OFN components (e.g., cabinets, terminals, enclosures, patch panel ports, optical fiber cable, optical fiber cable connectors, hardware, equipment, etc.) must be received, installed, inventoried, and maintained in an organized manner. After installation, the service provider must provide service to its customers and locate and correct any faults that occur in the network. Each of these operations (deployment, maintenance, provisioning, and fault location) requires the service operator to know and understand what OFN components are deployed in the network, as well as their location and particular capabilities.

[0007] hi OFN deployment, there is the need to positively identify and characterize the OFN components. This applies to the cabling (aerial or buried) as well as to the other HE0347A aforementioned OFN components. Currently, this process is carried out by visual identification, using foot markers printed on outside cable jackets, and color-coding and labeling of connectors, ports, enclosures, etc. During the initial installation as well as during operations and maintenance, significant time is spent associating the various OFN components and their characteristics to an inventory database, which is updated manually. Besides the extra time spent, there is a high risk of errors due to misidentification, database entry errors or failures to correctly update the database.

[0008] An OFN is typically deployed over a relatively large geographical area, with the optical fiber cables and other OFN components being installed either below ground or above ground. Thus, the ability to quickly locate and identify the various network components and obtain information about their installation and operating status can provide significant labor and cost savings with regard to deploying and maintaining the OFN, and can increase OFN uptime.

Radio-frequency identification

[0009] Radio-frequency identification (RFED) is a remote recognition technique that utilizes RFED tags having microcircuits adapted to store information and perform basic signal processing. The stored information is retrievable via RF communication between the RFID tag and a RFID tag reader. The typical RFED system utilizes a RFED tag reader (e.g., handheld) that when brought sufficiently close to a RFED tag is able to read a RFED tag signal emitted by the tag, usually in response to an interrogation signal from the RFID tag reader. One form of RFED tag relies on the interrogation signal from the RFED reader to provide power to the tag. Other forms of RFED tags have internal power sources.

[0010] The data encoded into a RFID tag can generally be written at a distance, and some types of RFED tags can be re- written multiple times. Each RFED application has its own unique issues and circumstances that require the RFID system to be engineered accordingly.

[0011] In view of the above-described issues associated with the deployment and maintenance of OFNs and the benefits of RFID technology, there is a need for systems and HE0347A methods that integrate RFED technology with OFNs to facilitate OFN deployment and maintenance.

SUMMARY

[0012] One aspect of the invention is a RFED method of deploying and/or maintaining and/or provisioning service and/or locating faults an optical fiber network (OFN). The method includes providing at least one RFED tag on at least one OFN component of a plurality of OFN components that constitute the OFN, and writing to at least one RFED tag using at least one RFED reader, OFN component data relating to at least one property of the corresponding OFN component. The method also includes recording and storing the OFN component data in an OFN-component-data database unit. The method further includes automatically updating the OFN-component-data database by reading OFN component data from the at least one RFED tag using the one or more RFED tag readers. Ln an example embodiment of the method, the one or more RFED tag readers are mobile and are adapted to be taken within a read range of the at least one RFED tag affixed to the at least one OFN component.

[0013] Another aspect of the invention is a RFED system for deploying and/or maintaining and/or provisioning service and/or locating faults in an OFN. The system includes at least one RFED tag affixed to at least one OFN component of a plurality of OFN components that constitute the OFN, wherein the at least one RFED tag affixed to the at least one OFN component contains OFN component data that relates to at least one property of the OFN component. The system also includes at least one mobile RFED tag reader adapted to be taken within a read range of the at least one RFED tag affixed to the at least one OFN component and read the OFN component data from the at least one RFED tag. The system further includes an OFN component data database unit adapted to receive and store OFN component data read by the at least one RFED tag reader. The system also includes the ability to automatically update the OFN-component-data database according to the OFN component data read from the at least one RFED tag. HE0347A

[0014] Another aspect of the invention is a RFED system for deploying and/or maintaining and/or provisioning service and/or locating faults in an optical fiber network (OFN) that is optically coupled to a central office (CO). The system includes at least one feeder-cable RFID tag fixed to a feeder cable that is optically coupled to the CO, with the at least one feeder-cable RFID tag having feeder-cable data relating to one or more properties of the feeder cable. The system also includes at least one local convergence point (LCP) RFID tag fixed to a local convergence point (LCP) that is operably connected to the feeder cable, with the at least one LCP RFLD tag having LCP data relating to one or more properties of the LCP. The system further includes at least one distribution-cable RFID tag fixed to a distribution cable that is operably coupled to the LCP, with the at least one distribution-cable RFID tag having distribution-cable data relating to one or more properties of the distribution cable. The system also includes at least one network access point (NAP) RFED tag fixed to a NAP that is operably coupled to the LCP via the distribution cable, with the at least one NAP RFED tag having NAP data relating to one or more properties of the NAP. The system additionally includes at least one network interface device (NID) RFED tag fixed to a NED that is operably coupled to the LCP via a drop cable, with the at least one NAP RFED tag having NED data relating to one or more properties of the NID. The system further includes one or more mobile RFED tag readers adapted to be taken within a read range of the at least one RFED tag affixed to the at least one OFN component and read at least one of the feeder-cable RFED tags, the LCP RFED tags, the distribution-cable RFID tags, the NAP RFID tags, and the NED RFED tags, and provide corresponding feeder-cable data, LCP data, distribution-cable data, NAP data, and NED data. The system also includes an OFN component database unit adapted to receive and store the feeder-cable data, the LCP data, the distribution-cable data, the NAP data and the NED data. The system also preferably includes the ability to automatically update the OFN-component-database according to the OFN component data read by the one or more mobile RFED tag readers.

[0015] Additional features and advantages of the invention will be set forth in the following detailed description, and in part will be readily apparent to those skilled in the art HE0347A from that description or recognized by practicing the invention as described herein, including the following detailed description, the claims, as well as the appended drawings.

[0016] It is to be understood that both the foregoing general description and the following detailed description present embodiments of the invention, and are intended to provide an overview or framework for understanding the nature and character of the invention as it is claimed. The accompanying drawings are included to provide a further understanding of the invention, and are incorporated into and constitute a part of this specification. The drawings illustrate various embodiments of the invention, and together with the description serve to explain the principles and operations of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0017] FIG. 1 is a general schematic diagram of an example embodiment of an OFN-RFID system according to the present invention, wherein the OFN is shown in the form of an FTTx- PON;

[0018] FIG. 2 is a detailed schematic diagram of an example embodiment of the central office (CO) of the OFN-RFED system of FIG. 1;

[0019] FIG. 3 is a detailed schematic diagram of an example embodiment of a local convergence point (LCP) of the OFN-RFID system of FIG. 1;

[0020] FIG. 4 is a detailed schematic diagram of an example embodiment of a network access point (NAP) of the OFN-RFID system of FIG. 1;

[0021] FIG. 5 is a detailed schematic diagram of an example embodiment of a RFID tag attached to a general OFN component, and also showing the details of an example RFID tag reader and an example database unit in operable communication therewith;

[0022] FIG. 6 is a schematic front-on view of an example splitter module rack that houses three splitter modules, wherein each splitter module includes a splitter-module RFBD tag;

[0023] FIG. 7 is a schematic front-on view of a single splitter module of FIG. 6, showing an example embodiment wherein each port has an associated port RFID tag; HE0347A

[0024] FIG. 8 is a schematic front-on view of an example patch-panel rack that houses six patch panels, wherein each patch panel includes a patch-panel RFED tag;

[0025] FIG. 9 is a close-up view of one of the patch panels of FIG. 8, illustrating the patch-panel ports and the patch-panel RFID tag;

[0026] FIG. 10 shows an example embodiment of an interactive OFN-RFED map as shown on the display of the database unit;

[0027] FIG. 11 illustrates an example embodiment wherein an OFN-RFID interactive map is shown along with a geographical map;

[0028] FIG. 12 shows an example information table as displayed on the database unit display when the cursor "clicks on" a distribution-cable RFID tag icon in the OFN-RFID map of FIG. 10;

[0029] FIG. 13 shows an example maintenance log table as displayed on the database unit display when the cursor "clicks on" the maintenance log icon of the information table of FIG. 12;

[0030] FIG. 14 shows the interactive OFN-RFID map of FIG. 10, but with the cursor moved to a the LCP active icon; and

[0031] FIG. 15 shows an example of a more detailed interactive map of the LCP and its components as displayed when the LCP icon in the OFN-RFID map of FIG. 14 is clicked on.

DETAILED DESCRIPTION

[0032] Reference is now made to present preferred embodiments, examples of which is/are illustrated in the accompanying drawings. Whenever possible, the same reference numbers or letters are used throughout the drawings to refer to the same or like parts.

[0033] The term "OFN component" as used herein is generally any component used in any type of OFN, and includes but is not limited to: a feeder cable, a distribution cable, a drop cable, a network access point (NAP), an enclosure, a splice box, a cabinet, a terminal, a patch panel, a patch cord, a fiber connector, an optical splitter, a splitter module, a coupler, an HE0347A optical amplifier, a wavelength multiplexer, a wavelength demultiplexer, an optical line terminal, a filter, a light source, an optical receiver, an optical transmitter, an intrafacility cable, a local convergence point (LCP), a network interface device (NID), a fiber distribution frame (FDF), an equipment module, or any other OFN-related hardware, including fiber- related hardware.

[0034] In the discussion below, the term "data" is used in the singular and represents a collection of one or more pieces of information. The term "RFID tag data" refers to data stored in or to be stored in a RFID tag, which data contains at least one property of the corresponding OFN component associated with the RFID tag.

[0035] Also, the term "electromagnetic signals" as used to describe the signals communicated between a RFED tag and a RFED reader includes free-space radio waves as well as magnetic inductive coupling.

[0036] For the sake of convenience, the following is a list of the acronyms used in this application:

[0037] OFN = optical fiber network

[0038] CO = central office

[0039] RFID = radio-frequency identification.

[0040] PON = passive optical network.

[0041] FTTx = "fiber-to-the-x," where "x" is the fiber cable endpoint.

[0042] LCP = local convergence point

[0043] NAP = network access point

[0044] NED = network interface device

[0045] GPS = global positioning system

[0046] OLT = optical line terminal

[0047] OSP = outside plant HE0347A

[0048] GUI = graphical user interface [0049] FDF = fiber distribution frame [0050] dB = decibels

The OFN-RFID system

[0051] FIG. 1 is a schematic diagram of an example embodiment of an OFN-RFID system 6 according to the present invention. OFN-RFID system 6 is interfaced with one or more components C n of an OFN 10 via one or more RFID tags T n , as described below. OFN- RFID system 6 is adapted to facilitate deploying and/or maintaining an OFN 10 by a service provider and their service personnel. OFN 10 as presented in FIG. 1 is in the form of a FTTx-PON for the sake of illustration. It will be understood by those skilled in the art that the present invention is generally applicable to all of the different types of active and passive OFNs and their respective physical plants.

[0052] With reference to FIG. 1, OFN 10 includes one or more COs 20, which is the main switching facility of the OFN. OFN 10 is shown with a single CO 20 for ease of illustration. Coupled to CO 20 are a number of external networks EN, such as for example the Internet IN for data and video services, and a public switched telephone network (PSTN) for telephone services, and a cable TV network (CATV) for entertainment video services. External networks EN provide CO 20 with external network signals SE that are distributed via the operation of the CO to select user sites (subscribers) of the OFN. FIG. 2 is a schematic diagram of an example embodiment of CO 20 that includes a number of OFN components adapted to take incoming external network signals SE and establish temporary connections to select optical fibers in the OFN in order provide the external network signals to the OFN subscribers. CO 20 includes, for example, an optical line terminal (OLT) 26 that interfaces with the external networks EN. OLT 26 is adapted to processes external signals SE and send them to a fiber distribution frame (FDF) 30 via a cross-connect patch cord 36. FDF 30 is connected to a fiber entrance cabinet 40 via an intrafacility cable 46. Fiber entrance cabinet 40 is connected to the outside cable plant (OSP), i.e., feeder cables 50 and the rest of the HE0347A

OFN, as discussed below. Alternatively, fiber entrance cabinet 40 is connected to feeder cables 50 that in turn connect to another CO 20, in order to allow the signals SE to be interconnected among multiple COs 20. The cables 50 may include splice boxes, enclosures, manholes, optical amplifiers, repeaters, and the like, that allow the cable distances to span long enough distances for metropolitan interoffice networks, regional networks, and long-haul networks.

[0053] With reference again to FIG. 1, OFN 10 also includes at least one feeder cable 50, with each feeder cable optically coupled at one end to CO 20 and at the opposite end to a local convergence point (LCP) 100. Feeder cable 50 may have over 100 optical fibers 52.

[0054] OFN 10 also includes one or more distribution cables 110 operably coupled to a given LCP 100, with each distribution cable including one or more optical fibers 112. Note that feeder cable(s) 50 and distribution cable(s) 110 may be either buried or supported above ground.

[0055] FIG. 3 is a schematic diagram of an example LCP 100. LCP 100 includes a distribution cabinet 120 that houses a splitter module 130 having a number of ports P. A typical number of ports is either 16, 32 or 64. Splitter module 130 includes one or more splitters (not shown). LCP 100 also includes a patch panel 140 that terminates optical fibers 52 in feeder cable 50 and facilitates access thereto by splitter module 130.

[0056] With reference again to FIG. 1, OFN 6 includes at least one network access point (NAP) 200, with each optically connected to a corresponding LCP 100 via a corresponding distribution cable 110. OFN 6 also includes one or more drop cables 220 operably coupled to NAP 200. Each optical drop cable 220 includes one or more optical fibers 222.

[0057] FIG. 4 is a schematic diagram of an example embodiment of NAP 200. NAP 200 includes a distribution cabinet 120 that houses passive optical components, such as patch panel(s) 140 that includes splice trays and/or connector ports for receiving a preconnectorized distribution cable 110 and a preconnectorized drop cable 220. For the sake of illustration, connector ports P are shown. Patch panel 140 serves to distribute incoming signals from the individual optical fiber 112 of distribution cable 110 to one or more drop cables 220 and the HE0347A individual optical fibers 222 therein. Other example embodiments of NAPs 200 may include other OFN components, such splitters 130, making them similar to LCPs 100 of FIG. 3.

[0058] With reference again to FIG. 1, each drop cable 220 is optically coupled to a network interface device (NID) 300. NID 300 (also called a network interface unit, or NTLJ) is located at a user site 310. NTD 300 includes electrical and/or optical components (not shown) that enables a user at user site 310 to connect to OFN 6.

RFID tags in OFN-RFID system

[0059] With continuing reference to FIG. 1, OFN-RFID system 6 includes at least one RFID tag provided to (e.g., fixed or otherwise attached to) at least one OFN component, and at least one RFID tag reader 400 adapted to read RFID tags. OFN-RFID system 6 also includes an OFN component data database unit 410 (hereinafter, "database unit") in operable communication with RFID tag reader 400. To associate RFID tags with given components, the reference letter T n is used to represent a RFID tag, where the subscript "n" is the reference number of the corresponding OFN component, generally referred by the reference letter C n .

[0060] FIG. 5 is a detailed schematic diagram of an example embodiment of a RFID tag T n attached to OFN component C n (e.g., RFID tag T 20O attached to NAP 200 as shown in FIG. 1 and in FIG. 4). FIG. 5 also shows details of RFID tag reader 400 and Database unit 410. RFID tag T n includes a microcircuit 450 (e.g., in the form of a microchip) electrically connected to a memory unit 452 and to a receive/transmit antenna 454. Memory unit 452 is adapted to store information ("RFID tag data"), which includes at least one property of the associated OFN component, but more typically includes a number of such properties. Typical RFID tag data includes, for example, the type of component to which the RFID tag is affixed, the component manufacturer, the manufacturer part number, the date of component manufacture, the date of component installation, the component's operational status, component maintenance information and history, component location in the OFN (e.g., global positioning system (GPS) coordinates), a part or other identification number, and so on. HE0347A

[0061] Microcircuit 450 is adapted to receive an electromagnetic RFID-tag interrogation signal SI" emitted by RFED reader via antenna 480 and to process this signal. The processing includes comparing the received interrogation signal SI" to a corresponding bit sequence stored value in memory unit 452. In an example embodiment, microcircuit 450 is adapted to use the energy in the interrogation signal to power itself. If the content of the received interrogation signal SI" is confirmed, then microcircuit 450 is adapted to generate a RFID tag signal ST n representative of the stored RFED tag data and to transmit this signal to RFED reader 400 as an electromagnetic tag signal ST n " to be read by RFED tag reader 400.

[0062] In an example embodiment, one or more of the RFED tags are adapted to generate electromagnetic RFED tag signals at a frequency that is not significantly affected by soil or water, such as in the frequency range from 100 KHz to 125 KHz. This is so that the RFED tag signal can be read even though the corresponding OFN component is buried underground or covered by water. Here, the electromagnetic RFED tag signals are based on magnetic inductive coupling. Suitable RFID tags and associated RFED tag readers are available from 3M Corporation.

[0063] Also in an example embodiment, at least some of the RFED tags are adapted to generate RFED tag signals at a frequency suitable for long-range RFID-tag reading, such at the 915 MHz band or the 2.45 GHz band. Such RFED tags are best suited for aerial or aboveground OFN components, or more generally for OFN components that are not buried or otherwise obstructed by an intervening RF-frequency-absorbing medium. Suitable RFID tags are available from Alien Technologies, Inc., as Model Nos. ALL-9440 and ALL-9350.

[0064] Ln an example embodiment, RFID tag reader 400 and one or more of RFID tags T n are adapted with encryption capability so that the interrogation signal and the RFED tag signal can be encrypted to prevent third parties from reading or overwriting RFID tag data.

Example RFID tag reader

[0065] With continuing reference to FIG. 5, an example embodiment of RFID tag reader 400 includes a receive/transmit antenna 480, a signal processing circuit 482 electrically HE0347A connected thereto, and a memory unit 484 electrically connected to the signal processing circuit. RFID tag reader 400 also includes other electronic components that not essential to the present invention and so are not shown, hi an example embodiment, RFID tag reader 400 includes a GPS circuit 486 adapted to provide GPS data to signal processing circuit 482 and/or to memory unit 484.

[0066] Signal processing circuit 482 is adapted to generate interrogation signal SI and transmit it via antenna 480 to RFID tag T n as an electromagnetic interrogation signal SI". Signal processing circuit 482 is also adapted to write information to RFED tag T n based on information either stored in memory unit 484, entered into the RFID tag reader directly by a user, or communicated to it from database unit 410, as described below.

[0067] RFID tag reader 400 is also adapted to receive electromagnetic RFID tag signal ST n " via antenna 480, which converts this signal back to electrical RFBD tag signal ST n . Signal processing circuit 482 is further adapted to extract the RFID tag data from this signal and store this data in memory unit 484 and/or transmit this data to database unit 410.

Example database unit

[0068] In an example embodiment, RFID tag reader 400 is operably coupled to database unit 410 so that it can transmit information to and receive information from the database unit. La an example embodiment, database unit 410 includes a second transmit/receive antenna 494 used to wirelessly communicate with RFBD tag reader 400, through a Wi-Fi network or through the cellular phone network, as examples, hi another example embodiment, database unit 410 is operably coupled to RFID tag reader 400 via a non-wireless (e.g., an electrical or optical) communication link 492, such as an Ethernet link, hi an example embodiment, RFID tag reader 400 is mobile (mounted on a vehicle or carried by service personnel) and is brought out to the field so as to be accessible to those working in the field to deploy or maintain or provision service or locate faults in the OFN 10.

[0069] Database unit 410 includes a microprocessor 500 operably connected thereto, a memory unit 510 operably coupled to the microprocessor, and a display 520 operably coupled HE0347A to the microprocessor. In an example embodiment, database unit 410 is or otherwise includes a computer, such as a laptop computer, personal computer or workstation. In an example embodiment, database unit 410 is mobile (e.g., as a laptop computer or hand-held device) and is brought out to the field so as to be accessible to those working in the field to deploy or maintain OFN 10. Also in an example embodiment, database unit 410 supports a graphical user interface (GUI) so that a database-unit user can view graphical images and interact with interactive graphical images on display 520.

[0070] hi an example embodiment, RFED tag reader 400 transmits RFID tag data to database unit 410 either non-wirelessly via a non-wireless data signal SD sent over communication link 492, or wirelessly via electromagnetic data signal SD". Database unit 410 then stores and processes the RFID tag data, such as described below.

[0071] Also in an example embodiment, database unit 410 either wirelessly and/or non- wirelessly transmits write information in respective information signals SW and/or (electromagnetic) signal SW" to RFID tag reader 400. The write information in signals SW or SW" is then written by RFID tag reader 400 to one or more RFID tags T n and stored therein as RFED tag data.

[0072] Microprocessor 500 in database unit 410 is adapted to process the RFED tag data to create useful information about the status of OFN 10 and OFN components C n . In an example embodiment, this information is displayed on display 520. Ln an example embodiment, the information is represented as graphics, and further is presented by database unit 410 in the form of one or more interactive OFN-RFED maps. The OFN-RFED maps may include, for example, component inventory data, component location data, component connectivity data and/or component status data. Example interactive OFN-RFED maps for facilitating the deployment and maintenance of OFN 10 are discussed in greater detail below.

CO RFID tags

[0073] FIG. 1 shows a number of RFID tags T n attached to different OFN components C n of OFN 10. With reference also to FIG. 2, CO 20 includes a OLT-RFID tag T 26 affixed to HE0347A

OLT 26. OLT RFID tag T 26 includes, for example, information relating to the manufacturer, manufacturer model number, date of installation, the last maintenance performed, what was performed during the last maintenance, what the next maintenance is and when it is scheduled, the number of PONs served by the OLT, the number of connections to external networks EN, the types of external networks served, the exact location of the OLT in the CO, communication protocols used, etc.

[0074] CO 20 also includes a patch-cord RFED tag T 36 attached to patch cord 36 and a intrafacility-cable RFID tag T 46 . These RFID tags include, for example, information relating to the manufacturer, manufacturer part number, date of installation, the number of connections, type of fiber, etc.

[0075] CO 20 also includes an FDF RFTD tag T 30 attached to FDF 30 and a cabinet RFID tag T 40 attached to entrance cabinet 40. These RFID tags include, for example, information relating to the manufacturer, manufacturer part number, date of installation, the number of connections, location of the frame or cabinet, etc.

Feeder cable RFID tags

[0076] With reference again also to FIG. 1, OFN-RFID system 6 includes a number of feeder-cable RFID tags T 50 attached to feeder cables 50. In an example embodiment, feeder- cable RFID tags T 50 are arranged along the length of each feeder cable 50 (e.g., at fixed intervals) and include information such as their respective GPS position information, the status of the feeder cable, the number of optical fibers 52 in the feeder cable, the last maintenance operation, feeder cable manufacturer, feeder cable manufacturer model number, the location and type of LCP to which the feeder cable is connected, the length of cable, the distance between cable RFID tags, etc. In another example embodiment, feeder-cable RFID tags T 50 are located at certain important locations, such as splice locations.

[0077] Feeder cable RFID tags T 50 may also include information relating to the installation of feeder cables 50, such as the planned installation destination, installation date, special instructions regarding the installation (e.g., aerial or buried cable), and the like. HE0347A

LCP RFID tags

[0078] OFN-RFBD system 6 also includes a number of LCP RFED tags. In an example embodiment, a main LCP RFED tag Tioo is attached to the OSP distribution cabinet 120 and contains information relating to the general properties of LCP 100, such as the cabinet location, operational status of the LCP, manufacturer information, maintenance status, the number and type of internal OFN components, etc. A splitter-module LCP RFID tag Too is attached to splitter module 130.

[0079] FIG. 6 is a detailed face-on diagram of an example splitter module rack 554 that houses three splitter modules 130. Each splitter module 130 has a number of splitter ports P. Twelve such splitter ports Pl through P12 are shown for the sake of illustrations. Other numbers of splitter ports, such as 32 and 64 are also often used. A splitter-module RFED tag Ti 30 is attached to each splitter module 130. hi an example embodiment, each splitter module 130 also includes a conventional ED tag 556 with a tag ID number that identifies the splitter module, e.g., by its shelf location in splitter module rack 554. This conventional ED tag can be placed directly on the RFED tag T 130 , as shown.

[0080] Ln an example embodiment, RFED tag Too includes a light 560 (e.g., a light- emitting diode (LED)) that activates when the particular RFED tag Too is interrogated by RFID tag reader 400. This helps identify which one of the RFED tags Too is being interrogated and read at a given time.

[0081] Table 1 below presents an example embodiment of RFED tag data stored in the splitter-module RFED tag To 0 for splitter module ID# 124290. For the sake of illustration, only the data for the first six ports Pl- through P6 is shown.

HE0347A

[0082] Table 1 includes the shelf ID number — here, ED number 124290 chosen for illustration purposes — that identifies the splitter-module RFED tag as being located in a particular shelf of splitter module rack 554. Table 1 includes the following information for each port: The 1310 nm loss (dB), the 1550 nm loss (dB), the street name served by the port, the street address served by the port, the pole number associated with the port, the GPS coordinates of the location served by the port, and "other information" that can be added to the RFED tag as needed, such as the operating status or the maintenance status. Generally speaking, data can also be written to the RFED tag via RFED reader 400 so that the data can be updated as needed. In an example embodiment, RFED tags T^o contain default deployment data written to the RFED tag prior to the deployment of LCP 100 or the installation of splitter module 130 in the LCP.

[0083] Ln another example embodiment illustrated in FIG. 7, each splitter module 130 includes a port RFED tag Tp for each splitter port P. Port RFED tags Tp contain, for example, information about the status of the corresponding port P and its connectivity.

[0084] FIG. 8 is a detailed face-on diagram of an example patch-panel rack that includes a number of patch panels 140. Each patch panel 140 includes a patch-panel RFED tag T^o attached thereto. As with splitter-module RFED tag T^o, patch-panel RFID tag T 140 includes in an example embodiment a light 556 activated by microcircuit 450 when the patch-panel RFED tag is interrogated by RFED tag reader 400. Patch-panel RFED tag T 1 4 0 also includes a conventional ID number that indicates the patch panel's shelf location in patch-panel rack 600. HE0347A

[0085] FIG. 9 is a close-up front-on view of patch panel 140, showing patch-panel RFID tag Ti 4 o and patch-panel ports Pl through P6. Table 2 below presents an example embodiment of data stored in patch-panel RFBD tag T 14O for patch-panel ID # 13425 of FIG. 8.

[0086] Table 2 includes the patch-panel ID number — here, ID number 13425, chosen for illustration purposes. Table 2 also includes the patch-panel port number Pl through P6, the loss per port (in dB), and the OSP location information. Other information, such as building name, room number, subscriber location, street address, power levels, maintenance schedules, and the like can be included in Table 2. Alternately, it is possible to have a separate RFID tag, with one for each port number Pl through P6, that contains all of the data pertinent to its associated port.

[0087] Here, it is emphasizing that the prior art approach to OFN deployment and maintenance involves obtaining such information by inspection and previous written documentation, and then documenting the updated information on paper. The paper documents are then distributed to provide information about the maintenance history of OFN components C n such as splitter module 130 and patch panel 140. With RFID tags, this paper documentation is replaced by the data written into the RFID tags, and is available instantly at the point of use and at any time it is needed. HE0347A

Distribution-cable RFID tags

[0088] With reference again to FIG. 1, OFN-RFID system 6 includes a number of distribution-cable RFID tags Tno attached to distribution cables 110. In an example embodiment, distribution-cable RFID tags Tno are arranged along the length of each distribution cable 110 (e.g., at fixed intervals). Distribution-cable RFID tags Tno include information such as their respective GPS positions, the status of the distribution cable, the number of optical fibers 112 in the distribution cable, the distance between RFID tags, the last maintenance operation, the distribution-cable manufacturer, distribution-cable manufacturer model number, the location and type of LCP 100 and NAP 200 to which the distribution cable is connected, etc. In another example embodiment, distribution-cable RFID tags Ti 1O are located at certain important locations, such as splice locations.

[0089] Distribution-cable RFBD tags Tno may also include information relating to the installation of distribution cables 110, such as the planned installation destination, installation date, special instructions regarding the installation (e.g., aerial or buried cable), and the like.

NAP RFID tags

[0090] OFN-RFID system 6 also includes a number of NAP RFID tags. A main NAP RFID tag T 2 oo is attached to the distribution cabinet 120 and contains information relating to the general properties of NAP 200, such as the cabinet location, operational status of the NAP, manufacturer information, maintenance status, the number and type of internal OFN components, etc.

[0091] The other NAP RFID tags for NAP 200 are essentially the same as those for LCP 100 since the NAP typically includes the same OFN components — namely, splitter module(s) 130 and patch panel(s) 140.

Drop-cable RFID tags

[0092] With reference to FIG. 1, OFN-RFID system 6 includes a number of drop-cable RFID tags T 22 o attached to drop cables 220. In an example embodiment, drop-cable RFID HE0347A tags T 22 o axe arranged along the length of each drop cable 220 (e.g., at fixed intervals). Drop- cable RFID tags T 22 o include information such as their respective GPS positions, the distance between successive RFED tags, the status of the drop cable, the number of optical fibers 112 in the drop cable, the last maintenance operation, the drop-cable manufacturer, drop-cable manufacturer model number, the location and type of NAP 200 and NID 300 to which the drop cable is connected, etc. hi another example embodiment, drop-cable RFED tags T 22 o are located at certain important locations, such as splice locations.

[0093] Drop-cable RFID tags T 22 o may also include information relating to the installation of drop cables 220, such as the planned installation destination, installation date, special instructions regarding the installation (e.g., aerial or buried cable), and the like.

NID RFID tags

[0094] OFN-RFED system 6 also includes a number of NED RFED tags. A main NED RFED tag T 300 is attached to cabinet 120 and contains information relating to the general properties of NED 300, such as the cabinet location, operational status of the NED, manufacturer information, maintenance status, the number and type of internal OFN components, etc.

[0095] Other NED RFED tags are provided to the corresponding NED OFN components in analogous fashion to the LCP RFID tags described above. In an example embodiment, the other NED RFED tags are essentially the same as those for LCP 100 in the case where the two have the same or similar OFN components.

RFID Mapping of the OFN

[0096] As discussed above, an example embodiment of the present invention involves using OFN RFED tags T n to create one or more OFN-RFED maps of OFN 10 based on the RFID tag data read from the OFN RFED tags. En one example embodiment, OFN RFED tags T n are provided with data relating to the deployment of the corresponding OFN components C n prior to OFN 10 being deployed. In one example, the OFN RFED tag data is written to the corresponding RFID tags by the OFN component manufacturer and/or by the OFN installer (service provider). For example, for cable assemblies that are factory terminated and customized for installation in a particular location, the location information can also be HE0347A written in the RFED tags. RFID tags on the cable reel or cable assembly reel can also contain information about their installation destination, as required.

[0097] The OFN RFtD tag data is then read from the OFN RFED tags using RFED tag reader 400 prior to or during deployment. In an example embodiment, the service provider receives materials from the OFN component supplier and scans all tagged OFN components. This information is then added to the inventory database unit of database unit 410. At this point, the service provider may choose to replace the manufacturer identification and the identification number written to the RFED tag by the manufacturer with its own identification number, which uniquely identifies this tag within its entire inventory of assets. The original identification number and the manufacturer code can be stored in the inventory database unit so that each entity can still be traced back if necessary. This enables the full capability and capacity of the manufacturing database collection to be searched to determine the characteristics and performance of the component in more detail than can be written into the RFID tag. Such manufacturing data can be retrieved remotely, for example, via the Internet or via a cellular phone network. This information can be further updated at the time of installation, to add additional details of interest to the network operator, such as the association between ports and connectors.

[0098] The OFN RFID tag data, which is collected in memory unit 510 of database unit 410, is processed via microprocessor 500 to provide a representation of the OFN RFED tag information from the various OFN RFED tags, such as an OFN map.

[0099] Ln an example embodiment, the information stored in the OFN RFED tags T n includes positional information (e.g., GPS coordinates) for the OFN components C n . The positional information is, for example, originally provided by GPS circuit 486 and written to the OFN RFID tags T n by RFED tag reader 400 during installation of the OFN component. Service personnel can use the RFID tag reader, either mounted on vehicles or as hand-held units, at the field location to read and write the GPS and OFN component data to the associated OFN RFED tags T n . Writing of GPS information can be carried out, for example, by OFN service personnel working in the field while installing, maintaining or repairing the OFN. For example, the GPS information can also be added to the RFID tag data by RFID HEΘ347A tag reader 400 during the RPED tag reading process after OFN deployment (e.g., by OFN service personnel) and sent to the database unit along with the read RFID tag data. Updating of the RFID tag data and the database data can be done manually by service personnel or automatically by the RFID tag reader 400. This allows the map to show in detail the precise locations of the OFN components, as well as the spatial relationships between OFN components in the OFN.

[00100] hi a similar manner, an OFN inventory map is created that shows the location (e.g., via GPS coordinates) and the corresponding part number for each OFN component C n in OFN 10. In an example embodiment, the OFN inventory map includes information about not only installed OFN components, but spare OFN components as well, such as availability, location, etc.

[00101] hi another example embodiment, an OFN maintenance map of OFN 10 is created by writing to one or more of the OFN RFID tags T n maintenance information for the corresponding OFN components C n . The maintenance map includes, for example, maintenance that needs to be performed and/or maintenance that has already been performed. By updating OFN RFID tags T n using one or more RFID -tag readers 400 and transmitting the updated OFN RFED tag information from the one or more RFED tag readers to database unit 410, an updated maintenance map is established. Such an updated maintenance map can be viewed on display 520 of database unit 410 and used to plan and schedule OFN maintenance.

[00102] En an example embodiment, both inventory and maintenance maps are used in combination when performing OFN maintenance, since inventory issues often arise in connection with performing OFN maintenance. FIG. 10 shows an example of an interactive OFN-RFID map 700 as shown on display 520 of database unit 410. OFN-RFED interactive map 700 shows a portion of OFN 10. The GUE functionality of database unit 410 allows a cursor 710 to be moved by a user to the various OFN components, which serve as active icons that can be "clicked on" to reveal the RFlD tag information corresponding to the particular OFN component. HE0347A

[00103] FIG. 11 illustrates an example embodiment of the present invention wherein an OFN-RFED interactive map 700 is overlaid or shown along with a standard geographical map 800 (e.g., a GPS-based map). The spatial layout of at least a portion of OFN 6 and the location of the various OFN-RPIG tags T n is viewable in the context of the local geography, which includes roads, building, geographic features, etc. This allows for the OFN components to be positioned on the map so that the field service personnel can easily locate the components, and can find the physical location of faulty OFN components, or can identify which OFN components are causing the fault by knowing their position on the map. Service personnel can also use the OFN component locations on the map to simplify provisioning of service to customers. It is worth emphasizing here that locating OFN components in the field is a time-consuming job. Even after a particular component is found, one may not be sure it is the correct one. The RFID tag for the particular OFN component provides the field operator with positive confirmation that they have indeed found the correct component.

[00104] FIG. 12 is an example schematic diagram of a table 720 (similar to Tables 1 and 2, set forth above) as displayed on display 520 when cursor 710 is used to click on a RFID tag Tioo icon in OFN-RFID map 700 of FIG. 10. Table 720 includes the RFID tag data of clicked-on RFID tag Tno. The example RFED tag data includes the RFED tag ID serial number, the GPS location, the distance to the nearest LCP 100, the distance to the nearest NAP 200, the type of cable, the cable part number, the date of installation, and who installed the cable. Table 720 also includes one or more active icons, such as a maintenance log icon 730 that, when clicked on, displays additional RFID tag data regarding the maintenance performed.

[00105] FIG. 13 is an schematic diagram of an example maintenance log 740 that is displayed on display 520 when maintenance log icon 720 of FIG. 12 is clicked. Service personnel use the RFED tag data and GPS location data to locate the fault or OFN component needing maintenance, make the necessary repairs, and/or automatically write maintenance or repair data into the RFID tag Tno. Maintenance log 740 shows example maintenance RFID tag data, such as the RFID tag ID serial number, the GPS location of the RFID tag, the date a maintenance problem was reported, the nature of the problem identified, what repair was HE0347A performed and when, when the system was placed back in operation, who effected the repair, and what parts were used to make the repair.

[00106] FIG. 14 shows the interactive OFN-RFID map 700 of FIG. 10, but with cursor 710 moved to the LCP 100 active icon. FIG. 15 illustrates a second interactive map 750 (adapted from FIG. 3) of LCP 100 that is displayed on display 520 when the LCP 100 icon of FIG. 14 is clicked on. Interactive map 750 shows the different OFN components of LCP 100 as described above in connection with FIG. 3.

[00107] Each of the RFBD tags T n in interactive map 750 are active icons that can be clicked on to display the corresponding RFID tag data. For example, clicking on RFID tag T 130 displays Table 1 as shown and discussed above in connection with splitter module 130. Likewise, clicking on RFID tag T 14O displays Table 2 as shown and discussed above in connection with patch panel 140. Interactive map 750 also includes a general LCP RFID tag Tχ 2 o icon that can be clicked on to display general RFED tag data generally concerning the corresponding LCP 100.

[00108] As discussed above, in an example embodiment, database unit 410 is portable, allowing it to be taken into the field by those deploying or maintaining OFN 10. The RFID tag reader 400 is also portable, being mounted on a vehicle or hand-held, allowing it to be taken into the field by those deploying or maintaining OFN 10. This provides for real-time processing of OFN deployment and maintenance RFID tag data during the deployment or maintenance activity.

[00109] The automated tracking of OFN components afforded by the present invention reduces the risk of misidentification and errors that often accompany manual updates of an OFN component inventory database. The present invention also allows for automated updating of RFID tag data and associated OFN-component-data database entries. The present invention also provides for faster and more accurate installation, provisioning operations, fault location and maintenance of the OFN.

[00110] 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 HE0347A 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.




 
Previous Patent: WO/2010/042807

Next Patent: ADAPTIVE KNOWN SIGNAL CANCELLER