Network management systems for use with physical layer information.

(54) Title: NETWORK MANAGEMENT SYSTEMS FOR USE WITH PHYSICAL LAYER INFORNATION. (54) Title: NETWORK MANAGEMENT SYSTEMS FOR USE WITH PHYSICAL LAYER INFORMATION.

(57) Summary

An exemplary embodiment is directed to a network management system that uses information from the physical layer to perform a network management function. Another exemplary embodiment is directed to a method of tracking channel compliance using information from the physical layer.

(57) Abstract

One exemplary embodiment is directed to a network management system that uses physical layer Information in performing a network management function. Another exemplary embodiment is directed to a method of tracking channel compliance using physical layer Information.

<img file="MX337306B_D0001.tif" />

Institute

Mexican Property

Industrial

<img file="MX337306B_D0002.tif" />

PATENT TITLE NO. 337306

Owner (s): ADC TELECOMMUNICATIONS, INC.

Address: 13625 Technology Drive, Eden Prairie, Minnesota, 55439, USA

Name: NETWORK MANAGEMENT SYSTEMS FOR USE WITH PHYSICAL LAYER INFORMATION.

Classification: IC 8: H04L12 / 24

Inventor (s): MOHAMMAD RAZA; KAMLESH PATEL; JOHN ANDERSON; JOSEPH COFFEY

REQUEST

Number:

MX / a / 2015/008658

Internal filing date February 2010

Divisional Patent Number: 331284

Country: ΐ

US

W -TR

Validity: Twenty years

Expiration Roof »

Reference patent &amp; grant co

-Lie conformity with article 23 of i _. / counted from the fedfia for the provision of rights.

.Who subscribes the present title what Industrial Property (Official Diaf ^ b c

PRIORITY

Date:

February 2009

<img file="MX337306B_D0003.tif" />

2030 .2nd fraction V, 6th fraction based on the Federation (DOF /

Number:

61 / 152,624, and 69 of the Industrial Property Law (patent present) has a valid term of twenty unenforceable years, «and will be subject to the payment of the fee to maintain the eff ents provided by the articles. / 06 ^ 1991. reformed on 02.

lll and 7 ° bis 2 of li 25/10/1996, 12/26/1997, 1 ey of the /5 / 1999,

-26/01/2004, 06/16/2005, »/ 01/2006, 6/05 / 2009,06 / 01/2010, 06/18/2010, 06/23/2010, 07/07/2012 and 04/09 / 2012); articles 1, 3 ration V

<img file="MX337306B_D0004.tif" />

it is I and Ill 28/07/2004 and

signed the Organic 3 of the Mexican Institute of Industrial Property (DOF 12/27/1999, amended on 10/10/2002, 07/29/2004, 08/04/2004 and 09/13/2007); 1, 3 and 5 subsection a) of the Agreement that delegates powers to the Deputy Directors General, Coordinator, Divisional Directors, Holders of the Regional Offices, Divisional Deputy Directors, Departmental Coordinators and other subordinates of the Mexican Institute of Industrial Property. (DOF 12/15/1999, amended on 02/04/2000, 07/29/2004, 08/04/2004 and 09/13/2007).

<img file="MX337306B_D0005.tif" />

Issue Date: February 24, 2016

THE DIVISIONAL DIRECTOR OF PATENTS

I

Ί

NAHANNY CANAL REYES

Arenal No. 550. Floor 1_;

Tol. Santa María Tepepan town.

Xochirnílco. CP 16020,

Mexico City

Tel. (55; 53 34 07 00 \ s ^ y.; Jmp.i.¿ /; oí) ,. n) x

<img file="MX337306B_D0006.tif" />

MX72016 / 15089

<img file="MX337306B_D0007.tif" />

aotsfeé'SS

IMPI

NETWORK MANAGEMENT SYSTEMS FOR USE ^,¿S030®Ía ^ t6tf .. 'J OF PHYSICAL LAYER

CROSS REFERENCES TO RELATED REQUESTS

This application claims the priority of US provisional patent. Minutes No. filed on February 13, 2009, which to this document by reference.

application

61 / 152,624, incorporated

BACKGROUND

Communication networks typically include numerous logical communication links between various pieces of equipment. Often, a single logical communication link is implemented using different pieces of physical communication media. For example, a logical communication link between a computer and a network interconnect device such as a hub or router can be implemented as follows. A first cable connects the computer to a wall-mounted outlet. A second cable connects the wall-mounted socket to one port on a patch panel, and a third cable connects the network interconnect device to another port on a patch panel. A junction of connecting cables connects them both. In other words, a single link is normally implemented

<img file="MX337306B_D0008.tif" />

logical communication that uses varXQ &amp;, „physical media segments.

A business or network management system (generally referred to here as a network management system or NMS) is typically aware of the logical communication links that exist on a network, but typically has no information about the means of communication. specific physical layer used to implement logical communication links. In fact, NMS systems typically do not have the ability to display or otherwise provide information on how logical communication links are implemented at the physical layer level.

There are Physical Layer Management (PLM) systems. However, existing PLM systems are typically designed to facilitate adding, changing, and removing cross connections on a particular patch panel or patch panel group at a given location. In general, such PLM systems include the functionality of tracking what is connected to each port on a patch panel, tracing the connections made using a patch panel, and providing visual prompts to a user on a patch panel. However, said

<img file="MX337306B_D0009.tif" />

PLM systems are typically focused on patch panels because they focus on helping a technician add, change, or remove cross connections on a patch panel. All intelligence included or coupled to the patch panel is typically designed only to facilitate accurate cross-connection connections at the patch panel and troubleshooting problems (for example, detecting if a patch cord has been inserted into a given port and / or determining which ports are coupled to each other using a connecting cable).

Furthermore, all the information that such PLM systems collect is typically only used in PLM systems. In other words, the collections of information that these PLM systems maintain are logical islands that are not used at the application layer level by other systems. Despite the fact that such PLM systems sometimes connect to other networks (for example, they connect to local area networks or the Internet), such network connections are typically only used to allow the user to remotely access the PLM systems. That is, a user remotely accesses the alignment layer functionality »

IMPL

MEXICAN INSTITUTE OF Industrial .HEOaD

<img file="MX337306B_D0010.tif" />

PLM-related application that — gas-i Ha in the PLM system itself using the external network connection, but external systems or networks typically do not themselves include any application layer functionality that uses information related to the physical layer that resides in the PLM system.

COMPENDIUM

An exemplary embodiment is directed to a network management system (NMS) comprising an interface that communicatively couples the NMS to a network and a programmable processor configured to run the software. The software comprises a Physical Layer Information (PLI) functionality that receives information from the physical layer. NMS uses at least a portion of the physical layer information to develop a network management function. At least a portion of the information in the physical layer is read from a storage device included in or on a physical communication medium.

Another exemplary embodiment addresses a method that is developed when a channel is certified to meet at least one channel specification. The method includes receiving information on compliance with the

<img file="MX337306B_D0011.tif" />

INSTITOR

MEXICAN

OF THE fXOFlEOAO ^D INDUSTRIAL components used to implement the channel with less than one component specification and receive compliance information on a permalink used to implement the channel with at least one permalink specification. The method further includes receiving information on the compliance of the channel with at least one channel specification and determining, through the use of the physical layer information associated with the components used to implement the channel at that time, whether the basis for Channel compliance certification with at least one channel specification has changed since channel compliance was certified with at least one channel. The information in the physical layer associated with the components used to implement the channel at that time includes the information stored in or about the component that identifies the components.

The details of the various embodiments of the claimed invention are set forth in the connected drawings and the following description. Other features and advantages will be apparent from the description, the drawings and the claims.

<img file="MX337306B_D0012.tif" />

DRAWINGS

FIG. 1 is a block diagram of an exemplary embodiment of a system that includes the Physical Layer Information (PLI) functionality as well as the Physical Layer Management (PLM) functionality.

FIG. 2 is a block diagram of a high-level embodiment of a port and a media read interface that are suitable for use in the network system.

FIG. one.

FIG. 3 illustrates an exemplary embodiment of a system that includes the Physical Layer Information (PLI) functionality as well as the Physical Layer Management (PLM) functionality.

FIG. 4 is a block diagram of an exemplary embodiment of each slave processor module shown in FIG. 3.

FIG. 5 is a block diagram of one embodiment of the master processor unit of FIG. 3.

FIG. 6 is a diagram illustrating an embodiment of a connection cable that is suitable for use in the system of FIG. 3.

~ · Λ^:Λ 'Τ -' ΧΤ '.--.

; , / i X;!

: X .; __

FIG. 7 is a diagram illustrating another exemplary embodiment of a connection cable that * is ™ adécüá &lt;3ópara ”use in the system of FIG. 3.

FIG. 8 is a block diagram of one embodiment of an aggregation point.

FIG. 9 is a block diagram of an embodiment of a network management system (NMS) that is specially configured to use the physical layer information that is captured and aggregated using the techniques described herein.

FIG. 10 is a flow chart of an exemplary embodiment of a compliance monitoring method in a network that includes the physical layer information functionality.

FIG. 11 is a block diagram of an embodiment of a network interconnect device that is specially configured to use physical layer information that is captured and aggregated using the techniques described herein.

FIG. 12 illustrates an example of how the physical layer information that is captured and aggregated can be used using the techniques described here to

<img file="MX337306B_D0013.tif" />

MEXICAN INSTITUTE OF PROPERTY

INDUSTRIAL

<img file="MX337306B_D0014.tif" />

improve the efficiency of the network interconnection diapooitives ··· used in a network.

FIG. 13 illustrates another exemplary embodiment of a system that includes the physical layer information functionality as well as the physical layer management functionality.

FIG. 14-16 illustrate another exemplary embodiment of a system that includes the physical layer information functionality as well as the physical layer management functionality.

FIG. 17 is a block diagram of an embodiment of a wall outlet that includes the functionality of obtaining information on the physical layer.

FIG. 18 is an embodiment of a computer that includes the functionality of obtaining information on the physical layer.

FIG. 19 is a block diagram of an exemplary embodiment of a switch using a physical layer device that includes the integrated functionality of reading the media information.

FIG. 20 is a block diagram of an exemplary embodiment of a computer using a device.

<img file="MX337306B_D0015.tif" />

Physical layer that includes built-in functionality to read media information.

FIG. 21 is a diagram of one embodiment of a cover that can be fitted around an RJ-45 plug to connect a storage device to the RJ-45 plug.

FIG. 22 illustrates a network that deploys passive fiber optic lines.

FIG. 23 is a schematic diagram showing an exemplary cable routing scheme for the fiber distribution hubs of FIG. 2. 3.

Similar numbers and designations in various drawings indicate similar elements.

DETAILED DESCRIPTION

FIG. 1 is a block diagram of an embodiment of a system 100 that includes the Physical Layer Information (PLI) functionality as well as the Physical Layer Management (PLM) functionality. System 100 comprises a plurality of connector sets 102, where each connector set 102 comprises one or more ports 104. In general, connector sets 102 are used to connect physical media segments to each other.

>4

<img file="MX337306B_D0016.tif" />

»·&lt;:

<img file="MX337306B_D0017.tif" />

Ί

<img file="MX337306B_D0018.tif" />

Each physical communication media segment connects to its respective port 104. Each port 104 is used to connect two or more physical communication media segments to each other (eg, to implement a portion of a logical communication link). Examples of connector assemblies 102 include, for example, rack-mounted connector assemblies (such as patch panels, distribution units, and media converters for physical fiber and copper media), wall-mounted connector assemblies. (such as boxes, jacks, outputs, and media converters for physical copper and fiber media), and network interconnect devices (such as switches, routers, hubs, repeaters, gateways and access points).

At least some of the connector assemblies 102 are designated for use with physical communication media segments that identify the attribute information stored in or on them. The identifier and attribute information are stored in the physical media segment so as to allow the stored information, when the segment is connected to port 104, to be read by an ín¿ti ru'ie>

,,. '. &lt;/ 1 programmable processor 106 associated with _the _with connector assemblies 102. Examples of information that can be stored in a physical media segment include, without limitation, an identifier that uniquely identifies the particular physical media segment (similar to an ETHERNET Media Access Control (MAC) address. but associated with the physical communication means and / or the connector connected to the physical communication means), a part number, a plug or other type of connector, a cable or fiber type and length, a serial number, a cable polarity, a manufacturing date, a manufacturing lot number, information about one or more visual attributes of physical communication media or a connector connected to the media communication physicals (such as information about the color or shape of the physical media or connector or an image of the physical media or connector), and other information used by an Enterprise Resource Planning (ERP) system or an inventory control system. In other embodiments, the alternative or additional data is stored in the media segments. For example, tests or information about the quality or performance of

Lü.j;

Media can be stored in the physical media segment. Testing or information on media quality or performance, for example, may be the results of tests that are performed when manufacturing a particular media segment.

Also, as noted below, in some embodiments, the information stored in or on the physical media segment may be updated. For example, information stored in or about the physical media segment may be updated to include the results of tests that are performed when a physical media segment is installed or controlled. In another example, such test information is administered to an aggregation point 120 and stored in a data store maintained by aggregation point 120 (both of which are described below). In another example, the information stored in or about the physical media segment includes a count of the number of times that a connector (not shown) connected to a physical media segment was inserted into port 104. In that example, the count stored in or on the segment of

<img file="MX337306B_D0019.tif" />

The physical means of communication is that the connector is inserted into port 104. This insert count value can be used, for example, for warranty purposes (for example, to determine if the connector has been inserted more times than specifically established in the guarantee) or for the purposes of security (for example, to detect unauthorized insertions of the physical means of communication).

In the particular embodiment shown in FIG. 1, each of the ports 104 of the connector assemblies 102 comprises a respective media read interface 108 through which the respective programmable processor 106 is capable of determining whether the physical media segment is connected to port 104 and, if one is, if one is able to read the identifier and the attribute information stored in or on the connected segment (if said information is stored there). Programmable processor 106 associated with each set of connectors 102 is communicatively coupled to each of the media read interfaces 108 using a suitable bus or other interconnect (not shown).

In the particular embodiment shown in FIG. 1, Four exemplary types of configuration are shown '^ of *' connector sets. In the first connector assembly configuration 110 shown in FIG. 1, each connector set 102 includes its own respective programmable processor 106 and its own respective network interface 116 which is used to communicatively couple those connector sets 102 to an Internet Protocol (IP) network 118.

In the second type of connector assembly configuration 112, a group of connector assemblies 102 are physically located in close proximity to each other (eg, in a bay or an equipment closet). Each of the connector assemblies 102 in the group includes its own respective programmable processor 06. However, in the second connector assembly configuration 112, some of the connector assemblies 102 (referred to herein as matched connector assemblies) include their own respective network interface 116 while some of the connector assemblies 102 (referred to herein as unsuitable connector sets) do not include it. The unsuitable connector assemblies 102 are communicatively coupled to

<img file="MX337306B_D0020.tif" />

one or more of the matched connector sets 102 in the group via local connections. In this way, non-matched connector sets 102 are communicatively coupled to IP network 118 through network interface 116 included in one or more of matched connector sets 102 in the group. In the second type of connector set configuration 112, the total number of network interfaces 116 used to couple connector sets 102 to IP network 118 can be reduced. Furthermore, in the particular embodiment shown in FIG. 1, non-matched connector sets 102 are connected to matched connector sets 102 using a daisy-chain topology (although other topologies may be used in other implementations and embodiments).

In the third type of connector assembly configuration 114, a group of connector assemblies 102 are physically located in close proximity to each other (eg, within a bay or equipment cabinet). Some of the connector sets 102 in the group (also referred to herein as master connector sets 102) include their own programmable processors 106 and

<img file="MX337306B_D0021.tif" />

their network interfaces. 116, although ^ some of the connector sets 102 (also referred to herein as slave connector sets 102) do not include their own programmable processor 106 or network interfaces 116. Each of the slave connector sets 102 it is communicatively coupled to one or more of the master connector assemblies 102 in the group through one or more local connections. The programmable processor 106 in each of the master connector sets 102 is capable of performing the processing described below for the master connector sets 102 of which it is a part and all slave connector sets 102 to which the connector sets 102 teachers connect through local connections. As a result, the cost associated with slave connector sets 102 can be reduced. In the particular embodiment shown in FIG. 1, the slave connector sets 102 are connected to a master connector set 102 in a star topology (although other topologies may be used in other implementations and embodiments).

Each programmable processor 106 is configured to run software or firmware causing the processor to r

<img file="MX337306B_D0022.tif" />

<img file="MX337306B_D0023.tif" />

Programmable 106 perform several of the functions described below. Each programmable processor 106 also includes a suitable memory (not shown) that is coupled to the programmable processor 106 to store instructions and program data. In general, the programmable processor 106 determines whether a physical communication media segment is connected to a port 104 with which that processor 106 is associated and, if one is, reads the identifier and attribute information stored in or on the connected physical media segment (if the segment includes such information stored in or on it) using the associated media read interface 108.

In the first, second, and third configurations 110, 112, and 114, each programmable processor 106 is also configured to transmit physical layer information to devices that are coupled to IP network 118. The physical layer information (PLI) includes information on the connector sets 102 associated with that programmable processor 106 (also referred to herein as device information) as well as information on any of the physical media segments

J, ί: ^; r-1. ♦ '- · /; '' j; Ri. '&lt;· Connected to ports 104 thereof ^ '15 óñjOiTtos - = - ^ e .-- ^ .. ^, connectors 102 (also referred to here as media information). Device information includes, for example, an identifier for each set of connectors, a type of identifier that identifies the type of connector set, and port priority information that associates a priority level with each port. The media information includes the identity and attribute information that the programmable processor 106 has read from the connected physical media segments that have identifier and attribute information stored in or on them.

Media information may also include information about physical communication media that do not have identifier or attribute information stored in or about them. This latter type of media information can be entered manually when the physical media segments associated with connector sets 102 are connected (for example, using a management application running on programmable processor 106 that allows a user to configure and check connector sets 102).

<img file="MX337306B_D0024.tif" />

In the fourth type of connector assembly configuration 115, a group of connector assemblies 102 is located within a common chassis or other type of enclosure. Each of the connector sets 102 in configuration 115 includes its own programmable processors 106. In the context of this configuration 115, the programmable processors 106 in each of the connector sets are slave processors.

106. Each of the programmable slave processors

106 they are also communicatively coupled to a common master programmable processor 117 (eg, on a backplane included in the chassis or enclosure). The master programmable processor 117 is coupled to a network interface 116 which is used to communicatively couple the master programmable processor 117 to the IP network 118. In this configuration 115, each slave programmable processor 106 is configured to determine if the physical media segments are connected to its port 104 and to read the identifier and attribute information stored in or on the connected physical media segments (if the connected segments have such information stored in or on them) using the associated media read interface 108. This information is communicated from c-. * The slave programmable processor 106 ~ en -— eada, _, usp_ from connector assemblies 102 in the chassis to master processor 117. Master processor 117 is configured to handle the processing associated with the communication of physical layer information read by the Slave processors 106 to devices that are coupled to IP network 118.

System 100 includes functionality that allows the physical layer information that connector sets 102 capture to be used by application layer functionality outside of the traditional physical layer application management domain. In other words, that the information on the physical layer is not retained in a PLM island used only for PLM effects, but is available for other applications. In the particular embodiment shown in FIG. 1, system 100 includes an aggregation point 120 that is communicatively coupled to connector sets 102 through the IP network

118 .

Aggregation point 120 includes the functionality of obtaining physical layer information from connector sets 102 (and other devices) and stores the physical layer information in a data store.

• · 1 Lj ../

The aggregation point 12 0 can be used — paxg .__ to receive the physical layer information of various types of connector sets 106 that have the functionality to automatically read the information stored in or about the physical media segment. Examples of such connector sets 106 are described above. Also, the aggregation point 120 and the aggregation functionality 124 can be used to receive the physical layer information from other types of devices that have the functionality to automatically read the information stored in or on the physical media segment. Examples of such devices include end-user devices - such as computers, peripherals (such as printers, copiers, storage devices, and scanners), and IP phones - that include the functionality to automatically read information stored in or on the physical media segment. Communication.

Aggregation point 120 can also be used to obtain other types of physical layer information. For example, in this embodiment, the aggregation point 120 also obtains information about

<img file="MX337306B_D0025.tif" />

Physical media segments that are not otherwise communicated with an aggregation point 120. An example of such information is information about unconnected physical media segments that otherwise do not have information stored in or about them, that are connected to a set of connectors (including, for example, information indicating which ports on devices are connected to which ports of other devices on the network as well as media information about the segment). Another example of such information is information about physical communication media segments that are connected to devices that are unable to read the media information that is stored in or about the media segments that are connected to their ports and / or that are not are capable of communicating such information to aggregation point 120 (for example, because such devices do not include such functionality, because such devices are used with media segments that do not have media information stored in or on them, and / or because bandwidth is not available to communicate such information to aggregation point 120). In this example, the information may include, for example, information about the devices themselves (such as the device's MAC addresses and the IP addresses if assigned to those devices), information that indicates which ports on the devices are connected to which ports from other devices on the network (for example, other connector sets), and information about the physical media connected to the device ports. This information can be provided to aggregation point 120, for example, by manually entering such information into a file (such as a spreadsheet) and then uploading the file to aggregation point 120 (for example, using a web browser) online. with the initial installation of each of the various items.

Such information can also, for example, be entered directly using a user interface provided by aggregation point 120 (eg using a web browser).

Aggregation point 120 can also obtain information on the design of the building or buildings in which the network is installed, as well as information indicating where each of the connector sets 102 is located, the physical media segment and the network interconnection device within the building. This information may, for

<img file="MX337306B_D0026.tif" />

IN

Ui L.

<img file="MX337306B_D0027.tif" />

'í.

<img file="MX337306B_D0028.tif" />

For example, manually enter and ^ verify (for example, using a web browser) in connection with the initial installation of each of the different items. In one implementation, such location information includes an X, Y, and Z location for each port or another termination point for each physical media segment (for example, location information for X, Y, and Z of the type specified in the ANSI / TIA / EIA 606-A (Management Standard for the Infrastructure of

Commercial Telecommunications).

Aggregation point 120 can obtain and maintain evidence, media quality, or performance information related to the various physical media segments that exist on the network. Testing, media quality, or performance information, for example, may be the results of tests that are performed when a particular media segment is manufactured and / or when tests are performed when a media segment is installed particular or otherwise controlled.

Aggregation point 120 also includes the functionality of providing an interface for external devices or entities to access the νν v

INSTIT maintained physical layer information ».p.or _ .. ql ~ j) aggregation point 120. This access may include retrieving information from aggregation point 120 as well as providing information to aggregation point 120. In this embodiment, the point Aggregation 120 is implemented as middleware that is capable of providing such external devices and entities with transparent and convenient access to the PLI maintained by the access point 120. Since aggregation point 12 0 aggregates the PLI of relevant devices on IP network 118 and provides external devices and entities with access to that PLI, external devices and entities do not need to individually interact with all devices on the IP network 118 that the PLI provides, nor should those devices have the ability to respond to requests from such external devices and entities.

Aggregation point 120, in the embodiment shown in FIG. 1, implements an application programming interface (API) through which the application layer functionality can access the physical layer information maintained by the aggregation point j!

INS

120 which using a development kit describes and documents the API.

<img file="MX337306B_D0029.tif" />

i'ru / c

DE L \ f hOElEDÁD ir.'DUSr.-GAL.

<img file="MX337306B_D0030.tif" />

(SDK) software '»**«' · * - r ~ - V -y,

For example, as shown in FIG. 1, a network management system (NMS) 130 includes the physical layer information (PLI) functionality 132 which is configured to retrieve physical layer information from the aggregation point 120 and provide it to other parts of the NMS 130 for use by that medium. The NMS 130 uses the retrieved physical layer information to perform one or more network management functions (eg, as described below). In one implementation of the embodiment shown in FIG. 1, the PLI 132 functionality of NMS 130 retrieves physical layer information from aggregation point 120 using the API implemented by aggregation point 120. NMS 130 communicates with aggregation point 120 on the IP network

118.

As shown in FIG. 1, an application 134 running on a computer 136 can also use the API implemented by aggregation point 120 to access PLI information maintained by aggregation point 120 (for example, to retrieve such information from aggregation point 120 I for

<img file="MX337306B_D0031.tif" />

manage this information at the point ^ disaggregation 120). Computer 136 attaches to IP network 118 and accesses aggregation point 120 of IP network 118.

In the embodiment shown in FIG. 1, one or more network interconnect devices 138 used to implement IP network 118 include Physical Layer Information (PLI) functionality 140. The PLI 140 functionality of network interconnect device 138 is configured to retrieve information on physical layer from aggregation point 120 and use the recovered physical layer information to perform one or more network interconnection functions. Examples of network interconnect function include Layer 1, Layer 2, and Layer 3 (OSI model) network interconnect functions such as routing, switching, repeating, bridging, and maintaining communication traffic that it is received in the network interconnection device. In an implementation of such an embodiment, the PLI 140 functionality uses the API implemented by the aggregation point 120 to communicate with the aggregation point 120.

The PLI 140 functionality included in the network interconnect device 138 can also be used

<img file="MX337306B_D0032.tif" />

to capture the information about the TCT layer '^ S''oclade' - '*' with the network interconnection device 138 and the physical communication means connected to it and communicates the captured physical layer information to the aggregation point 120. It can be providing such information to aggregation point 120 using the API or using the protocols that are used for communication with connector sets 102.

Aggregation point 120 can be implemented in a stand-alone network node (eg, appropriate software running on a stand-alone computer) or can be integrated in conjunction with other network functionality (eg, integrated with an item management system or a network management system or other network server or network element). Furthermore, the functionality of the aggregation point 120 can be distributed across multiple nodes and devices on the network and / or implemented, eg, hierarchically (eg, with multiple levels of aggregation points).

In addition, aggregation point 120 and connector sets 102 are configured so that aggregation point 120 can automatically discover and connect with devices that provide PLI to an aggregation point 120 (such as

<img file="MX337306B_D0033.tif" />

<td>connectors</td><td> 102</td><td>and</td><td>the device</td><td>of</td><td>jn t erconex ion</td><td>of</td>

<td>networks 138)</td><td>than</td><td>I know</td><td>they find in</td><td>the</td><td colspan="2">network 118. From this</td>

<td colspan="2">shape when</td><td>the</td><td>devices</td><td>than</td><td>They are capable</td><td>of</td>

providing PLI to an aggregation point 120 (such as connector sets 102 or a network interconnect device 138) are coupled to IP network 118, an aggregation point 120 is capable of automatically discovering connector sets 102 and starting to add physical layer information for connector sets 102 without requiring the person installing the connector sets 102 to be aware of the aggregation points 120 found on the IP network. Similarly, when an aggregation point 120 is coupled to IP network 118, aggregation point 120 is capable of automatically discovering and interacting with devices that are capable of providing PLI to an aggregation point without the need for person installing the aggregation point 120 has knowledge of the devices found on the IP 118 network. Thus, the physical layer information resources described here can be easily integrated into the network

IP 118.

ΪΜ kίΝΜΊΤυ O

<img file="MX337306B_D0034.tif" />

IP network 118 may include one or more — -_.,, -Area, local, and / or wide-area networks (including for example the Internet). Accordingly, aggregation point 120, NMS 130, and computer 136 need not be located in the same location as each other or in the same location as connector assemblies 102 or network interconnect devices 138.

Various conventional connection techniques can be used in IP networks to install the system 100 of FIG. 1. For example, conventional security protocols can be used to secure communications if communication is made through a public channel or otherwise insecure communication (such as the Internet or over a wireless communication link).

In an implementation of the embodiment shown in

FIG. 1, each set of connectors 102, each port 104 of each set of connectors 102, and each media segment is individually addressable. When IP addresses are used to individually address each set of connectors 102, a dedicated virtual private network (VPN) can be used for use with the various sets of connectors 102 to segregate the IP addresses used for the sets of

O ΊΓ .i A

U.ZíCá'NO VXfi. ''

Uvi i ¡GAL 'BK ?.

XA connectors 102 of the main space used in the IP 118 network.

IP addresses

Also, connector assemblies 102 can be powered using conventional techniques of

Power over Ethernet specified in the standard

<td>IEEE 802.3af</td><td>, which</td><td>I know</td><td colspan="2">incorporates the present</td>

<td>document by</td><td>reference.</td><td>In</td><td>said implementation,</td><td>a</td>

<td>hub</td><td>power</td><td> 142</td><td>or other device</td><td>of</td>

Power supply (located near or incorporated in a network interconnect device that is coupled to each set of connectors 102) injects DC power into one or more of the wires (also referred to herein as the power wires) included in the stranded copper cable used to connect each set of connectors 102 to the associated network interconnect device. Interface 116 on connector assemblies 102 draws the injected DC power from the power wires and uses the withdrawn energy to supply power to the active components of those connector assemblies 102. In the second and third connector assembly configuration 112 and 114, some of the connector sets 102 are not directly connected to IP network 118 and therefore cannot receive power.

<img file="MX337306B_D0035.tif" />

INLTf

<img file="MX337306B_D0036.tif" />

rR'Jr'IECA!)

R'D'Jí ​​'.' Íí'aL

<img file="MX337306B_D0037.tif" />

directly from the power wires. These connector sets 102 receive power from the connector sets 102 that are directly connected to the IP network 118 through the local connections that the connector sets 102 communicate with each other. In the fourth configuration 115, the interface 116 extracts the injected DC power from the power wires and supplies power to the master processor 117 and each of the slave processors 106 in the backplane.

In the particular embodiment shown in FIG. 1, system 100 also supports conventional physical layer management (PLM) operations such as motion tracking, additions, and changes of physical media segments that are connected to ports 104 of connector sets 102 and provide assistance in carrying out movements, additions and changes. The PLI provided by aggregation point 120 can be used to enhance conventional MAC-guided processes. For example, information about the location of port 104 and the visual appearance (eg, color or shape) of the relevant physical media segment (or the connector connected to it) may be transmitted to a technician for assistance.

<img file="MX337306B_D0038.tif" />

carry out a movement, an addition Q_xi_.un_c ^ nibi.o_z, ...., This information can be transmitted to a computer or smartphone used by the technician. Furthermore, the PLI functionality residing on system 100 can also be used to verify that a particular MAC has been properly performed by verifying that the expected physical media segment is located on expected port 104. If this is not the case, it can be send an alert to the technician so that the technician can correct the matter.

The PLM functionality included in system 100 can also support conventional techniques to guide the technician to perform a MAC (for example, illuminating one or more light emitting diodes (LEDs) to direct a technician to a set of connectors 102 home and / or to a particular port 104 or displaying messages on a liquid crystal display (LCD) included in or near connector assemblies 102.

Other PLM functions include keeping historical records of the media connected to the connector sets. In the embodiment shown in FIG. 1, aggregation point 120 includes PLM 144 functionality that implements such PLM functions. The PLM 144 functionality does this by using the information on the physical layer as aggregation point 120.

IP network 118 is typically implemented using one or more network interconnection devices. As described above, a network interconnect device is a type of connector set (and a particular implementation of a network interconnect device 138 is referred to individually in FIG. 1 solely for ease of explanation). In general, a network interconnect device can be configured to read media information that is stored in or on the physical media segments that are connected to its ports and to communicate the media information that is read from the connected media segments (as well as information about the network interconnection device itself) to an aggregation point 120 like any other set of connectors described here.

In addition to connector assemblies 102, the techniques described herein for reading media information stored in or on a physical media segment may be used at one or more network end nodes. For example, computers (such as laptops, ~ - ^ BervidQr.es, ^_{;; j}... J-as_ desktop computers, or special-purpose computing devices such as IP phones, IP multimedia applications and storage devices) can be configured to read the media information that is stored in or on the physical media segments that are connected to its ports and to communicate the media information read from the media segments connected (as well as information about the devices themselves) to an aggregation point 120, as described here.

FIG. 2 is a block diagram of a high-level embodiment of a port 104 and a media read interface 106 that are suitable for use in the system 100 of FIG. one.

Each port 104 comprises a first connection point 206 and a second connection point 208. The first connection point 206 is used to connect a first physical media segment 210 to port 104, and the second connection point 208 is used to connect a second segment of physical communication media 212 to port 104.

and A · /? ·> π go to _________

A A'Ni .T ¿

<img file="MX337306B_D0039.tif" />

In the particular embodiment shown ^ in FIG. 2, the first connection point 206 is located near the rear of the connector assemblies. Accordingly, the first connection point 206 and the first physical media segment 210 connected thereto are referred to herein as the rear connection point 206 and the rear media segment 210, respectively. Also, in this embodiment, the rear connection point 206 is configured to connect the rear media segment 210 to port 104 semi-permanently. As used herein, a semi-permanent connection is one that is designed to be changed relatively infrequently, if ever. This is also sometimes referred to as a one-time connection. Examples of suitable rear connectors 206 include punch-down blocks (in the case of physical copper media) and fiber adapters, fiber splice points, and fiber termination points (in the case of optical physical media).

In the embodiment shown in FIG. 2, the second connection point 208 is located near the front of the connector assemblies 102. Accordingly, reference is also made herein - - - '⁵- ......- 'ΐά tx ^;· '' / Ν i to the second connection point 2 08 and to the ^^ éguñdb “'' gégtn'eiítt5 ''¹ of physical media 212 such as front connection point 208 and front media segment 212, respectively. In the embodiment shown in FIG.

2, the front connection point 208 for each port 104 is designed for use with connected front media segments 212 having identifier and attribute information stored in or on them. As used herein, a connected media segment is a physical communication media segment that includes a connector 214 at at least one end of the segment. The front connection point 208 is implemented using a suitable connector or adapter that mates with the corresponding connector 214 at the end of the front media segment 212. Connector 214 is used to facilitate connection and repeated disconnection of the front media segment 212 with port 104. Examples of connected media segments include CAT-5, 6, and 7 stranded cables that have modular connectors or plugs connected to both ends (in which case, the front connectors are implemented using compatible modular jacks) or optical cables that have connectors SC, LC, FC, LX.5, MTP or MPO (in which case the front connectors are implemented using SC, LC, FC, LX.5, lL υ · i connectors

MTP, or compatible MPO or adapters). The techniques described here can be used with other types of connectors including, for example, BNC connectors, F connectors, DSX jacks and plugs, bantam jacks and plugs, and MPO multi-fiber connectors and adapters and

MTP.

Each port 104 communicatively couples the respective rear connection point 206 with the respective front connection point 208. As a result, a rear media segment 210 connected to the respective rear connection point 206 is communicatively coupled to any front media segment 212 connected to the respective front connection point 208. In one implementation, each port 104 is designed for use with a rear media segment 210 and a front media segment 212 comprising the same type of physical communication media, in which case each port 104 communicatively couples any rear media segment 210 connected to the respective rear connection point 206 with any front media segment 212 connected to the respective front connection point 208 at the physical layer level without any physical media conversion. In other implementations, each port

104 &lt;A 'communicatively couples any segment of TTt ^ aTb ^ HrfáSéTó' 210 connected to the respective rear connection point 206 with any front media segment 212 connected to the respective front connection point 208 in other ways (eg, using a multimedia converter if the rear media segment 210 and the front media segment 212 comprise different types of physical communication media).

As shown in FIG. 2, port 104 is configured for use with front media segments 212 that include a storage device 216 in which the media information for that media segment 212 is stored. Storage device 216 includes a storage device interface that, when the corresponding connector 214 is inserted into (or otherwise connected to) a front connection point 208 of port 104, communicatively couples storage device 216 with the Corresponding media read interface 108 so that the associated programmable processor 106 can read the information stored in the storage device 216. In one implementation of the embodiment shown in FIG. 2, each connector 214 contains the FI M FI device

.... ...... '.'Λ *' · - '____ · -' Ά ιΚίΤΓΓοϊΟ méxícano

CC L ?. , ΤΟΗΪΙ / ΆD V ^ JZSiÍL ^ - 't storage 216. In another implementation of said embodiment, the storage device 216 is located within a separate housing of connector 214. In such an implementation, the enclosure is configured so that it can fit into media segment 212 or connector 214, with the interface of the storage device positioned relative to connector 214 so that the interface of the storage device is properly paired with the media read interface 108 when connector 214 is inserted into (or otherwise connected to) front connection point 208.

In some implementations, at least some information stored on storage device 216 may be field updated (for example, an associated programmable processor 06 causes additional information to be written to storage device 216 or information previously stored in it to be changed or deleted. the storage device 216). For example, in some implementations, some information stored in storage device 216 cannot be changed in the field (for example, identifier information or manufacturing information) while other information stored

ΪΜΡΪ: ““ ¿agSx on storage device 216 can be changed in the field (eg testing, media quality or performance information). In other implementations, no information stored on storage device 216 can be updated in the field.

Likewise, storage device 216 may also include a processor or microcontroller, in addition to storage for media information.

In that case, the microcontroller included in the storage device 216 can be used to run software or firmware, for example, to control one or more LEDs connected to the storage device 216. In another example, the microcontroller runs software or firmware that performs an integrity test on the front media segment 212 (for example, performing a capacitance or impedance test on the coating or isolator that surrounds the front media physical communication segment 212 , (which may include a metallic foil or a metallic filler for such purposes)). In the event that a problem is detected with the integrity of the front media segment 212, the microcontroller

<img file="MX337306B_D0040.tif" />

You can report the fact to the programmer> le l06 processor associated with port 104 using the interface of the storage device (for example, causing an interrupt). The microcontroller can also be used for other functions.

FIG. 3 illustrates an embodiment of a system 300 that includes the Physical Layer Information (PLI) functionality as well as the Physical Layer Management (PLM) functionality. System 300 comprises a plurality of patch panels 302 located within a common chassis 301. For example, in a common configuration, chassis 301 is installed in a cabinet or communications room and mounted on a bracket. In some larger installations, there are various chassis means 301 and patch panels 302 (arranged, for example, in multiple bays). Patch panels 302 can be packaged as sheets that slide into chassis 301.

Each patch panel 302 comprises a set of ports 304 (eg, 16, 32, 48, or 512 ports 304). The number of ports 3 04 can vary between a connection panel 302 and a connection panel 302.

Each of the 3 04 ports is implemented ^^ as shown in FIG. 2. In general, in the context of the embodiment shown in FIG. 3, each front media segment 312 comprises a connection cable 312 that is used to selectively interconnect two ports 304 thereof or different connection panels 302. In this embodiment, each patch cord 312 has a modular jack 314 attached to each end that can be inserted into a front media connector on one of ports 304 of patch panels 302.

In this way, the respective rear media segments (not shown in FIG. 3) coupled to the two interconnected ports 304 may be communicatively coupled to each other to implement a logical communication link between the equipment that is coupled to the media segments respective rear. For example, in an exemplary application, a wall-mounted socket is communicatively coupled to a rear port 304 connector using a suitable rear media segment, such as a copper or fiber cable. The cable is typically placed in a building (eg, below, above, around, and / or on walls, ceilings, floors, and the like) and does not move easily or frequently. Yes

Λ a first piece of equipment that is connected to'ííiade —....

Said wall mounted sockets need to be communicatively coupled to a second piece of equipment that is connected to another of said wall mounted sockets, a connection cable 312 can be used to establish the connection.

As shown in FIG. 3, a master processor unit (MPU) 330 is also included within the chassis 301. The master processor unit (MPU) 330 communicates with the slave processor module 318 included in each of the patch panels 304 in one plane posterior 315. FIG. 4 is a block diagram of one embodiment of each slave processor module 318 shown in FIG. 3.

Each module of slave processor 318 comprises a programmable slave processor 320 that executes software 322. Execution of software 322 causes slave processor 320 to perform several of the functions described below. Each module of slave processor 318 also includes memory 324 that is coupled to slave processor 320 to store program instructions and information. The 320 slave processor in each processor module

<img file="MX337306B_D0041.tif" />

Slave 318 attaches to backplane 315 using a suitable interface.

System 300 is designed for use with patch cords 312 (or other front media segments) having identifier and attribute information of the type described above in connection with FIG. 2 stored in or on them. Each of the ports 304 of each patch panel 302 comprises a respective media read interface (not shown in FIG. 3). Slave programmable processor 320 on each patch panel 302 is communicatively coupled to each media read interface on patch panel 302 using a bus or other interconnect (not shown). The slave programmable processor 320 is configured to determine if the status of a port 3 04 changes. The state of a port 304 changes, for example, when a connection cable is inserted into a previously empty front connector, or when connection cable 312 is removed from a front connector, or when a different connection cable is inserted into a connector. previously occupied front.

In one implementation of such an embodiment, each media read interface is configured so

<img file="MX337306B_D0042.tif" />

that the slave programmable processor 320 can detect changes in the state of each port 304. For example, the electrical contact structure of the media read interface may be configured such that a change in the state of electrical signals occurs when a patch cord is inserted into or removed from port 304 (for example, by closing or opening an electrical circuit). Slave processor 320 detects such changes in state to detect when a patch cord is inserted into or removed from the front connector of each port 304. Examples of such contact structures are contained in United States Provisional Patent Application Act No. 61 / 252,395, filed on October 16, 2009, titled MANAGED CONNECTIVITY IN ELECTRICAL SYSTEMS AND THEIR METHODS (also referenced here such as application '395), the United States provisional patent application acts No. 61 / 253,208, filed on October 20, 2009, titled ELECTRICAL PLUG FOR SYSTEMS OF

MANAGED CONNECTIVITY (also referred to here as the '208 application and the United States provisional patent application minutes No. 61 / 252,964, filed on October 19, 2009, titled ELECTRICAL PLUG FOR SYSTEMS OF

I. JÍV: l P, jmsiív; ¡-, ¿·. &lt;&lt; /_r and Λ

MANAGED CONNECTIVITY (to which Xambiéri · ^ '^^ ·' has ^ ¿2 ^ reference here as the request '964 * T ^ ~ Kct *' »oi-i © itu.dz ....-.-_;„_:._;, '395, application' 208, and application '964 are incorporated herein by reference.

Alternatively, slave processor 320 can be configured to periodically scan the entire media read interface included in that patch panel 302 to determine the status of any one of associated ports 304.

Also, when the software 322 running on the slave programmable processor 320 on each patch panel 302 determines that a patch cord has been inserted into a previously empty front connector or a different patch cord has been inserted into a front connector previously connected, the 322 software reads the information stored in or on the inserted connection cable.

All changes in the status of the patch panel ports 304 and the information that is read from the patch cords are communicated to the MPU 33 0 on the backplane 315. Port status information is collectively referred to herein. and the i ÁZÍ jZ it

MEXICAN INSTITUTE rT-go -.- f. , 'X, cables run on the processor each connection port 3 02 information read from the port information.

The programmable software 322 slave 320 en also communicates information about the respective patch panel 302 to the MPU 330 in the backplane 115 (such information is also referred to as patch panel information). Patch panel software 322 communicates patch panel information to MPU 330, for example, in the following situations: in response to a request from MPU 330, or when patch panel 302 is turned on first, or when any of the information changes occur in the patch panel, or after a predetermined amount of time has passed since the last patch panel information communication to the MPU 330.

As shown in FIG. 3, each of the ports 304 of each patch panel 3 02 includes a respective visual indicator 316 (such as a light emitting diode (LED)) that is coupled to the slave programmable processor 318 via an internal bus or other interconnect (not shown) Visual indicator 316 is located near port 3 04 with which the

<img file="MX337306B_D0043.tif" />

visual indicator 316. The priS ^ aTOable -'- slave processor 332 can drive each of the visual indicators 316 (eg, through the illumination of an LED) to identify associated port 304.

As shown in FIG. 3, the MPU 33 0 is configured to communicate with and control the slave processor 318 modules. Also, the MPU 330 is configured to communicate with other devices on an IP 350 Network (such as LAN 352). More specifically, MPU 330 is configured to communicate with an aggregation point 353 on LAN 352. FIG. 5 is a block diagram of one embodiment of the master processor unit 330 of FIG. 3. The MPU 330 includes a master programmable processor 332 that runs the software 334. Execution of the software 334 causes the master programmable processor 332 of the MPU 330 to perform various functions described below. MPU 330 also includes memory 336 which is coupled to master processor 332 to store program instructions and information. Master processor 332 is coupled to backplane 315 of chassis 301. Slave processor 320 in each of patch panels 302 communicates with master programmable processor 332

<img file="MX337306B_D0044.tif" />

<img file="MX337306B_D0045.tif" />

<img file="MX337306B_D0046.tif" />

in the MPU 330 in the posterior plane — particular embodiment shown in FIG. 3, most of the processing performed on system 300 is performed by master programmable processor 332 in MPU 330. As a result, a relatively low power slave programmable processor 318 can be used in each of the patch panels. 302, as an 8-bit or 16-bit microcontroller. The master programmable processor 332 in the MPU 33 0, in said embodiment, is implemented using a 16-bit or 32-bit microcontroller or microprocessor.

The MPU 330 also comprises an ETHERNET 340 interface that is used to communicatively couple the MPU 330 (and the 332 master programmable processor included there) to one or more Network Protocol networks.

Internet (IP) 350 (shown in FIG. 3). In the particular embodiment shown in FIG. 3, the ETHERNET 34 0 interface is coupled to a local area network (LAN) 352. This connection to LAN 352 can be implemented, for example, through the use of a cable to connect the ETHERNET 340 interface of the MPU 330 to port 304 of a patch panel 302 (attaching the cable to the rear connection point 306

INSTITUT MEXICANO L> E LA AGE

INDUSTRIAL

<img file="MX337306B_D0047.tif" />

of that port 304). Each of the multiple ^^ ports of a network interconnect device (such as a hub, a router, or a switch) (not shown in FIG. 3) also connects to respective ports 5 304 of a patch panel 302 (connecting the respective cables to the respective rear connection points 306 of ports 304).

The ETHERNET 34 0 interface of the MPU 33 0 is interconnected to a port of the network interconnect device by inserting one end 314 of a connection cable 312 into the front connector 308 of port 304 which is connected to the interface of ETHERNET 340 and by inserting the other end 314 of the connection cable 312 into the front connector 308 of port 306 which is connected to one of the ports of the interconnection device

<td></td><td>of networks. The others</td><td>ports</td><td>of the</td><td>device</td><td>of</td>

<td></td><td>network interconnection</td><td colspan="2">connect (to</td><td>through</td><td>the</td>

<td></td><td>connection panels 302)</td><td>) to others</td><td>items</td><td>of the team</td><td>of the</td>

<td> 20</td><td>end user 356 (se</td><td>shows</td><td>in the</td><td colspan="2">FIG. 3) (like</td>

computers) and other network interconnection devices (such as gateways or network interface devices that connect LAN 352 to a wide area network such as Internet 358 (shown in FIG. 3)).

í institute ·.? μ ί · 4 CC £ LAfüOfi; -MÓ V^ι· · .. V i ¡P .. ιΝΟ-Λτζνα.

As shown in FIG. 5, In this particular embodiment, the MPU 334 software includes a TCP / IP stack 342 that allows the MPU 332 processor to communicate with other devices over one or more IP networks 350.

In the embodiment shown in FIG. 3, power is supplied to MPU 330 and slave processor modules 318 through stranded copper wiring that is used to connect MPU 330 to LAN 352. Power is supplied using Power over Ethernet techniques specified in the IEEE 802.3af standard. In such an embodiment, the interconnect device to which the MPU 3 30 is coupled includes a power hub 354 or other power supply device (located near or incorporated in it) that injects DC power into one or more of the wires (also referred to here as the power wires) included in the copper braided cable used to connect the MPU 330 to the network interconnect device. The ETHERNET 34 0 interface on the MPU 330 collects the DC power drawn from the power wires and uses the drawn power to supply power to the active components in the MPU 330. In addition, power is supplied from the MPU 33 0 to the patch panels

302 on the backplane 315 to provide power to the active components in the patch panels

<img file="MX337306B_D0048.tif" />

302.

In the particular embodiment shown in FIG. 4, MPU 330 also comprises a power supply unit (PSU) 344 for situations where devices in chassis 3 01 are not powered using Power over Ethernet. PSU 344 can be connected to one or more external power sources 346 (shown in FIG. 3) (such as the alternating current (AC) energy matrix and / or a telco / information center direct current (DC) power source) and converts external power received from external power source 346 to provide power that is suitable for use through the active components of MPU 330 and connection panels 302.

The MPU 334 software running on the programmable MPU processor 332 receives the port and patch panel information from all patch panels 302 and maintains a data store 362 (shown in FIG. 5) in which information is stored and organized. The MPU 334 software running on the MPU processor!

IMPI '^NiTn¿Y · «« 'Cano

OF industrial currency

<img file="MX337306B_D0049.tif" />

programmable 332 also cor'F'i configured to communicate with one or more aggregation points 353. In the particular embodiment shown in FIG. 5, MPU 334 software includes discovery protocol software 364 that is used by MPU 330 and aggregation point 353 to discover and connect to each other. The MPU 334 software also includes communication protocol 366 software that is used to communicate port and patch panel (and other PLI) information to and from aggregation port 353.

The MPU 334 software also includes functionality that allows users, systems, and devices to directly interact with the MPU 330 on IP 350 networks. In the particular embodiment shown in FIG. 3-11, the MPU 334 software is configured to interact with users using a web browser. In this embodiment, the MPU 334 software includes a 37 0 web server (shown in FIG. 5) allowing the MPU 33 0 to interact with a user web browser on IP 350 networks using the Hypertext Markup Language (HTML) protocol (and related protocols such as the v .ha and Ti-cit protocols.

INSTITUYO .VlXICa. '. O

DE La í'V'P'íJ'a.O \ ir.'MlTTRíAL

Asynchronous JavaScript and XML (AJAX)). In

.... ... 14 particular embodiment shown in FIGS. 3-11, the 'MPU 334 software is also configured to interact directly with users, systems, and devices in other ways. For example, MPU 334 software includes TELNET 372 software that allows other users, systems, and devices to establish a Telnet-type connection to MPU 330 and a 374 email server (implementing, for example, the Transfer Protocol Simple Messages (SMTP)) that allows the MPU 334 software to send email messages to other users, systems and devices. The MPU 334 software also includes security and encryption software 3 76 to allow the MPU 334 software to communicate in a secure manner (for example, using Security Protocol (SSL) sessions or Virtual Private Networks (VPN)).

In the embodiment shown in FIGS. 3 to 11, system 300 is configured for a user to manually enter, for each port 304 that has a respective rear media segment 310 connected to its rear connection point, information about the physical media that is used to implement that ί Α / ί ΊΟ Τ ζ ^ »5 i 1VIΓI @

INSTITUTO MEXICANA de LA RRepiEDAD INDUSTRIAL rear media segment. In this embodiment, the rear media segments are connected to the rear connection points semi-permanently, and typically these connections do not change frequently, if at all. As a result, information about the physical media used to implement the rear media segments can be manually entered and verified in connection with the initial media installation and will typically remain valid thereafter. This information may include information similar to that of port information stored in or on a patch cord and is also referred to here as rear media information. In the event that a change is made to the media that is connected to a rear connection point of a port 3 04, the corresponding physical media information for that port 304 must be updated manually. This read media information, for example, can be entered into a spreadsheet or other file. The spreadsheet is then loaded at aggregation point 353. Aggregation point 353 associates the read media information included in the spreadsheet with information about patch panels 302 and ports 304 that it gets from MPU 330.

<img file="MX337306B_D0050.tif" />

<td></td><td></td><td></td><td></td><td></td><td>(f] I saw (θ H .4. A (. · Jy. INÍTITUrC MEXICANO C- £ LA fltCMÍOAl&gt; IHDUSTIÍIaL</td><td>β</td><td></td>

<td colspan="2">Also, when</td><td>I know</td><td>connect</td><td>a</td><td>device</td><td>of</td><td></td>

<td>interconnection</td><td>of</td><td colspan="2">networks (like</td><td>a</td><td>switch or</td><td>a</td><td></td>

<td>router) a</td><td>the</td><td colspan="3">connection points</td><td>rear of</td><td>the</td><td></td>

<td>ports 304</td><td>of</td><td>a</td><td>panel of</td><td colspan="2">connections 302,</td><td>the</td><td></td>

<td colspan="2">information about</td><td>the</td><td>device</td><td>of</td><td>interconnection</td><td>of</td><td></td>

networks (such as the device's MAC address and an assigned IP address) and the information indicating which port of the networking device is connected to which port 304 of patch panel 3 02 can be manually entered and provided to aggregation point 353 in connection with the initial installation of the network interconnection device. This information is also referred to herein as network interconnect device information. Also, as indicated above, if the network interconnect device includes PLI functionality, such information from the network interconnect device can be automatically captured by the network interconnect device and communicated to aggregation point 353.

Furthermore, in the embodiment shown in FIGS. 3 to 11, system 300 is configured for a user to enter information about the design of the building or buildings in which the network is installed, as well as

F. i'A í'.i O ¡T 'ivi elr

INST.TUT · MEXICAN OE industrial PROPERTY

<img file="MX337306B_D0051.tif" />

also information indicating where—— »patch panel 302, the rear media segment, the networking device, and the wall outlet inside the building. This information is also referred to here as location information. For example, this location information can be entered into a spreadsheet and loaded into aggregation point 353, which associates the location information with the other PLI obtained on system 300.

In the embodiment shown in FIGS. 3 through 11, aggregation point 353 has access to various types of physical layer information including, for example, device information (i.e., port information, patch panel information, network interconnect device information and information from any wall-outlet and end-user devices), media information (i.e. front media information — including media information stored on patch cords — and rear media information), and location information.

In the embodiment shown in FIG. 3, MPU 330 also includes additional 382 interfaces to dock ί Μ Ρ ΐ

MEXICAN INSTITUTE

L'í LA PKOPIFDAD f * „· i; &lt;ou¿Tki« L communicatively the MPU 330 (and the programmable MPU processor 332) to one or more external sensors (eg external temperature sensors) and 384 alarms ( shown in FIG. 1). The MPU 330 can be communicatively »coupled to these external sensors and alarms

384 using conventional and / or wireless communication links. In an application, a thermal map of the network can be produced from the temperature reading, which can be useful for the purposes of

HVAC.

Also, as shown in FIG. 5, the MPU 330 includes a 378 interface through which a technician can directly connect a device such as a computer, personal digital assistant (PDA), or smartphone to the MPU 330 and interact with the 334 software running the processor teacher 332.

In one implementation of the embodiment shown in FIGS. 3 to 11, the MPU 330 and slave processor module 318, the media read interface, and associated visual indicators 316 are integrated into patch panel 302 along with the other components. In another implementation, the MPU 33 0 and the slave processor module 318, the media read interface and associated visual indicators 316 are

IMPI

MEXICAN INSTITUTE OF INDUSTRIAL PRCPIF.DAD

<img file="MX337306B_D0052.tif" />

they locate within one or more modules that are separate from the respective connection panel 302. In said implementation, the individual modules are connected to the front of the respective connection panel 302 so that each visual indicator 316 and media reading interface remain located near its corresponding port 304.

In some embodiments, a monitor (such as a liquid crystal display) is incorporated into the MPU 33 0, the slave processor modules 318, or the patch panel 3 02 to display the messages on the patch panel 302. Also, in In some embodiments, a user input mechanism (such as one or more buttons) is incorporated into the MPU 33 0, slave processor modules 318, or patch panel 302 to

<td>to receive panels</td><td>the inputs of connection 302.</td><td>users located near</td><td>the</td>

<td>FIG.</td><td>6 is a diagram</td><td>illustrating an embodiment</td><td>of</td>

<td>a cable</td><td>connection 312</td><td>which is suitable for use in</td><td>the</td>

<td>system</td><td>300 of FIG.</td><td>3. The connection cable</td><td> 312</td>

<td>shown</td><td>in FIG. 6 is</td><td>suitable for use with</td><td>a</td>

<td colspan="2">panel implementation</td><td>FIG 302</td><td> . 3</td>

where modular RJ-45 sockets are implemented in the front connectors of ports 304. The connection cable í Ivi jp .1

MEkzcáno INSTITUTE

D £ LA P!; Or¡EC / j? V * '\

I i '* «J v« (T XlÁL *** · £ ν »*

312 shown in FIG. 6 comprises an unshielded copper twisted pair (UTP) cable 386. UTP cable 386 includes eight conductors arranged in four conductor pairs. Connecting cable 312 also comprises two RJ-45 plugs 314, one on each end of cable 386 (only one shown in FIG.

6). The RJ-45 314 plugs are designed to be inserted into the RJ-45 modular jacks used as front connectors. Each RJ-45 plug 314 comprises a contact portion 388 in which eight generally parallel electrical contacts 390 are located. Each of the eight electrical contacts 390 are electrically connected to one of the eight conductors in UTP Cable 386.

Each pin 314 also comprises (or is attached to) a storage device 392 (eg, an Electrically Erasable Read Only Programmable Memory (EEPROM) or other nonvolatile memory device). The media information described above for connection cable 312 is stored in storage device 392. Storage device 392 includes sufficient storage capacity to store such information. Each storage device 392

...

-ύ- ν ζ. INSTITUTE s

DS lA I

INLL'j also includes an interface of the storage dTspos'íüiVó'- 394 which, when the corresponding plug 314 is inserted into a front connector of a port 304, communicatively couples the storage device 392 to the corresponding media reading interface of so that the programmable processor 320 in the corresponding connection panel 302 can read the information stored in the storage device 392.

Examples of such 312 connection cable and plug

314 they are described in application '395, application' 208 and application '964.

The embodiment shown in FIGS. 3 to 11 is generally described herein as being implemented using connection cable 312 shown in FIG. 6. However, other types of patch cords can be used, one of which is shown in FIG. 7.

FIG. 7 is a diagram illustrating another embodiment of a connection cable 312 'that is suitable for use in the system 300 of FIG. 3. The connection cable

312 'shown in FIG. 7 is suitable for use with an implementation of patch panel 3 02 of FIG. 3 where the front connectors of the ports

<img file="MX337306B_D0053.tif" />

or connectors

I '

2l.

iNS'rm.

^v l? i

304 are implemented using adapters

Fiber LC. The 312 'connection cable shown in

FIG. 7 comprises an optical cable 386 '. The 386 'optical cable includes an optical fiber included within a suitable coating. Connection cable 312 'also comprises two LC connectors 314' on each cable 386 '. Each LC 314 'connector is designed to be inserted into an adapter designed to be inserted into an LC adapter used as the front connector of a 304 port. Each LC connector 314 'comprises a 3 88' end portion into which an optical connection can be established with the optical fiber in cable 386 'when LC connector 314' is inserted into a single port 304 LC adapter.

Each LC connector 314 'also comprises (or is connected to) a storage device 392' (eg, an Electrically Erasable Read Only Programmable Memory (EEPROM) or other non-volatile memory device). The media information described above for connection cable 312 is stored in storage device 392 '. The storage device 392 'includes a sufficient storage capacity to store said information. Each storage device

<img file="MX337306B_D0054.tif" />

i Μ Ρ1

INST '/ UT'-J and

The ftWiáúc »/; &lt;βί

INDUSraiAl N «s ~ W

392 'also includes a storage device interface 394' which, when the corresponding LC connector 314 'is inserted into a front port 304 connector, communicatively couples storage device 392' to the corresponding media read interface so that the slave programmable processor 320 in the corresponding connection panel 302 can read the information stored in the storage device 392 '.

In some implementations of patch cords 312 and 312 ', storage devices 392 and 392' are implemented using a surface installed EEPROM or other non-volatile memory device. In such implementations, the interface of the storage devices and the media read interface may comprise four terminals: a power terminal, a ground terminal, an information terminal, and an extra terminal that is reserved for future use. The four terminals of the storage device interface come into electrical contact with the corresponding four terminals of the media read interface when the corresponding plug or connector is inserted into the corresponding front connector

INSTITUTO MSICi.'IO

DL LA? R:; í? IFí; \ a industrial

<img file="MX337306B_D0055.tif" />

one port 304. Each storage device interface and media read interface are arranged and configured so that they do not interfere with the information communicated through the connection cable.

In other embodiments, other types of interfaces are used. For example, in one such alternative embodiment, a two-line interface with a single charge pump is used. In other embodiments, additional lines are provided (eg, for potential future applications).

Examples of such 312 'fiber cable connections and 314' connectors are described in United States Provisional Patent Application Act No. 61 / 252,386, filed October 6, 2009, entitled

MANAGED CONNECTIVITY IN FIBER OPTIC SYSTEMS AND THEIR METHODS (referred to here as the '386 application), the United States provisional patent application minutes No. 61 / 303,961, filed on February 12, 2010, entitled FIBER PINS and

SENSORS FOR MANAGED CONNECTIVITY (the '961 application), and United States provisional patent application No. 61 / 303,948, filed on February 12, 2010, titled SYSTEM OF COMMUNICATIONS OF

BLADE TYPE (the '948 application). The '386 application,

<img file="MX337306B_D0056.tif" />

The '961 application and the '94 8 application are incorporated herein by reference.

In some implementations of connecting cables 312 and 312 ', each pin 314 or connector 314' includes within itself the respective storage device and the interface of the storage device. In some implementations, each storage device and corresponding storage device interface are housed within a housing that is independent of the corresponding plug or connector. In such implementations, the enclosure is configured so that it can fit into (or otherwise connect to) the cable or plug or connector, with the interface of the storage device positioned relative to the plug or connector so that the interface of the storage device is properly paired with the relevant media read interface when the plug or connector is inserted into the front connector of the corresponding port 304.

A portable test set can be provided that includes a port into which you can insert pin 314 or connector 314 'of a 312 or 312' connecting cable to read media information

<img file="MX337306B_D0057.tif" />

Stored on the almat-prwiriipfttQ — F1 device, portable test _set_ also includes a monitor of some kind to display the media information read from the storage device.

In other embodiments, the storage device also includes an optical or infrared interface to read the media information stored in the storage device while the corresponding connection cable 312 or 312 'connects to one or more connection panels 302. This allows the technician to read the media information stored on the storage device without having to remove connection cable 312 or 312 'to use the portable tester described above.

The remainder of the description of the embodiment shown in FIGS. 3 to 11 generally refers to connection cable 312 shown in FIG. 6. However, it will be understood that other connecting cables (such as connecting cable 312 'shown in

FIG. 7).

FIG. 8 is a block diagram of one embodiment of an aggregation point 353. The particular embodiment of an aggregation point 353 shown in

FIG. 8 is described herein as being implemented for use in the system 300 of FIG. 3, although other embodiments can be implemented in other ways.

MEXICAN INSTITUTE OF THE PROnrpA! ·

To the

<img file="MX337306B_D0058.tif" />

Aggregation point 353 is typically implemented as software 800 running on a workstation or other 802 computer. Workstation 802 comprises at least one programmable processor 804 on which software 800 runs. Software 800 comprises program instructions that are stored (or otherwise instrumented) on a suitable storage medium or media from which at least a portion of the program instructions is read by programmable processor 804 to be executed that way. Workstation 802 also comprises memory 806 for storing program instructions and any related information during execution of software 800.

The 802 workstation on which the aggregation point 800 software runs also includes one or more interfaces 808 that communicatively couple the aggregation point 353 to the devices or entities with which it communicates. More specifically, one or more interfaces 808 communicatively couple the aggregation point 353 to these devices or entities in one 350. In an implementation of less than one of the ETHERNET network interfaces 808 to couple

353 to one or more IP 350 networks.

i: ·²- 0 i

ílACKOmüAD CV ~ - 5¾ industrial or magical IP networks said implementation, since an interface includes the aggregation point i · ¡Nifjru'Í D / ·. FROM i

Aggregation point 800 software comprises PLI 810 aggregation software that allows aggregation point 353 to automatically discover and connect to devices that are capable of providing PLI and other information to aggregation point 353 (such as patch panels 302). The aggregation point 353 and the PLI 810 aggregation software can be used to receive the physical layer information from various types of connector sets that have the functionality to automatically read the information stored in or on a physical media segment. Examples of such devices are mentioned above and include, for example, patch panels 302 and network interconnect devices. Also, the 353 aggregation point and 810 PLI aggregation software can be used to receive the physical layer information from other types of devices that have the functionality of

<img file="MX337306B_D0059.tif" />

ί. &amp; Π »INÍ: ':' .:: i .......

* D £ LÁ?. · '.Θ! ΖΓο_Α5

T UiUWfíílAL Ί automatically read the information aTmacéíTatta ^ -en- · © -......

on the physical media segment.

Examples of such devices include end-user devices - such as computers, peripherals (eg, printers, copiers, storage devices, and scanners) and IP phones - that include the functionality to automatically read information stored in or on the media segment. communication physicists.

In the particular embodiment shown in FIG. 8, PLI 810 aggregation software comprises 812 software that uses one or more discovery protocols to discover and connect to devices that are capable of supplying PLI information to aggregation point 353 (assuming that those devices also support those discovery protocols). Examples of discovery protocols include, without limitation, DNS Multicast (mDNS), the Service Discovery Protocol

Based on DNS (DNS-SD), the Connect and Use Protocol

Universal (UPnP), the Discovery Protocol of

Simple Device (SDDP) and Service Location Protocol (SLP), as well as proprietary protocols, and extensions of other protocols (such as

Τ5 ΤΓ

51. X Έ_ MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY

<img file="MX337306B_D0060.tif" />

the Main Configuration Protocol— “Dynamic (DHCP)). In this embodiment, when a 3 02 patch panel (or other device that is capable of providing PLI information to the aggregation point 353) is first coupled to the LAN 352, the MPU 330 of the 3 02 patch panel first gets Place an IP address (typically from a DHCP server for LAN 352). The MPU 330 in connection panel 302 then uses the discovery protocol to broadcast an informational message to the other nodes in LAN 353. The informational message includes information about the services that connection panel 302 provides, which they include in this case services related to the provision of information

PLI to patch panel 302 and patch cords 312 coupled to patch panels 302. Aggregation point 353 listens for such informational messages. When the aggregation point 353 receives an informational message from a connection panel 302 that it can manage, the aggregation point 353 uses the discovery protocols to send a corresponding message to the connection panel 302 (using the address information included in the informational message received) requesting more information on connection panel 302. In response to this request, the MPU 33 0 on the connection panel 3 02 provides the requested information. At this point, aggregation point 353 is capable of controlling and receiving notifications from MPU 330 on patch panel 302. Similar processing can be done when the other devices that provide the PLI to an aggregation point 353 (such as the network interconnection device) add to the

LAN 352.

Also, when an aggregation point 353 is connected to LAN 352, discovery protocol software 812 uses discovery protocols to broadcast an informational message to all nodes on LAN 352. This message indicates that aggregation point 353 You are searching for the devices and / or services that include the PLI functionality described here. Devices that are capable of providing PLI to an aggregation point (devices like patch panels 320 and infrared devices) are on the lookout for such messages. If those devices meet the search criteria set forth in the message, the devices respond with an appropriate message promoting the services they provide. When the

IMPIO * · 13ΤιTUTO MEXICaíSO f ¿^ 5w Ü ​​£ LA FROilEDAD ^V

INDIUJ KI / .L aggregation point 353 receives said- · menea je —- ete - «n device that can manage, the 812 software sends a message to that device (using the address information included in the included message) requesting more information about that device. In response to this request, the device provides the requested information to aggregation point 353. At this time, aggregation point 353 is capable of controlling and receiving notifications from the device.

In this way, when devices that are capable of providing PLI to an aggregation point dock to LAN 352, aggregation points 353 are able to automatically discover the device and start adding physical layer information for that device without requiring have a technician install the device to find out the aggregation points found on LAN 352. Similarly, when aggregation point 353 is attached to LAN 352, aggregation point 353 is capable of automatically discovering and interacting with devices that are capable of providing PLI to aggregation point 353 without requiring the technician to install the 353 aggregation point to know the devices that are

<img file="MX337306B_D0061.tif" />

found on LAN 352. Thus, 'resources - of —......

Physical layer information described here can be easily integrated into LAN 352.

In the embodiment shown in FIG. 8, PLI 810 aggregation software also includes 814 software that is configured to retrieve physical layer information from devices it has discovered and connects using 812 discovery protocol software (for example, devices such as patch panels 302 and infrared devices). An 816 database manager is used to store the PLI information that the 810 aggregation software obtains in a database. In the particular embodiment shown in FIG. 8, software 814 uses one or more suitable protocols to transmit physical layer information to and from said devices. Examples of protocols that can be used include, without limitation, the

File Transfer (FTP), Trivial File Transfer Protocol (TFTP), Protocol

Hypertext Transfer (HTTP), the Protocol

Simple Network Management (SNMP), the Common Gateway Interface Protocol (CGI), the Protocol of

Representative State Transfer (REST) ​​and the

<img file="MX337306B_D0062.tif" />

<img file="MX337306B_D0063.tif" />

τ »-

IiNjJ i *

<img file="MX337306B_D0064.tif" />

'' RCí'ííDad

INDUSTRIAL

Simple Object Access Protocol (SOAPTT ^ 'WS ·' · 'devices from which aggregation point 353 receives information also implement at least some of the protocols implemented by aggregation point 353 to organize, track, store and communicate information on physical layer.

Aggregation point 353 and aggregation software 810 can also be used to obtain other types of physical layer information. For example, in this embodiment, aggregation software 810 also obtains information about physical media segments that are not otherwise automatically connected to an aggregation point. An example of such information is information about unconnected cables that do not otherwise have information stored in or about them that are connected to a patch panel 302 (including, for example, information indicating which of the ports on the control panel connection 302 are connected to which of the ports of other devices on network 350 through that cable as well as media information about the cable).

Another example of such information is information about the connection cables that are connected to 'Q ι-ι • ¿ί ·' · 'V', -Γ-ΐί '-' Ί

<img file="MX337306B_D0065.tif" />

industrial devices that are unable to read ^ PTarfeMeaei &amp; i. * »»: of media that is stored in or on the connection cables that are connected to its ports and / or that are not capable of communicating said information to the aggregation point 353 (for example, because said devices do not include said functionality, because said devices are use with patch cords that do not have media information stored in or on them, and / or because bandwidth is not available to communicate that information to aggregation point 353). In this example, this information may include, for example, information about the devices themselves (such as the MAC addresses of the devices and the IP addresses if assigned to those devices), information that indicates which ports on the devices are connected to which ports on the device. other devices on the network and information about the physical media connected to the device ports. This information can be provided to aggregation point 353, for example, by manually entering such information into a file (such as a spreadsheet) and then uploading the file to aggregation point 353 in connection with the initial installation of each of the different items. Such information can also, for example, be entered directly

INDUSTRIAL using a user interface provided by the 353 aggregation point (eg using a web browser). In the embodiment shown in FIG. 8, the 810 aggregation point software includes an 818 web server to facilitate the upload of files and / or the direct entry of said manually entered information.

The 810 aggregation software can also obtain information on the design of the building or buildings in which the 350 network is installed, as well as information indicating where each device of the connection panel 302, the connection cable (or other item of physical means of communication) and the network interconnection device within the building. This information can, for example, be entered manually and loaded into aggregation point 353 in connection with the initial installation of each of the various items. In one implementation, said location information includes an X, Y, and Z location for each of the ports or another termination point for each physical media segment that terminates on network 350 (for example, location information X, Y and Z of the type specified in the ANSI / TIA / EIA Standard

<img file="MX337306B_D0066.tif" />

606-A - Administration Standard for

Commercial Telecommunications Infrastructure).

810 aggregation software can also obtain and maintain evidence, media quality, or performance information related to the various physical media items that exist on the network. Testing, media quality, or performance information, for example, may be the result of tests that are performed when a particular media segment is manufactured and / or when tests are performed when a particular media segment is installed or is controlled in another way.

The 810 aggregation software also provides an interface for external devices or entities to access the physical layer information maintained by the 353 aggregation point. This access may include retrieving information from the 353 aggregation point as well as providing information to the point of aggregation. aggregation 353. In this embodiment, aggregation point 353 is implemented as middleware that is capable of providing such external devices and entities transparent and convenient access to the PLI maintained by the access point.

<img file="MX337306B_D0067.tif" />

353. Since aggregation point 353 'aggregates' of relevant devices on IP network 350 and provides external devices and entities with access to that PLI, external devices and entities do not need to individually interact with all devices on IP network 35 0 that PLIs provide, nor should those devices have the ability to respond to requests from such external devices and entities.

The aggregation point software 810, in the embodiment shown in FIG. 8, implements an 820 application programming interface (API) through which the application layer functionality on such other devices can access the physical layer information maintained by aggregation point 353 using a software development kit (SDK) that describes and documents API 820. In an implementation of such an embodiment, API 820 is configured to use the Simple Object Access (SOAP) protocol for communications between aggregation point 353 and said external devices or entities. In other implementations, other protocols can be used (for example, the protocols

SNMP or CGI).

<img file="MX337306B_D0068.tif" />

D¿ í kGÍ 1EÜAO MEXICAN INSTITUTE

INDUSTRIAL

<img file="MX337306B_D0069.tif" />

For example, an application 370 (shown in FIG. 3) running on a computer 356 may use API 820 provided by aggregation point 353 to access PLI information maintained by aggregation point 353 (for example, to retrieve such information from aggregation point 353 and / or to manage information to aggregation point 353). Computer 356 couples to LAN 352 and accesses aggregation point 353 through LAN 352.

FIG. 9 is a block diagram of an embodiment of a network management system (NMS) 380 that is specially configured to use the physical layer information that is available in system 300 of FIG. 3. The particular embodiment of an NMS 380 shown in FIG. 9 is described herein as being implemented for use in the 3 00 system of FIG. 3, although other embodiments can be implemented in other ways.

NMS 380 is typically implemented as software 900 running on a workstation or other computer 902. Workstation 902 comprises at least one programmable processor 904 on which software 900 runs. Software 900 comprises instructions from the program to be stored (ok / T 'ϊγ 1V1 F i

............

1NSTÍTL

OR

Ü «;> USTaÍAL otherwise materialize) in a suitable storage medium or media from which at least a portion of the program instructions is read by programmable processor 904 for execution by that means. Workstation 902 also comprises memory 906 to store program instructions and all related information during execution of software 900.

The workstation 902 on which the NMS 900 software is running also includes one or more interfaces 908 that communicatively couple the NMS 380 to the network elements that the NMS 380 manages and with which it also interacts. More specifically, one or more 908 interfaces communicatively couple NMS 380 with those network elements through one or more IP networks.

350. In one implementation of such an embodiment, at least one of interfaces 908 comprises an ETHERNET network interface for coupling NMS 380 to one or more IP 350 networks.

The NMS 900 software comprises the 910 network management functionality that implements various conventional NMS functions, such as displaying the status information and alarms of the various elements in the managed network. In the particular embodiment described here, the functionality of the NMS 910 includes the functionality of deploying a user interface for the NMS 380 and the information management functionality to organize, transport and store the information received from the managed network elements.

IMPI

MEXICAN INSTITUTE

OF INDUSTRIAL PROPERTY

<img file="MX337306B_D0070.tif" />

The NMS 900 software also includes the 914 Physical Layer Information (PLI) functionality. The PLI 914 functionality is configured to retrieve physical layer information from aggregation point 353 and provide it to the NMS 910 functionality to be used in this way. . The NMS 910 functionality uses the retrieved physical layer information to perform one or more network management functions. In the embodiment shown in FIG. 9, PLI 914 functionality retrieves physical layer information from aggregation point 353 using API 820 (shown in FIG. 8) implemented by aggregation point 353. To do this, PLI 914 functionality supports the protocol used by API 820. NMS 900 software communicates with aggregation point 353 over IP 350 networks. Aggregation point 800 software running on aggregation point r &lt;__ ^ΙΝ5τ'τυτο Mexican industrial property

<img file="MX337306B_D0071.tif" />

353 processes and answers AB3L calls ._from NMS

380.

The recovered physical layer information can be used by NMS 380 to provide Layer 1 resolution (of the OSI model) in the information it displays. For example, in one implementation of the embodiment shown in FIG. 9, the NMS 900 software displays a graphical representation of the managed network showing the logical communication links between various network elements. When a user clicks on one of the logical communication links, the NMS 900 software uses the PLI 914 functionality to display the various physical layer items (for example, physical media, patch panels, and wall outlets) that implement that logical communication link, as well as information about those physical layer items (for example, their location, product name, type, color, length, temperature, etc.) that were recovered from aggregation point 353.

In the particular embodiment shown in FIG. 9, the NMS 900 software also includes the 912 physical layer management functionality that the

<img file="MX337306B_D0072.tif" />

INSTITUTO f / .HXIC'ANO Ce INDUSTRIAL PROPERTY information on physical layer received from aggregation point 353 to carry out various PLM functions. For example, the functionality of PLM 912 allows the NMS 380 to manage connection cable movements, additions, or changes (MAC) for connection panels 302. This can be done through the PLM 912 functionality that communicates MAC information to a computer or other device used by the technician using the 350 network. This information may include physical layer information received from an aggregation point 353 (for example, information identifying the particular ports 304, patch panels 3 02, and patch cables 312 involved in the MAC and their locations as well as information on the visual attributes of the items involved in the MAC).

In addition, the functionality of PLM 912 allows the NMS 380 to receive alarms and warning messages from aggregation point 353 that are related to movements, additions, or changes (for example, when a movement, addition, or change is made. unsolicited or when a requested movement, addition or change was made incorrectly). In other words, the functionality of PLM 912 on NMS 380 can be used to verify that a MAC ¥ A '' Ό Τ J. Jlva X 1.

INS-ΠΤ ITO MEXICANO h

U £ ', \;' ?. ο: ή: ο ·· .Γ) v- *_: . ..Stef

INDUSi'¡GAL requested has been __ ^ impl.emeqtado, properly, and if it was not, inform the technician of the fact. Additionally, the PLM 912 functionality on the NMS 380 can be configured to perform a guided MAC in which the PLM 912 functionality causes the appropriate LEDs 316 to light up or flash on patch panels 302 to assist the technician in identifying ports. 304 involved in a MAC. The PLM 912 functionality can do this using a suitable API call to request LEDs 316 to be lit. Aggregation point 353, in response to that API call, sends a request to the appropriate MPU 330 for the processor modules Slave 318 make LEDs 316 light up.

This MAC functionality can be implemented as a standalone application that is not part of an NMS 380.

Other examples of functions that the NMS 380 can perform using the physical layer information include generating an alarm or warning if a specific default patch cord (or a particular patch cord type) is not used to implement a particular cross-connect, apply other policies and / or use the location information included in the physical layer information to

<img file="MX337306B_D0073.tif" />

assist in E911 or the location-based services (LBS) processing that the NMS 380 supports (for example, to determine where a phone is located

<img file="MX337306B_D0074.tif" />

IP) ·

Another example of PLI-enabled functionality that can be added to an NMS 380 is shown in FIG. 10. FIG. 10 is a flowchart of an exemplary embodiment of a compliance monitoring method on a network that includes the PLI functionality described here. The particular exemplary embodiment of method 1000 shown in FIG. 10 is described herein as being implemented as part of the NMS 380 PLI 914 functionality shown in FIG. 9 for use in system 300 shown in FIG. 3 (although other embodiments can be implemented in other ways).

In such an exemplary embodiment, the physical layer information that is supported by and added to aggregation point 353 includes information about the compliance of various parts of system 300 with various standards. Standards such as the TIA / EIA-568-B family of standards define performance requirements for the various physical layer cabling components that are used to implement networks,

Μ PI

MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY

<img file="MX337306B_D0075.tif" />

performance for a given channel the global channel.

'permalinks ~ inr-1 iiidos within and the performance requirements for

For each channel that is installed, information about the compliance of each connection cable 312 and pin 314 used in the channel with the requirements of the relevant standards is stored in the relevant non-volatile memory 392 (block 1002). This information can be determined through tests carried out by the manufacturer and / or an installer. This information may include an indication of whether or not each component associated with that 312 patch cord meets the relevant performance specifications as well as the underlying performance information used to determine compliance. In other words, the margin or performance envelope for each or such component can be stored in the relevant EEPROM 392. This component compliance data is automatically read when patch cable 312 is connected to port 3 04 of patch panel 302 and communicates with relevant aggregation point 352 (block 1004).

When a particular permanent link is installed (for example, a link between a wall outlet and a

ΊΡ τ

7. ν Á Λ. JL ϋ Ι5Ϊ! Ή) ΤΟ · ΙΕ / (CANO Dz LA i'ROFltCAD LM DUSTRIAL punch panel ”from a patch panel 302), the installer tests the performance of the permanent link and certifies its. compliance with the requirements of the relevant standards (block 1006).

Information on compliance of the permalink with the requirements of the relevant standards is communicated to aggregation point 353 (for example, uploading such information as described above) (block 1008). This information may include an indication of whether or not the permalink meets the permanent performance requirements as well as underlying performance information used to determine compliance. In other words, you can provide the performance margin or envelope for the permalink to aggregation point 353 in addition to an indication of compliance.

In the embodiment shown in FIG. 10, the installer also tests the global channel and certifies the compliance of the general channel with the requirements of the relevant standards (block 1010). Information related to general channel compliance is communicated to aggregation point 353 (for example, uploading such information as

<img file="MX337306B_D0076.tif" />

describes

I .VI iP I Β; .IVm

Ía> P institute .ms; oí;, ·.; ', Ό \ »·· ^ -. · / AD £ LA Í-RCí'íeDaO V' ·. ^

INDUSTRIAL j ^ jí ^ above). Aggregation point 353 then identifies the particular components that were used in the channel when the channel was certified (block 1012). For example, aggregation point 353 knows which of patch cables 312 and patch panel ports 304 were used in the channel when certified. If one of those 312 patch cords is to be replaced in the future, aggregation point 353 is capable of automatically determining that the original basis for certification of channel compliance no longer exists (block 1014). When said 312 connecting cable is replaced, Aggregation point 353 can also automatically determine if the global channel has the ability to maintain compliance with relevant standards by checking whether the replacement patch cord has been certified to meet the specifications of the components required for channel compliance and verifying that the permanent link for the channel remains unflappable and that the connecting cable connects to the same ports as before (block 1016). Such information can be used in troubleshooting network performance problems.

')' / 'ί U

XtX AA

INSTITUTO MEXICANO Di LA FAOHEDAD

INDUSTRIAL

<img file="MX337306B_D0077.tif" />

Method 1000 is an example of how you can — uLili'¿a * jr such compliance information. Also, the embodiment of method 1000 shown in FIG. 10 is described herein as being implemented in NMS 380 of FIG. 8, although it will be understood that similar functionality may be implemented in other parts of system 300 (for example, at aggregation point 353 or as a standalone application). In addition, other types of compliance information can be received and stored through an aggregation point and used in compliance tracking. Examples of such compliance information include, without limitation, compliance information regarding communications, standards, military rules, regulations, laws, specifications, and standards.

FIG. 11 is a block diagram of an embodiment of a network interconnection device 354 that is specially configured to use the physical layer information made available by the system 300 of FIG. 3. The particular embodiment of a network interconnection device 354 shown in FIG. 11 is described herein as being implemented for use in the system 300 of FIG. 3,

<img file="MX337306B_D0078.tif" />

although other realizations can be implemented in other ways.

In the embodiment shown in FIG. 11, the network interconnect device 354 comprises at least one programmable processor 1100 that runs the software 1102 (referred to as firmware in some embodiments) that causes the network interconnect device 354 to perform several of the functions described below. Software 1102 comprises program instructions that are stored (or otherwise incorporated) on a suitable storage medium or media (eg, a flash memory) from which at least a portion of the program instructions is read by the 1100 programmable processor for execution. Network interconnect device 354 also includes memory 1104 that is coupled to programmable processor 1100 to store program instructions and data.

Network interconnection device 354 includes a plurality of ports 1106. Each port 1106 includes an interface suitable for coupling the physical means of communication to the interconnection device ϊ Μ Ρ ί "

MEXICaHO INSTITUTE OF INDUSTRIAL FACILITY

<img file="MX337306B_D0079.tif" />

of networks 1106. Each of said interfaces includes, for example, a mechanical structure to connect the physical communication means to the network interconnection device 354 and a physical layer device (PHY) to send and receive signals through the means connected communication. In one such embodiment, ports 1106 are ETHERNET ports.

The software 1102 comprises the network interconnection functionality 1108 which causes the network interconnection device 354 to perform one or more of the network interconnection functions for which it was designed. Examples of network interconnect functions include Layer 1, Layer 2, and Layer 3 (of the OSI model) network interconnect functions such as routing, switching, repeating, bridging, and maintaining traffic of communication that is received in the network interconnection device 354 through the plurality of ports 1106.

The software 1102 also comprises the management functionality 1110 that allows the network interconnection device 354 to be configured and managed. In the particular embodiment shown in FIG. 11, the 1110 management functionality includes a web server 'i /%. * - &lt;

2, * Λ · '

Ά li? Fr'ynruTC ·

Say L \ 'V κ ad fHD'JJTAI .'- L (and the web content and applications_-xe ± aci_Qíiada.si that allows a user to directly interact with the 354 network interconnect device using a web browser. In this In one embodiment, the 1110 management functionality also includes SNMP functionality to interact with an NMS (such as NMS 380) using the SNMP protocol. SNMP commands and responses communicate over one or more IP networks 350 through one or more of ports 1106 of network interconnect device 354.

Software 1102 also includes the 1112 Physical Layer Information (PLI) functionality. The 1112 PLI functionality is configured to retrieve physical layer information from aggregation point 353 and to provide it to the 1108 network interconnect functionality. Network Interconnect 1108 uses the recovered physical layer information to perform one or more network interconnect functions. In the embodiment shown in FIG. 11, functionality

PLI 1112 retrieves physical layer information from aggregation point 353 using API 820 (shown in FIG. 8) implemented by aggregation point 353. To do this, PLI functionality to IVa jc i

IAEXICAN INSTITUTE OF PROPERTY

INDUSTRIAL

<img file="MX337306B_D0080.tif" />

1112 supports the protocol used by API 820. Software 1102 on network interconnect device 354 communicates with aggregation point 353 through IP 350 networks. Software for aggregation point 800 running at the point of Aggregation 353 processes and responds to API calls from network interconnect device 354. Network interconnect device 354 also retrieves at least some physical layer information from an NMS or other network element.

Some communication protocols (for example, the IEEE 802.3 family of ETHERNET standards) include the functionality to automatically determine an appropriate communication rate for a communication link (for example, the IEEE 802.3 auto-negotiation, auto-detection and auto-response functions ). This type of functionality tests to achieve these determinations. In other words, the physical means of communication are still, from the perspective of said network interconnection device, a black box. The physical layer information provided to the 1108 network interconnect functionality through the PLI 1112 functionality enables the functionality of

<img file="MX337306B_D0081.tif" />

(Ί3Τi TUTO: á EX [cA NO L't THE PROPERTY

IiiDUSTKIAL

<img file="MX337306B_D0082.tif" />

1108 network interconnect to treat the physical layer as a white box for which you have the exact information that you will use to carry out your network interconnect function (for example, for use in bridging, routing, or switching decision making) . In an implementation of said embodiment, the information on the physical layer received from the aggregation point 353 is provided to the network interconnection functionality 1108 for assistance in carrying out said procedures for selecting said automatic rate.

Furthermore, when such conventional rate determination functionality is used to make network interconnection decisions (such as, port-related decisions where to route information), as conventional functionality is typically only capable of characterizing communication links that are directly connected to the network interconnection device. This means that if there is a segment of physical communication media that is one or more hops away from the network interconnection device that is of lower quality (for example, because it supports a lower communication rate) than the physical media of

INSTITUTE .'ALA &lt;·,.: ·.) V^;'.

E'E LA PjCrlK. ' .Aj V * '; -_c.

ÍNL'US'I communication used to implement · ^ · -®Í..snl_!ac &amp; .._lSince it is directly connected to the network interconnection device, the network interconnection device would not be aware of that fact and would not take this fact into account when making routing or other decisions on network interconnection policies. In the embodiment shown in FIG. 11, the physical layer information received from aggregation point 353 (and from other sources such as NMS 380) can be used to identify such situations and respond accordingly.

The physical layer information received from aggregation point 3 53 can be used in other ways. For example, network interconnect functionality 1108 can be configured to restrict routing of communication traffic through a policy that dictates that traffic received on some ports 1106 can only be communicated through certain areas of a building or buildings (for example, only through secure areas of the building). For such a policy to apply, the 1108 network interconnect functionality needs to know where the traffic leaving each of its ports will pass. The information on the physical layer received from the

-¿S »

<img file="MX337306B_D0083.tif" />

ΙΝ / ΎΓΓΙΠΟ -V.ÍXtCA DE LA ¡TíCHir »aggregation point 353 can be used for such determinations.

In another example, the 1108 network interconnect functionality is configured to enforce a policy that requires only certain types of physical communication media to be used with it (for example, requiring the use of certain brands or types or lengths of patch cords ). The information on the physical layer received from the aggregation point 353 can be used through the network interconnection functionality 1108 to apply said policy (for example, not forward the information received on ports 1106 that have incompatible means connected to them and / or generate alarms or warnings when unsupported media is connected to port 1106). In other words, the network interconnect functionality 1108 can be configured to act as a bus gatekeeper applying a virtual encryption scheme in which at least some media information stored in or on a connection cable 312 is used to encode the connection cable 312.

As noted above in connection with FIG. 1, network interconnection devices also

Ρϊ

MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY

<img file="MX337306B_D0084.tif" />

they may include a read interface — media to read the media information that is stored in or on the physical media segments that are connected to its ports and to communicate the media information that is read from the connected media segments (as well as also information about the network interconnection device itself) to an aggregation point. For example, as shown in FIG. 11, each port 1106 has an associated media read interface 1120 that the programmable processor 1100 uses to read the media information that is stored in or on the physical media segments that are connected to its ports 1106. The programmable processor 1100 in This example communicates the media information it has read to a suitable aggregation point using one or more of the communication links that are established through one of its ports 1106.

In other implementations, the network interconnection device 354 does not include a media read interface and the information on the physical layer related to the physical media connected to its ports is provided to an aggregation point of

<img file="MX337306B_D0085.tif" />

INSTíT '.

OF THE>

other ways (for example, loading information).

. INDUSTRIAL manually entering and

FIG. 12 illustrates another example of how the physical layer information that is captured and aggregated using the techniques described here can be used to improve the efficiency of network interconnect devices used in a network. In the example shown in FIG. 12, network 1200 is implemented as a mesh network of Layer 2 devices 1202 (typically ETHERNET switches) linking several ETHERNET 1204 LAN segments. In such an ETHERNET 1200 network, a minimal spanning tree is built and those links that are not part of the spanning tree are disabled by disabling the corresponding switch ports 1202. As a result, there is a single active route between any two nodes on the 1200 network One or more redundant links can also be defined to provide backup routes that can be used if a link fails on the active path. The spanning tree is built to prevent loops.

In conventional ETHERNET networks, a spanning tree protocol that complies with the IEEE 802.ID MAC Bridges standard is used to build a

100

<img file="MX337306B_D0086.tif" />

2Λ. , j% _ * -Ai ,. -λ *

INSTITUTO MEXICANO D £ LA PROPIEDAD INDUSTRIAL spanning tree for the network. However, the spanning tree algorithm used in conventional ETHERNET networks is a distributed algorithm, in which the relevant switch must learn which devices are connected to it, exchange messages with the other switches, participate in the choice of a root bridge and maintain a routing database. Also, when a new switch is added to the network, all switches in the network must obtain information from the root bridge about any changes in the topology resulting from the addition of the new switch, in which case the other bridge devices must update the bases of routing data they maintain.

Since a spanning tree distributed protocol is used in conventional ETHERNET networks, each switch must include enough processing power to implement the spanning tree protocol and to perform database searches to make decisions about how to forward packets it receives . Additionally, changes in spanning tree topology can take a significant amount of time to propagate across the network, which can lead to degraded network performance, or

101

<img file="MX337306B_D0087.tif" />

IWS? Π ÍJT.'J Λ ^: , )

LA ΐϊ-HWi ¡UAL

<img file="MX337306B_D0088.tif" />

in some cases, loops. Also, the extent to which a conventional switch can learn about the network is limited, which can also degrade network performance.

Furthermore, each of said conventional switches typically uses transparent bridging to forward packets using the routing database. The routing database is initially empty, and entries are entered into the database as the switch receives packets. When a switch receives a packet, it inspects the source MAC address of the packet and adds an entry to the routing database for that source MAC address (if one doesn't already exist) that associates that MAC address with the port on which package was received. The switch also inspects the destination MAC address of the packet and looks for an entry in the routing database for that destination MAC address. If an entry is not found in the routing database for that destination MAC address, the packet is flooded on all other ports on the switch. In the future, when the switch receives a packet from the device that has that MAC address as its

102 ίΜ Ρ .1

<img file="MX337306B_D0089.tif" />

INSTITUTE MfXIfW.ot> £ LA TROHF.Oa ·, to industrial X ^ -as * source, the switch adds an entry ^ », a., ... sn routing data base that associates that MAC address with the port in which the package was received. In this way, the switch is able to build a routing database over time. The routing database must be updated as the network topology changes (for example, due to movement or removal of a patch cord, failure of links, addition or deletion of a switch, or movement of an end user device).

Since the routing database is maintained individually on each switch in a conventional ETHERNET network, each of these switches must have enough processing power to perform such processing. Also, when changes to the network topology occur, network performance may degrade as switches flood the network to learn the new network topology.

In the example shown in FIG. 12, the centralized bridge functionality 1206 is installed on the 1200 network to alleviate some of the problems stated above. The centralized bridge functionality 1206

103

<img file="MX337306B_D0090.tif" />

interacts with one or more aggregation points ~ i3QS ,, .. which add information about the physical layer for the 1200 network. In the particular example shown in FIG. 12, the center bridge functionality 1206 is installed on an NMS 1210. Aggregation point 1208 collects the MAC addresses of the end devices 1212 that are in the 1200 network as well as information about the 1202 switches.

In the example shown in FIG. 12, for some end devices 1212, the media information for each physical media segment connecting each of said end devices 1212 to a switch 12 02 is automatically read and communicated to an aggregation point 1208. That is, the end devices 1212 include a suitable media read interface and a software driver to read the media information that is stored on an ETHERNET cable connected to those end devices 1212 and provide the media information for the ETHERNET cable, as well as the MAC address for the 1212 end devices and their current IP address, to a 1208 aggregation point. If end devices 1212 are connected to a switch 1202 through one or more intermediary devices (such as a

104

<img file="MX337306B_D0091.tif" />

wall outlet and one or more panels of one of such intermediary devices would include the appropriate media reading interface functionality to read the media information and provide it to the aggregation point 1208. In this way, the aggregation point 1208 could associate the MAC address of each such end device 1212 with a switch port 1202.

Also, in the example shown in FIG. 12, for some of the end devices 1212, the media information for at least one physical communication media segment connecting each of said end devices 1212 to a switch 1202 is not automatically read and communicated to an aggregation point 1208. For these 1212 end devices, the physical layer information for each physical media segment connecting the 1212 end devices to switch ports 1202 and the MAC addresses to the 1212 end devices can be manually entered and loaded at the aggregation point 1208 (as described above). Alternatively, center bridge functionality 1206 and / or aggregation point 1208 can obtain such information in other ways. By

105

ΪΜΡΙ

INSTITUTE x; r..¿:_Cz. t> E LA U5.0? Ít ~ O, <· ';

YES Yes, the associations between the MAC addresses of the end devices 1212 and the ports of switch 1202 can be known from NMS 1210.

The functionality of the central bridge 1206 uses the physical layer information and the MAC address information it has received to associate the MAC address for each of the 1212 end devices with the particular switch port 1202 to which the 1212 end devices connect. . The center bridge functionality 1206 then determines a minimum spanning tree for the 1200 network using that information and determines a corresponding STP state (typically blocking, forwarding, or disabling) for each of the ports on each switch 1202. The functionality central bridge

1206 it then determines how the routing database for each of the switches 1202 should be configured based on the spanning tree and the MAC address information that the central bridge functionality 1206 has. The port status information and the routing database information is then communicated to each of the switches 1202.

106

<img file="MX337306B_D0092.tif" />

Each of the corresponding bridge functionality switches 1202 1214 to receive the port status information and routing database information of the core bridge functionality 1206. The bridge functionality 1214 on each switch 1202 configures switch 1202. so that each port is in the particular STP state specified by the 1206 central bridge functionality for it. Also, the bridge functionality 1214 on each switch 1202 uses the routing database information it receives from the central bridge functionality 1206 to configure its routing database 1216.

When changes occur in the 1200 network, the aggregation point 1208 (and / or the other source of the MAC address information such as the NMS 1210) will see the changes and provide updated information to the central bridge 1206 functionality. 1206 core bridge functionality can modify the spanning tree topology, if necessary, and determine what changes (if any) should be made to the port states of each switch and the databases on the switch.^r i

107

<img file="MX337306B_D0093.tif" />

1216 routing in response to camBToI

1200.

By allowing core bridge functionality 1206 to determine spanning tree for network 1200 and configure routing databases 1216 on switches 1202, switches 1202 do not need to perform such processing and instead resources on the Switch 1202 can be dedicated to forwarding packets. Also, the 1206 core bridge functionality is capable of directly knowing changes in the 1200 network from aggregation point 1208 and responding quickly to those changes, and communicating any necessary changes to switches 1202. All of this should improve the 1200 network performance. In addition, the center bridge functionality 1206, because it has access to more information about the 1200 network, can more effectively create the spanning tree (for example, by mounting the spanning tree based on the type, number, number, location, length, etc. of the physical communication means used to implement the various logical communication links in the 1200 network).

108

<img file="MX337306B_D0094.tif" />

FIG. 13 illustrates an alternative embodiment of a 3 00 'system that includes the physical layer information functionality as well as the physical layer management functionality. The system

300 'is similar to system 300 of FIG. 3 except as described below. Reference is made to those elements of the system 300 'which are identical to the corresponding elements of the system 300 in FIG. 13 using the same reference numerals, and the description of said elements is not repeated below in connection with FIG. 13.

The main difference between system 300 of FIG. 3 and the system 300 'of FIG. 13 is that, in the system 300 'of FIG. 13, the master processor unit and the slave processor unit are combined into a single combined master / slave processor unit 330/318 which is included in each patch panel 302 '. That is, each patch panel 302 'includes the functionality of the master processor unit 330 shown in FIG. 6 (For example, each patch panel 302 'includes a master processor 332 and an ETHERNET interface 340). Also, each patch panel 3 02 'directly communicates with an appropriate aggregation point 353. Accordingly, it is not

109 .ίί.

ΪΝ.

Ρϊ Ρ1

J'i'U'í '. ·' ·. · '\' ·· -. · .->

say the ín.vjsi; ual

<img file="MX337306B_D0095.tif" />

a back plane parS is required.

functionality of the master processor unit and functionality of the slave processor unit.

FIG. 14-16 illustrate yet another alternative embodiment of a system 300 that includes the physical layer information functionality as well as the physical layer management functionality. System 300 is similar to system 300 of FIG. 3 except as described below. Reference is made to those elements of system 300 that are identical to corresponding elements of system 300 in FIGS.

to 16 using the same reference numerals, and the description of said elements is not repeated below in connection with FIG. 14 to 16.

The main difference between system 300 of FIG. 3 and system 300 of FIGS. 14-16 is that patch panels 302 and MPU 330 communicate over a main bus 328 using the protocols specified in the Institute of Electrical and Electronics Engineers (IEEE) standard 802.14.5. Although IEEE 802.14.5 protocols are typically used for wireless communications, in the embodiment shown in FIG. 14 to 16, the connection panels 3 02 and the MPU 33 0

110 O 'i)' á i JV iNsnrj-fc> L'Ü LA! ';

JM uses the IEEE 8 02 protocols. L4TTⁱ'p * áírS ^J1-communicate through one or more CATV coaxial cables.

In said embodiment, the main bus 328 is physically implemented using one or more coaxial cables, in which the information communications are communicated through the coaxial cables in a suitable radio frequency through which the MPU 330 supplies DC power through of coaxial cables for use by the active components of each patch panel 302. Slave processor module 318 in each patch panel 302 includes a suitable bus interface 326 (shown in FIG. 15) for coupling slave processor 320 to master processor module 330, and master processor unit 330 includes a suitable bus 338 (shown in FIG. 16).

In such an embodiment, the software of the connection panel 322 and the interfaces of the main bus 326 of each connection panel 302 and the software of the MPU 334 and the interface of the main bus 338 of the MPU 330 comprise the appropriate functionality that allows the programmable processor 320 on each patch panel 3 02 and programmable processor 332 on MPU 330 send and receive information using the IEEE protocol

111

Ϊ íVÍ Ρ ϊ

802.14.5 as well as connectors (such as connectors

F) to connect each connection panel 3 02 and the

MPU 330 to the coaxial cables used to implement the main bus 328 (through, for example, a branch or a splitter). The IEEE 802.14.5 addressing scheme protocols support up to 127 patch panels (each 302 'patch panel supports up to 48 ports for a total of 6096 ports) and one 330 MPU. The IEEE 802.14.5 protocols are designed for low energy applications that are specifically suitable for use in the embodiment shown in FIG. 14 to 16.

Also, in the embodiment shown in FIGS. 14 to

16, power is supplied to each patch panel 302 (more specifically, to the active components of each patch panel 302) through the main bus 328. The PSU 344 in the MPU 330 converts the external power received from the power source 346 to provide power that is suitable for use by the components of MPU 330 and for supply to patch panels 302.

FIG. 17 is a block diagram of one embodiment of a wall outlet 1700 that includes the functionality of obtaining information on the physical layer.

112

<img file="MX337306B_D0096.tif" />

The embodiment of a wall outlet 1700 shown in FIG. 17 is described herein as being implemented for use with the system 100 of FIG. 1, although other embodiments may be implemented in other ways.

Wall outlet 17 00 is configured to be installed on or on a wall or similar structure. Wall outlet 1700 includes a set of ports 1702 similar to the ports described above in connection with FIGS. 1 to 6. Ports 17 02 which are also referred to here as Receive Ports 1702. In general, each receive port 1702 includes a respective front connector (or other connection point) to which a connected cable (or other physical media segment) can be connected. An example of such a connected cable is a twisted pair cable that has RJ-45 plugs at each end. Each receive port 1702 also includes a rear connection point that is connected to a corresponding port on a switch 1708. Switch 1708 is used to communicatively couple each of the receive ports 1702 to a patch panel (not shown in FIG. 17) via a single cable, which is connected to wall outlet 1700 through a port broadcast

113

<img file="MX337306B_D0097.tif" />

1712. In one implementation of such an embodiment, broadcast port 1712 is configured for use with an unconnected cable. This cable is typically run through a building (eg, above, below, around, and / or through walls, ceilings, floors, and the like) and is typically not moved easily or frequently.

Switch 1708 includes a switch function 1710 that switches information packets between receive ports 1702 and send port 1712. Switch function 1710 is implemented, for example, in software, hardware, or combinations thereof.

The receive ports 1702 of the wall outlet 1700 are configured for use with connected cables that have media information stored in or on them (eg, as described above in connection with FIGS. 1-16). Wall outlet 1700 includes a media read interface 1704 for each receive port 1702. In this embodiment, a media read interface 1704 is implemented in the same manner as the media read interface described above in connection with FIGS. 1 to 16. Each media read interface

114

I> 1 ri

INSTITUTO iÁl.ykMNO D- LA P'rODEL'A. '} ÍNDUSVt' .- 1704 is used to read the media information stored in or on the connected cable that is inserted into the corresponding reception port 1702. The media information which is read from the connected cables which are inserted into the receiving ports

1702 communicates from the multimedia read interfaces 1704 to a programmable processor 1706. In the embodiment shown in FIG. 17, the programmable processor 1706 is a part of switch 1708.

Programmable processor 1706 executes software that is similar to software that is executed by the programmable processors described above in connection with FIGS. 1 to 6 (including, for example, a web server or other software that allows a user to interact with the 1706 processor). The main difference is that the programmable processor 1706, in the embodiment shown in FIG. 17 communicates with a suitable aggregation point using the logical communication link provided using broadcast port 1712. Wall outlet 1700 can be used to capture and communicate physical layer information related to the appropriate aggregation point. the 1700 wall outlet itself, the connected cables inserted into the ports of

115

<img file="MX337306B_D0098.tif" />

>. Λ

INSTITUTO MEXICANO Ύέ * DE LA PRONEDAD INDUSTRIAL reception 17 02, and the cable not connected to the · · time-of-broadcast 1712.

As noted above, the techniques described here for reading media information stored in or about a physical media segment can be used at one or more network end nodes. For example, computers (such as laptops, servers, desktop computers, or special-purpose computing devices, such as IP phones, IP multimedia devices and storage devices) can be configured to read the media information that is stored in or on the physical media segments that are connected to its ports and to communicate the media information that is read from the media segments connected (as well as information about the device itself) to an aggregation point. FIG. 18 is an embodiment of said 1800 computer. Computer 1800 includes a 1802 red card interface (NIC) that is used to connect computer 1800 to an IP network (for example, an ETHERNET local area network). NIC 1802 includes a port 1804 that is used to physically connect a suitable cable (for example, a CAT-5/6/7 cable) to

116

<img file="MX337306B_D0099.tif" />

NIC 1802. NIC 1804 also »standard NIC functionality 1806 for communication over the IP network (eg a suitable physical layer device (PHY) and a Media Access Control (MAC) device). NIC 1802 enables one or more 18 08 processors (and the 1810 software running there) included in the 1800 computer to communicate with the IP network. In this embodiment, the NIC

1802 it includes a media read interface 1812 that uses one or more of the processors 1808 to read the media information stored on or on the cable that is connected to the 18 00 computer. The media information that is read from the cable, as well as also information about NIC 1802 and computer 1800 (for example, any assigned MAC addresses or IP addresses), can be communicated to a suitable aggregation point, as described above. In an implementation of such an embodiment, a NIC 1814 software driver used with NIC 1802 includes the Physical Layer Information (PLI) functionality 1816 which causes the 1808 processor to read and communicate such physical layer information. NIC 1802 and MRI 1812 are coupled to the 1808 processor using a suitable bus or other interconnect (not shown). In this way, you can

117

<img file="MX337306B_D0100.tif" />

automatically obtain and use information about the 1800 computer in the various applications described.

The functionality of reading the media information stored in or on the physical communication media can be integrated into one or more of the integrated circuits (or other circuits or devices) that communicate through the communication media. For example, the reading functionality of such media information can be integrated into an ETHERNET physical layer device used in a switch. One such example is shown in

FIG. 19.

FIG. 19 is a block diagram of an exemplary embodiment of an ETHERNET 1900 switch using a physical layer device (PHY) 1902 that includes the built-in functionality of reading media information. In the particular exemplary embodiment shown in FIG. 19, PHY 1902 is an octal ETHERNET PHY that includes ETHERNET physical layer functionality for eight ETHERNET ports (although it will be understood that the techniques described herein in connection with FIG. 19 can be used with physical layer devices that have a different number of

118

<img file="MX337306B_D0101.tif" />

ports). In this embodiment, eight shots are coupled

RJ-45 1904 to PHY 1902. Each of the RJ-45 jacks

1904 It is configured to receive an RJ-45 plug attached to a CAT-5, 6, or 7 twisted cable. For each RJ-45 1904 socket, the transmit conductors (TX + and TX-) and the receive conductors (RX + and RX- ) of that RJ-45 socket 1904 are coupled to transmit pins (TX + and TX-) and receive pins (RX + and RX-), respectively, from the

PHY 1902 using suitable isolation transformers (not shown) that are integrated into or external to the 1904 jack.

PHY 1902 includes the required ETHERNET physical sublayers - including a 1908 Physical Media Dependent Sublayer (PMD) (which includes a transceiver suitable for physical communication media used with the 1900 switch), an attached physical media sublayer ( PMA) 1910 (which performs PMA alignment, octet detection / synchronization and scrambling / descrambling), and a 1912 Physical Encryption Sublayer (PCS) (which performs auto-negotiation and encoding / decoding). PHY 1902 also includes a 1914 Media Independent Interface (MU) (for example, a media independent interface, a

119

<img file="MX337306B_D0102.tif" />

independent media interface redjj £ Íd ^^ £ ^ .IJJ., an independent gigabit media interface (GMII), and / or an independent serial media interface (SMII)) to connect the PHY 1902 to an Access Control device a ETHERNET Media (MAC) 1916. As noted above, in the particular exemplary embodiment shown in FIG. 19, PHY 1902 is designed for use in an ETHERNET 1900 switch, and consequently MAC 1916 is a MAC switching device that includes adequate functionality to implement an ETHERNET switch.

PHY 1902 typically also includes other standard ETHERNET physical layer functionality. For example, PHY 1902 includes management functionality 1920 to control and manage PHY 1902 and an information input / output management interface (MDIO) for communication of management information between PHY 1902 and MAC 1916. Other physical functionality of ETHERNET includes Media Dependent Cross Interface (MDIX) functionality and clock functionality (both of which are not shown in FIG. 19).

In the exemplary embodiment shown in FIG. 19, each RJ-45 1904 socket includes a read interface

120

l.

L

V.

<img file="MX337306B_D0103.tif" />

1906 media that can be used to determine ·· -e ± · -a RJ-45 plug is inserted into that RJ-45 socket 1904 and, if one is, to read the media information stored in an EEPROM attached to the RJ- plug 45 (if applicable). Exemplary configurations of said 1906 media interface and an RJ-45 plug are described above and in the '395 application, the' 208 application and the '964 application.

In this embodiment, a four line 1906 media read interface is used. One line is used to communicate information (using a serial information protocol), one line is used for power, and one line is used for ground. In this particular embodiment, a fourth line is also provided for possible future potential uses or updates.

The PHY 1902 includes suitable pins (or other inputs) for connection to each of the eight 1906 media read interfaces. The PHY 1902 also includes the 1918 Physical Layer Information (PLI) functionality that is coupled to all eight interfaces. Reading Media 1906.

121

<img file="MX337306B_D0104.tif" />

In the particular exemplary embodiment shown in FIG. 19, the PLI 1918 functionality is configured to provide the power and ground signals on the power and ground lines of each of the 1906 media read interfaces. For example, the PLI 1918 functionality, in one implementation, is connected to The PHY 1902's main power input to provide an adequate power signal on the power lines of each of the 1906 media read interfaces. Also, the PLI functionality

1918 It connects to the PHY 1902's main ground input to provide a ground connection for each of the ground lines on the 1906 Media Read Interfaces.

In the particular exemplary embodiment shown in FIG. 19, PLI 1918 functionality is configured to control the eight 1906 media read interfaces and determine when a plug has been inserted

RJ-45 on each of the RJ-45 1904 jacks. This can be done using the schemes described in application '395, application' 208 and application '964. The PHY 1902 device includes one or more 1922 records (also referred to as PLI records here

1922) in which the

122

<img file="MX337306B_D0105.tif" />

MEXICAN INSTITUTE OF PROPERTY

INDUSTRIAL

<img file="MX337306B_D0106.tif" />

PLI 1918 functionality stores PLI related information. A PLI 1922 register bit (also referred to as a status bit here) is used to store status information for each of the eight 1904 sockets, where each status bit represents the status of one of the respective sockets 1904. When the state of a particular 1904 socket changes (i.e. when a plug is inserted into a previously empty 1904 socket or a plug is removed from a 1904 socket), the 1918 PLI ​​functionality is able to detect such change and change the state of the corresponding bit in the status bit stored in the PLI 1922 registers.

The PLI 1918 functionality on the PHY 1902 device is also configured, when instructed to do so, to read the media information stored in an EEPROM (if applicable) attached to an RJ-45 plug that is inserted into a 1904 socket. The information read from EEPROM is stored in PLI registers 1922 of device PHY 1902. Also, the PLI 1918 functionality is configured, when instructed to do so, to write the information stored in the PLI 1922 registers to an EEPROM attached to an RJ-45 plug that is inserted into a 1904 socket.

123

Τ ',' i E'i / ti

<img file="MX337306B_D0107.tif" />

MEXICAN INSTITUTE Dt LA PRO »! FIMO

IMDUSTJUAi

<img file="MX337306B_D0108.tif" />

In the particular exemplary embodiment shown in FIG. 19, a main processor 193 0 is coupled to the MAC device 1916 through a suitable main interface. The main processor 1930 runs the 1932 software (also referred to here as the main software). Main software 1932 comprises program instructions that are stored (or otherwise materialized) on a suitable storage medium or media from which at least a portion of the program instructions is read by main processor 1930 for execution .

In this exemplary embodiment, the 1930 core processor includes a 1934 TCP / IP stack and 1936 management software that implements various management and configuration functionalities (for example, a Simple Network Management Protocol (SNMP) agent and a web server and / or TELNET through which a user can interact with management software 1936 running on switch 1900).

In the exemplary embodiment shown in FIG. 19, the 1932 core software also includes the 1938 PLI ​​software that is configured to transmit physical layer information associated with the 1900 switch and the

124

<img file="MX337306B_D0109.tif" />

MEXICAN INSTITUTE OF PROWED

INDUSTRIAL

<img file="MX337306B_D0110.tif" />

cables connected to the aggregation point in the network to which the 1900 switch is connected. In an implementation of the 1900 switch, the PLI 1938 software implements the protocols described above to participate in the discovery processing supported by the aggregation point and to send PLI to the aggregation point. Also, in other implementations, the PLI 1938 software interacts with an aggregation point solely using the API (or other external interface technology) that the aggregation point provides for the application layer functionality to interact with it. In still other implementations, the PLI 1938 software interacts

<td>with the point of aggregation through</td><td>one NMS or another</td>

<td>intermediary device or system</td><td>(for example,</td>

<td>using a protocol supported by</td><td>the NMS as</td>

<td>SNMP).</td><td></td>

<td>PLI 1938 software running on</td><td>processor</td>

Master 1930 periodically reads the status bit stored in PLI registers 1922 in PHY 1902 by instructing MAC device 1916 (through the main interface between 1930 master processor and MAC device 1916) to read the contents of the bit

125

<img file="MX337306B_D0111.tif" />

status (through MDIO interface, _ between jsl MAC 1916 device and PHY 1902 device).

When an RJ-45 plug is inserted into a 1904 socket, the 1938 PLI ​​software running on the 193 0 main processor will know the fact when it reads the status bit stored in the PLI registers 1922 of the PHY 1902 device. Then the software PLI 1938 (via the main interface between the 1930 main processor and the MAC 1916 device) causes the MAC 1916 device to instruct (via the MDIO interface between the MAC 1916 device and the PHY device

1902) PLI 1918 functionality on PHY 1902 device to read media information stored in EEPROM (if applicable) connected to newly inserted RJ-45 plug. The PLI 1918 functionality in the PHY 1902 device stores the media information that it reads from the EEPROM in the PLI 1922 registers. Once this is done, the PLI 1938 software can obtain that media information by making (through the main interface between the 1930 main processor and the MAC 1916 device) the MAC device

1916 Read (through MDIO interface between MAC device 1916 and PHY device 1902) the corresponding PLI records 1922 on the device

126

Χϊ. ... ·, μ ·; · .- - 4

INSTITUTE 'AcXUO.Tj' ·_;.· ¿

DE pyor-o v ^; PHY 1902. The media information on eÁdágX —. MAC 1916 device is then provided to the PLI 1938 software through the main interface. The PLI 1938 software can then communicate this information to an aggregation point, as described above.

In addition to communicating PLIs over switch 1900 and cables connected to sockets 1904 of switch 1900, switch 1900 can also implement one or more of the network interconnection functions described above in connection with FIGS. ll and 12.

Another example of an ETHERNET physical layer device having the integrated functionality of reading the media information stored in or on the physical communication media is shown in FIG. 20. FIG. 20 is a block diagram of an exemplary embodiment of a 2000 computer using a 2002 physical layer device (PHY) that includes the integrated media information reading functionality. Media information reading functionality stored in or on cables

CAT 5, 6 or 7 is integrated into PHY 2002 in the same manner as described above in connection with FIG.

19. Concordantly reference is made to

127 ·'· ·^ΰ--2- Vy / y ^. '4

IMS i í i L- * · · .Vu. '. Y.'óvj \ - - ··,'. · ¹ ..- A cu la -τ. ·, Ηϊζ .. ·· .υ V.>,; / - <-! yy w & vstlul · ____ elements of substantially the computer 2Ú & 0 -—— which ··· «. ·· ^ aon- ..

similar to the corresponding elements described above in connection with FIG. 19 in FIG. 20, using the same text labels as used in FIG. 19 and the reference numerals with the same last two digits as those used in FIG. 19.

A difference between the PHY 2002 of FIG. 20 and PHY 1902 of FIG. 19 is the number of supported ETHERNET ports. PHY 2002 of FIG. 20 supports a single ETHERNET port. Likewise, the MAC device 2016 of FIG. 20 is a MAC device suitable for use in a terminal node device such as a 2000 computer. Also, the software 2032 running on the main processor 2030 is software that is typically executed by an end user computer 2000.

Although FIG. 19 and 20 illustrate particular examples of how the media information reading functionality stored in or on a physical communication medium may be integrated into one or more of the integrated circuits (or other circuits or devices) communicating through the media. communication

128

<img file="MX337306B_D0112.tif" />

MEXICAN INSTITUTE OF PROPERTY

INDUSTRIAL

<img file="MX337306B_D0113.tif" />

You will understand that such media reading functionality can be integrated in other ways.

In other embodiments, the media information is stored in or on unconnected cables or other physical communication media. For example, in such an embodiment, the storage devices are connected near each end of the unconnected cables so that when each end of the cable is connected to a respective connection point, an interface for one of the respective storage devices is paired with a corresponding media read interface located at or near the connection point so that the information stored in the storage device can be read by the storage device in a similar way to that described above. Such embodiments may include punch down connections for connecting copper twisted pair cables to the rear sides of the RJ jacks to Krone type blocks including Insulation Displacement Connectors (IDC). FIG. 21 is a diagram of one embodiment of a cover 2100 that can be fitted around an RJ-45 plug to connect a

129 ζ 'j τ> «· ΰ'

one. Λ \ 'Ά /

ΙαΠΠΖ'.Τ?

lz the; · .Λ ·.; / storage to the RJ-45 plug. Cover 2100 is formed as a molded flexible circuit 2102 having two side walls 2104 and a top wall 2106. Flexible circuit 2102 is formed from one or more flexible films (for example, one or more polymer films) and is configured to fit snugly around an RJ-45 plug so that cover 2100, once placed around the plug, hold firmly to the RJ-45 plug.

In the embodiment shown in FIG. 21, a storage device 2108 (for example, an EEPROM or other non-volatile memory device) is mounted on the external surface of the top wall

2106 of molded flexible circuit 2102. The interface of the storage device to be paired with a media read interface comprises a set of conductive terminals 2110 that are formed on the outer surface of the top wall 2106 and extend down the outer surface of both side walls 2104. At least a portion of terminals 2110 is exposed (i.e. it does not have an insulator formed thereon) so that the corresponding contacts of a media read interface

130

<img file="MX337306B_D0114.tif" />

MEXICAN INSTITUTE EU INDUSTRIAL PROPERTY

<img file="MX337306B_D0115.tif" />

it may come into contact with terminals 2110 when the pin around which cover 2100 is connected is inserted into a port. In such an embodiment, the media read interface contacts can be spring loaded to exert pressure on terminals 2110 to form a good electrical contact. The media read interface can then be used to read the information stored in the storage device 1508 in the manner described above.

Also, in this embodiment, an infrared emitter 2112 is mounted on the outer surface of top wall 2106. Infrared emitter 2112 is configured to emit an infrared signal in which at least a portion of the information stored in the device is encoded. storage 2108. In one implementation, the infrared emitter 2112 is configured to generate the infrared signal with the information encoded there whenever the storage device 2108 is read using the media read interface. Cover 2100 is configured so that a technician can position an infrared detector close to infrared emitter 2112 so as to receive the emitted infrared signal. The

131 infrared detector can be attached, for example, * 'to a portable unit that decodes the ser ^ T “' ^ nTr ^ froJa“¹'' 'received and displays the information encoded in the infrared signal. In this way, a technician can view the information that is stored on the storage device 2108 without the need to remove the RJ-4 plug 5 from a port. This embodiment can be adapted to other types of connectors, including fiber optic connectors.

The PLI information that is captured, maintained, and made available using the techniques described here can be used for many different types of applications. For example, PLI information can be used to manage the amount of slack that is associated with each media segment in the system. When a new patch cord (or other media segment) needs to be installed on the network, the captured physical layer information can be used to determine an accurate and appropriate length for the patch cord based on the PLI and policies of particular slack management used by the company or the carrier. In addition, such PLI can be used to assist with public security applications (for example, to help locate

132 ϊ Μ ΡI

OI MEXICAN INSTITUTE: LA FROI'ILDaD indjstüjal

<img file="MX337306B_D0116.tif" />

Voice telephony devices that are used in an envelope Internet Protocol (VOIP) system.

Examples of how such physical layer information can be used include the following: for example, an NMS (or other user interface associated with aggregation point 120 or any set of connectors 102 such as a patch panel 302 or 302 '), by releasing information about a particular physical media segment, can also be configured to send automatically the user to the website through which the user can request a replacement for that particular media segment. For example, a web browser-based user interface can be configured to display a button (or other element of the user interface) that a user can click to automatically display a website through which a replacement segment can be requested. Similar functionality can be included in user interfaces deployed by aggregation points 120 and connector sets 104 (for example, through web servers running at aggregation points 102 and connector sets 104 ( for example, connection panels

302 or 302 ')).

133

ΜΡΪ __VA A

INDUSTRIAL

<img file="MX337306B_D0117.tif" />

In another example, when retrieving — aTT '”set of particular physical media segments (eg due to security or performance concerns), the physical layer information obtained in the manner described here can be used to determine if and where any of the recovered physical media segments are installed on the network. This information can be used to determine if the segment is replaced and / or if it can be used in the currently replaced segment.

In another example, the physical layer information described here is used for intrusion detection. For example, for particular secure resources on a network (for example, a particular server or service), a security policy can be established specifying that secure resources should only be accessed through specific computers that are attached to the resources Secure using particular ports of particular network interconnection devices or other sets of connectors and particular segments of physical communication media. If someone tries to access secure resources in a way that does not

134

<img file="MX337306B_D0118.tif" />

IMPI

MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY complies with the security policy, -ne-se-Le-Jará., Access to safe resources. For example, if an intruder could falsify the identity of a licensed computer but access a secure resource using an unauthorized logical communication link, the intruder would still be denied access to secure resources unless the intruder was able falsifying the identities of all other elements identified in the policy (for example, the identities of all the physical means of communication that implement the logical communication link between the computer and the secure resource).

In another example, the aggregation point receives and stores information about certain conditions that exist in various locations where the physical means of communication are installed. For example, you can configure the aggregation point to receive and store information that is unique to each location (such as local requirements regarding the use of battery backups, environmental conditions obtained from external sensors, and external systems (such as external temperature sensors, HVAC systems, or computer servers that

135

<img file="MX337306B_D0119.tif" />

MEXICAN INSTITUTE D £ THE PROPERTY

INDUSTRIAL

<img file="MX337306B_D0120.tif" />

provide weather related information)). Routing decisions within the network can be made, at least partially, based on locally unique conditions.

In another example, a technician near a particular patch panel 302 may wish to change a particular patch cord (for example, because a visual inspection of the patch cord identified some potential problem with the patch cord). A request for authorization to disconnect the patch cable from associated port 304 would be routed to an aggregation point or an NMS. The aggregation point or NMS would send messages to one or more relevant network interconnect devices 354 indicating that a patch cord used to implement a particular logical communication link is going to be disconnected in the near future. Network interconnection devices 354, in response to said signal, would route certain classes of traffic (eg, real-time traffic, such as telephony or multimedia traffic) away from that logical communication link. Also, the network interconnect devices 354 can be configured to communicate a go-ahead signal to the aggregation point or the NMS, indicating that everything is

136

<img file="MX337306B_D0121.tif" />

in order, from the perspective of each of said devices, to disconnect the relevant connection cable. When the aggregation point or NMS receives go-ahead signals from all reported network interconnect devices, the aggregation point or NMS informs the technician (using monitor 315) that they can proceed to disconnect that connection cable.

In another example, the information on the physical layer obtained using the techniques described here is used to verify whether h a particular type of physical communication means has been installed. For example, when a company or supplier wants to implement a particular type of physical communication media for a given logical communication link (for example, CAT-6 compliant physical communication media to implement GIGABIT ETHERNET communication links), the information over physical layer that is obtained, as described above, it can be used to confirm that each physical media segment of the logical communication link is implemented using the appropriate type of media. Another example is to confirm if a

137

Τ 1 ·, i Jí Ι'Ό

ΙΗ? Τ! ΤνΤΟ DE La

L '.' S'US i Má y;

·> <, L

<img file="MX337306B_D0122.tif" />

multimode or shielded twisted pair fiber instead of singlemode or unshielded twisted pair cabling, respectively, which may not be readily apparent from a visual inspection of the media when installed.

In another example, the information on the physical layer obtained using the techniques described here is used for theft control. For example, in the case of IP telephony, the IP telephony server can be configured to provide telephony service to each IP phone only if that IP phone is used with particular logical communication links implemented using particular physical layer elements (eg example, segments installed within a given building). If the IP phone is stolen or moved out of an authorized area, the IP phone server will not provide service to the IP phone, even if it is able to access the IP phone server.

here they can be used in even applications for

The techniques described different applications, companies and applications for suppliers.

138

<img file="MX337306B_D0123.tif" />

FIG. 22 and 23 illustrate an example..of a ^^ pl.icaci.ón for providers.

FIG. 22 illustrates a network 2200 that deploys passive fiber optic lines. As shown, network 2200 may include a central office 2201 that connects to a number of end subscribers 2205 (also called end users 2205 presently) on a network. Central Office 2201 may additionally connect to a broader network such as the Internet (not shown) and a public switched telephone network (PSTN). Network 2200 may also include 2203 Fiber Distribution Hubs (FDHs) that have one or more optical splitters (for example, between 1 and 8 splitters, between 1 and 16 splitters, or between 1 and 32 splitters) that generate a number of Individual fibers that can lead to end-user facilities 2205. The various lines on the 2200 network may be overhead or located within underground conduits.

In general, the portion of network 2200 that is closest to central office 2201 is referred to as the region Fl, where F1 is the power fiber of central office 2201. The portion of the network 22 00 more

139

<img file="MX337306B_D0124.tif" />

ΐΝΣΤί to γ ​​··? . • «'iAr.n Dfc lá j

l.^rÜÁJ i close to end users 2205 as a portion F2 of network 2200. Network 2200 includes a plurality of breakout locations 2202 in which branched cables are separated from the main cable lines. Branched cables are typically connected to drop terminals 2204 that include connector interfaces to facilitate coupling of fibers from branched cables to a plurality of different subscriber locations.

2205.

The spacers used in an FDH 2203 can accept an F1 power cable that has a number of fibers and can separate the incoming fibers into, for example, 216 to 432 individual distribution fibers that can be associated with a similar number of user locations. final. In typical applications, a prepackaged optical splitter is provided in an optical splitter module housing and is provided with a splitter outlet in patch cords extending from the module. The patch cords that come out of the splitter are typically connected with, for example, the SC, LC or LX.5 connectors. The optical separator module provides protective packaging for the components of the optical separator in

140

<img file="MX337306B_D0125.tif" />

INSTITUTE

DE LA (>! <RÍO, Ó. * Housing and thus provided for easy handling for otherwise fragile separator components. This modular approach allows optical separator modules to be incrementally added to the FDH 2203 , According to the requirements.

FIG. 23 is a schematic diagram showing an exemplary cable routing scheme for the FDH

2203 .

The FDH 2203 generally manages termination panel connections between incoming fiber and outgoing fiber in an Outside Plant (OSP) environment. As the term is used herein, a connection between fibers includes both direct and the indirect ones. Examples of incoming fibers include the fibers of the power cable entering the cabinet and the intermediate fibers (for example, the connected patch cords that extend from the dividers and connection fibers / jumpers) that connect the fiber of the power cable to the termination panel. Examples of outgoing fibers include the fibers of the subscriber cable coming out of the cabinet and any of the intermediate fibers connecting the fibers of the subscriber cable to the termination panel. FDH 2203

141 z &lt;

-'TO

Τ '

j.vi

LRóTí'í .Λό L'E LA ¡provides an interconnection interface for optical transmission signals at a location on the network where operational access and reconfiguration are desired. For example, as noted above, the FDH 2203 can be used to separate the power cables and terminate the separation of the power cables on the distribution cables routed to the subscriber locations. Additionally, the FDH 2203 is designed to accommodate a range of alternate sizes and fiber counts and to support factory installation of patch cords, output capacities, and standoffs.

As shown in FIG. 23, a 2320 power cable is initially routed to the FDH

2203 through a 2302 cabinet. In some embodiments, the fibers of the power cord

2320 they may include ribbon fibers. An exemplary 2320 power cord may include between twelve and forty-eight individual fibers connected to a central service provider office 2201. In some embodiments, after entering the cabinet

2302, the fibers of power cable 2320 are routed to a power cable interface

142

<img file="MX337306B_D0126.tif" />

2338 (for example, fiber-adapter-.optXGa ^. ^ modules to splice tray, etc.). At the power cord interface 2338, one or more of the power cord fibers 2320 are individually connected to the input fibers of the separate splitter 2324. The input fibers of the splitter 2324 are routed from the power cord interface 2338. to the separator module housing 2308. In the separator module housing 2308, the input fibers of the separator 2324 are connected to the separated separator modules 2316, where the fibers

<td></td><td>input</td><td> 2324</td><td>each separate</td><td>in</td><td>multiple</td>

<td></td><td>hoses</td><td> 2326,</td><td>each one of those</td><td>has</td><td>extremes</td>

<td></td><td>connected</td><td> 2328 .</td><td>In other embodiments,</td><td>without</td><td>embargo,</td>

<td> 15</td><td>the fibers</td><td>of the</td><td>power cord</td><td colspan="2">2320 can</td>

connect and route directly to 2316 splitter modules thereby bypassing or eliminating the need for an intermediate power cable interface

2338 .

When patch cords 2326 are not in operation, connected ends 2328 can be temporarily stored in a storage module 2318 that is mounted in storage region 23 06 of cabinet 2302. When patch cords 2326 are

143

<img file="MX337306B_D0127.tif" />

MEXICAN INSTITUTE OF PROPERTY

INDUSTRIAL

<img file="MX337306B_D0128.tif" />

Required for operation, patch cords 2326 are routed from spacer modules 2316 to a termination module 2310 that is provided in termination region 2304 of cabinet 2302. In termination module 2310, patch cords 2326 are connected to the fibers of a 2330 distribution cable. The termination panel is the dividing line between the incoming fibers and the outgoing fibers. A typical 2330 distribution cable forms the F2 portion of a network (see FIG. 22) and typically includes a plurality of fibers (eg, 144, 216, or 432 fibers) that are routed from FDH 2203 to subscriber locations. 2205. Cables 2330 with connected ends 2332 connect to connected ends 2328 of patch cords 2326 on fiber optic adapters 2312.

In some embodiments, one or more of the power cord fibers 2320 are not connected to any of the spacer modules 2316. Instead, these power cord fibers 2320 are connected to the transfer fibers 2334 having connected ends. 2336. Transfer fibers 2334 are connected to termination modules 2310, without first connecting the modules.

144

PI sf 1

Mexican INSTITUTE Oe LA I'HOheda ;, industrial

<img file="MX337306B_D0129.tif" />

spacers 2316. By refraining from signaling a 2334 fiber, a stronger signal can be sent to one of the subscribers. The connected ends 2336 of the transfer fibers 2334 can be stored in the storage region 2306 when not in use.

Cables 2330 with connected ends 2332 connect to connected ends 2336 of transfer fibers 2334 at the level of fiber optic adapters 2312. Feeder interface device 2338 includes connections 2322 for connecting the various cables, as with junctions or connected ends and adapters such as connected ends 2328 and 2336, and the adapters 2312 noted above.

The various physical media segments used in network 2200 of FIGS. 22 and 23 may have an identifier and attribute information stored in or on them. For example, the various connected fibers described above in connection with FIGS. 22 and 23 can be equipped with storage devices and the corresponding termination modules (and other connection points) can include the corresponding media reading interfaces to read at least a portion.

145

<td colspan="4"></td><td>go ii re Ί ' 11. J 1</td><td></td>

<td colspan="2">the identifier and</td><td>the</td><td colspan="3">iÑuTli 'j. attribute information</td>

<td>stored in</td><td>every</td><td>one</td><td>of the</td><td>devices</td><td>of</td>

<td>storage.</td><td colspan="3">The identifier and</td><td>information</td><td>of</td>

<td>attributes that</td><td>I know</td><td>read</td><td>of the</td><td>devices</td><td>of</td>

<td>storage</td><td>can</td><td colspan="2">communicate</td><td>to a point</td><td>of</td>

aggregation for use as described here (using a suitable communication link such as a wired or wireless communication link). Other information about the physical layer (for example, information about termination modules, dividers, cabinets, and other devices on the network and information about the locations where they are installed) can also be provided at that aggregation point for use in that way.

In another example, the physical layer information obtained using the techniques described here is used by a telecommunications operator to assist in complying with service level agreements. For example, as noted above, the physical layer information can be used to determine whether a given logical communication link has been implemented using appropriate physical communication means (for example, CAT-6 cabling on ETHERNET in First Mile applications ( EFM) or

146 faith W ΐί 'Ο Τ A 1V1 s- H

<img file="MX337306B_D0130.tif" />

A Mexican iHsmuTc DE LA PRONEC-AD industrial _ suitable fiber type). This is especially important at the demarcation point between the telecom operator's equipment and the client's equipment. Also, the physical layer information can be used to determine if unauthorized changes have been made at the demarcation point.

In another example, the information on the physical layer obtained using the techniques described here is used by a telecommunications operator to implement differentiated service levels. For example, when certain customers require their communications traffic to travel through certain geographic regions (for example, to comply with export control laws), an operator may use physical layer information obtained using the techniques described here to route customer traffic to meet customer demands. In another example, to each routing point, site, building, etc. it is assigned a security score and certain communication traffic is routed only through routing points, sites, buildings, etc. who have a safety score at or above a certain level.

147

<img file="MX337306B_D0131.tif" />

<img file="MX337306B_D0132.tif" />

.L »A number of embodiments of the invention defined by the following claims have been described. However, it will be understood that the various modifications of the described embodiments can be made without departing from the spirit and scope of the claimed invention. Accordingly, other embodiments are within the scope of the following claims.

148