WO2002080311A1

WO2002080311A1 - Intelligent network jack having location identifier

Info

Publication number: WO2002080311A1
Application number: PCT/US2002/010192
Authority: WO
Inventors: E. Stanley Otto
Original assignee: Otto E Stanley
Priority date: 2001-03-30
Filing date: 2002-03-29
Publication date: 2002-10-10

Abstract

A method and apparatus are provided for enabling the determination of the location of a device connected to a network, such as a local area network or a wide area network. The network interface, such as an RJ45 jack, is provided with intelligence to enable the network interface to respons to a query for an identifier. The network interface identifier can be correlated with location information previously generated or gathered by, for example, a central server. A network device, such as a personal computer, may query the network interface and ask for the network device, such as a personal computer, may query the network interface and ask for the network interface identifier. The network interface responds with the identifier. The network device can then forward the device's MAC address, along with the network interface identifier, to inform the central server that that particular network device is logged into the network at the location corresponding to the network interface identifier. Correlating known assets with their locations aids greatly in the management and accounting of those assets.

Description

INTELLIGENT NETWORK JACK HAVING LOCATION IDENTIFIER

The present application is related to computer networks. More specifically, the present application is related to the management of assets connected to the computer network by correlating location information with the devices that are connected to the computer network.

The explosion of networked computer systems in corporations has required a vast investment in computer equipment and personnel. Computer equipment, like other corporate assets, needs to be managed. However, maintaining, replacing, and tracking these networked assets can be a very expensive proposition. In the past, computer equipment was bulky, expensive, and required strictly controlled environments and specially trained personnel in order to operate. Because of operational constraints, computer equipment was usually confined to a central "data center" that could be secured easily and, thus, easily managed.

In contrast to earlier computer operational constraints, current computer equipment can work in common offices or, in some cases, in the field. Consequently, today's computing environment is widely distributed throughout the organization and consists of devices that need only a network connection and any standard power supply. The combination of easy network access, light-weight, relaxed environmental constraints, low cost and relative ubiquity makes network assets extremely mobile and creates new challenges for companies trying to manage them. To meet the challenge, companies often turn to sophisticated asset management systems. However, while these asset management systems can provide much of the needed functionality, they lack the ability to physically locate the devices within the company's facilities.

A further complication to the asset management challenge is leasing. Leases are a common way of financing computer equipment and offer many advantages over other forms of financing. Leasing, however, places an additional burden on companies because the ownership of the equipment rests with the lessor and not the company; the leased equipment has to be returned to the lessor at lease end or the company may incur monetary "penalties" (additional rents and/or lease buyout.) Many companies spend hundreds of thousands of dollars for these "penalties" because they are unable to locate the equipment in a timely manner for return to the lessor.

Property taxes are another reason for companies to keep accurate records of the physical location of these assets. Most states and counties have some form of personal property taxes, a tax levied on the value of assets used in a business in the taxing authority's jurisdiction. This tax is usually based on where the assets are located at a particular date. Each company is responsible for filing a "rendition" of the assets and their value for each taxing authority on an annual basis. The rendition is subject to audit and discrepancies are subject to fines and penalties. Filing an accurate rendition is difficult if accurate records of the physical location are not kept. In addition, different jurisdictions have varying tax rates. Erroneously rendering equipment in a jurisdiction with a higher rate can significantly increase a company's overall tax liability.

In response to these problems and as a more general requirement, companies must routinely track and inventory hard assets such as computer equipment. Traditional solutions include periodic physical inventories, going room-to-room and physically verifying each computer device within a site, and perpetual inventories, recording the movement of computer devices at or near the time they are moved. Even with bar coding and other automation tools this can be an expensive on-going process. In addition, current asset management systems place a high degree of reliance on manual processes and company-wide cooperation to maintain physical location information. Even the available automation tools have some level of manual intervention involved. Because of this, accuracy under these methods is suspect; errors occur when entering data into the system, moves are performed outside the proscribed processes, asset related databases are not maintained, asset tags are removed, etc.

The present invention is a response to the need for accurate, automated physical location information.

The present invention remedies the shortcomings of the prior art by providing an apparatus, system, and method for determining the location of network devices, such as personal computers, on a network. The present invention is a network connector having a network interface with a client connector (to which network devices are connected) and a network connector (which is coupled to the network itself). The network interface is designed to facilitate the coupling of a network device to a network. In the preferred embodiment of the present invention, the network and client connectors are RJ45 connectors. A chip, such as a microcontroller, is coupled to the network interface to create an intelligent jack. The chip is designed and fitted onto the intelligent jack in order to receive a query signal from the network interface and to return an identifier to the network interface, thereby allowing the network device to receive the identifier from the network interface. Thus, when the network device queries the network interface, the chip returns the identifier to the network device though the intelligent jack.

The network device may be a personal computer or any other device that can connect to the network. Normally, the network interface is an RJ45 connector, although other types of connectors can be used. The chip that is coupled to the network interface is typically a microcontroller or similar integrated circuit that can receive a query signal and return the identifier. The identifier can be a serial number or some other type of identifier that can be distinguished from other identifiers on the network. The present invention can work with various network protocols, such as Ethernet, IPX, AppleTalk, USB, Firewire, among others. The network device can be equipped with a client network management process which is designed to query the network interface and to receive the identifier as response from the chip via the intelligent jack.

The network can also be equipped with a server. The server itself may have an asset manager process that can be used to query the network interface and thereby receive the identifier (in the form of a signal) from the chip. Alternatively, the asset manager can query the network device and receive one or more identifiers from either the interface connector and/or the network device, typically after the network device itself has queried the network interface.

A method is provided for determining the location of a network device. The method includes the steps of connecting to a network at a network interface with a network device, querying the network interface with the network device; receiving an identifier from the network interface, and sending the identifier to an asset manager on the network. The step of querying the network interface can include the launching of a client asset management process on the network device. The client asset management process can be launched by the operating system of the network device upon, for example, system startup. The client asset management process can also be invoked by the asset manager of the network. In either case, the client asset management process is designed to query the network interface in order to prompt the chip of the network interface to return the identifier.

A more complete understanding of the present disclosure and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings wherein:

Figure 1 is a block diagram illustrating the exemplary embodiment of the present invention.

Figure 2 is a flowchart illustrating the method of the present invention. The present invention may be susceptible to various modifications and alternative forms. Specific embodiments of the present invention are shown by way of example in the drawings and are described herein in detail. It should be understood, however, that the description set forth herein of specific embodiments is not intended to limit the present invention to the particular forms disclosed. Rather, all modifications, alternatives, and equivalents falling within the spirit and scope of the invention as defined by the appended claims are intended to be covered.

The present invention is a system and method for determining the location of network devices that are connected to a network, such as a local area network ("LAN") or a wide area network ("WAN"). The present invention provides intelligence to a network interface to which one or more network devices connect to the network. The present invention is provided with the capability of receiving a query signal and replying with a identifier that distinguishes the intelligent jack of the present invention from other devices on the relevant network. The identifier response from the intelligent jack of the present invention may be interpreted by other devices on the network for various purposes, such as inventory control or location. The present invention can, therefor, be used to physically locate individual machines that are connected to the network.

The preferred embodiment of the present invention is illustrated in Figure 1. The intelligent jack apparatus 10 of the present invention is preferably positioned between the client device 8 and the network 14. Generally, the intelligent jack apparatus 10 is positioned at a physical location where a personal computer ("PC") 12, or other networked device, is plugged into a network 14. In this embodiment, the apparatus of the present invention is embedded into a wall jack 16, as illustrated in Figure 1. In a typical installation, PC 12 is connected to the network 14 using female RJ45 connectors 18, 19 though cable 20. Typically, a category 5 ("CAT5") wire, that is used in conjunction with an RJ45 connector, has eight separate wires which are individually routed into the female connectors 18, 19 as shown in Figure 1. In such an installation, the pin configuration of the RJ45 connector typically utilizes pins 1 , 2, 5, and 6 to transmit and receive information over, for example, an Ethernet operating on the network 14. Left unutilized are pins 3, 4, 7, and 8 and their respective wires of cable 20. The unutilized wires are available for transmission of other data.

In the preferred embodiment of the present invention, chip 22, which may be a microcontroller or other integrated circuit, is connected across any pair of available wires 3, 4, 7, and/or 8 of the network CAT5 cable 33 that are physically secured to the wall jack 16 via connecting wires 21 and 23. Chip 16 may be any circuit that is capable of providing unique indicia, such as a serial number, or a guaranteed unique identifier ("GUID"), or other indicia. For example, a PIC microcontroller, that is manufactured by Microchip Technology Inc. of Chandler, Arizona, can be used for the chip 22. Other devices, preferably that are integrated circuits, can be used with the present invention, so long as they are able to receive a query signal and return an identifier having a uniqueness that is suitable for the application, meaning that the returned value need only be unique to other devices on the network in question. In the preferred embodiment of the present invention, the query and response signals are all accomplished with standard wire connections, as illustrated in Figure 1. The preferred embodiment of the present invention further includes network interface driver 24 that is loaded next in the startup sequence of the PC 12. The network interface driver 24 is used for sending and receiving signals between the operating system 26 and the network interface card 17 that is connected to the network connector 18. While some network drivers are only capable of communicating with the operating system 26, other drivers are able to communicate with other processes. For example, depending upon the desired level of integration, or the ease of installation desired, a separate client asset management process 30 may also be loaded into memory by the operating system 26. It will be clear to those skilled in the art that the client asset management process 30 may be a standalone process (as illustrated in Figure 1), or it may be embedded within the network interface driver 24, or even within the operating system 26 itself.

In operation, the client asset management process 30 solicits the serial number or unique identifier of chip 22 using available wires of cable 20. The client asset management process 30 performs the solicitation in one of two general ways. The first way is to have the client asset management process 30 request the operating system 26 to signal the network interface driver 24 to have the network interface card 17 issue the signal over cable 20, with the response traveling the same path in reverse. The second method is similar to the first one, except that the client asset management process 30 issues the request for the query directly to the network interface driver 24, thereby routing around the operating system 26, as illustrated in Figure 1. Upon receiving the response from the chip 22, the client asset management process 30 stores and/or transmits the identifier to the network asset manager software 28 that runs on, for example, server 42. The asset management process 28 may then correlate the identifier, that was transmitted by the PC 12, to a physical location. The asset manager process 28 may then update the status of the location of the PC 12. In alternate embodiments of the present invention, the location information may be stored on a flat file (not shown), or in a database 32 on, for example, the server 42.

The server 42 is normally equipped with a network connection, including female RJ45 connector 34 that is connected to the network cable 33 (which itself is connected to the RJ45 connector 19), a network interface card 36 and associated network interface card driver 38 that is operative with the server's own operating system 40. The asset manager process 28 is also operative with the server operating system 40 and/or with the network interface card driver 38 as illustrated in Figure 1.

The identifier that is received from the intelligent jack 16 of the present invention may also be combined with, for example, a MAC address of the NIC 17 of the PC 12, and sent as a signal to the asset manager 28. The asset manager process 28 then correlates the location information stored, for example in the database 32, with the MAC address and the identifier that was received from the PC 12, and performs a correlation of the location information with the identifier in order to determine the location of the PC 12. The client asset management process 30 may be initiated during the startup sequence of the network device, such as PC 12, and perform the query/response/report sequence outlined above as soon as, for example, the central server has assigned an IP address to the PC or the PC 12 is otherwise logged into the network. Alternatively, the asset manager 28 may initiate a request to each network device, such as PC 12, to prompt the network device to query the intelligent jack 16 of the present invention and, at that time, report back identifying information.

An embodiment of the method 200 of the present invention is illustrated in Figure 2. The method begins, generally, at step 202. Thereafter, in step 204, the network device launches the sign-on routine to log into the network. Next, in step 206, the network device logs into the network.. In step 208, the network device's operating system, or network driver, or client asset management process, queries the intelligent jack of the present invention for the identifier. Next, in step 210, the identifier is embedded in a message. The message may optionally include specific information about the network device that generates the message, such as an IP address and/or network interface card identifier. In step 212, the message is forwarded to the network's asset manager. Finally, in step 214, the network's asset manager correlates the identifier with the location of the intelligent jack and, optionally, stores that information for later use. The method ends generally at step 216.

In the above example, the computer asset that is being track is a personal computer (PC) 12 that is running, for example, the Windows NT operating system, manufactured by the Microsoft Corporation of Redmond, Washington, although other operating systems, such as OSX by the Apple Computer of Cupertino, California, or open source software such as Linux, may also be used to equal effect. In other embodiments, any computer device that supports firmware or software and a network connection, such as UNIX computers, printers, Windows '95, Windows '98, etc., can use the intelligent jack 16 of the present invention. Moreover, any network protocol (in lieu of Ethernet) can be used, such as IPX, AppleTalk, USB, Firewire, i²C, CAN bus, etc.

The invention, therefore, is well adapted to carry out the objects and to attain the ends and advantages mentioned, as well as others inherent therein. While the invention has been depicted, described, and is defined by reference to exemplary embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alternation, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts and having the benefit of this disclosure. The depicted and described embodiments of the invention are exemplary only, and are not exhaustive of the scope of the invention. Consequently, the invention is intended to be limited only by the spirit and scope of the appended claims, giving full cognizance to equivalents in all respects.

Claims

1. A network connector comprising: a network interface having a connector that is constructed and arranged to facilitate coupling of a network device to a network; and a chip coupled to said network interface, said chip constructed and arranged to receive a query signal from said network interface and to return an identifier to said network interface; wherein, when said network device queries said network interface, said chip returns said identifier to said network device.

2. The network connector of claim 1, wherein said network device is a personal computer.

3. The network connector of claim 1, wherein said network interface is an RJ45 connector.

4. The network connector of claim 1, wherein said chip is a microcontroller.

5. The network connector of claim 1, wherein the identifier is a serial number.

6. The network connector of claim 1, wherein said identifier is a unique identifier.

7. The network connector of claim 1, further comprising a server.

8. The network connector of claim 1, wherein said network device has a client network management process, said client network management process constructed and arranged to query said network interface and to receive said response from said chip.

9. The network connector of claim 7, wherein said server has an asset manager, said asset manager being constructed and arranged to query said network device and to receive one or more identifiers from said network device after said network device has queried said network interface.

10. A method for determining the location of a network device comprising: connecting to a network at a network interface with a network device; querying said network interface with said network device; receiving an identifier from said network interface; and sending said identifier to an asset manager on said network.

11. The method of claim 11 , wherein said step of querying said network interface includes launching a client asset management process.

12. A method for determining the location of a network device comprising: launching a network sign-on routine with a network device; logging onto said network; querying an intelligent jack for an identifier; placing said identifier into a message; sending said message to a server; and correlating said identifier with a location.

13. The method of claim 12 further comprising : storing said identifier and said location.