BACKGROUND
The present invention relates to security asset management systems, and, more specifically, to securing assets that already include identification circuitry.
A security asset management system (SAM) can use circuitry to monitor, secure, and/or manage assets, such as keys, computers, weapons, and/or any other object. In some implementations, a SAM can control access to rooms, vehicles, and/or other places and/or objects, directly and/or indirectly. By providing proper credentials, a user can be authenticated and can be granted access to one or more assets. Credentials can be provided directly or indirectly, such as via a keypad on a SAM device, by phoning credentials into a SAM control center, and/or a variety of other ways. Access to assets can thus be managed among and/or restricted to those with proper authorization from an owner and/or user.
In some SAM systems, identification circuitry is included in a fob, can, button, or other device attached to, mounted on, or mounted in an asset to be tracked. In addition, some such systems can positively retain the device in which the identification circuitry is included, such as by using a solenoid to prevent withdrawal of the device from a storage position. Some assets, however, can already include identification circuitry and so would not require an additional device in which identification circuitry would ordinarily be included. Such assets therefore do not have a way to be positively retained in some security asset management systems.
SUMMARY
According to one embodiment of the present invention, a system for asset management can include at least one tracking communication port selectively coupled to an asset communication port. A database can be included and can be configurable to store one or more asset records. The system can also include a user interface and a controller coupled to the at least one tracking communication port, the database, and the user interface. The controller can identify a user via the user interface, sense when an asset, having the asset communication port, couples to the at least one tracking communication port via its asset communication port, query the asset for at least one unique asset identifier, and store a record corresponding to the at least one unique asset identifier.
Another embodiment of the invention disclosed herein can include an asset tracking device having at least one tracking communication port configured to be removably coupled to an asset communication port. Translation circuitry coupled to the at least one tracking communication port can including a sensor that selectively senses when an asset, having the asset communication port, couples to the at least one tracking communication port via its asset communication port. The translation circuitry can query the asset when present for at least one unique asset identifier and present the at least one unique asset identifier to a controller.
An additional embodiment of the invention disclosed herein can take the form of a security asset manager including a communication bus and at least one tracking communication port configured to be removably coupled to an asset communication port. Translation circuitry coupled to the at least one tracking communication port and the communication bus can sense when an asset, having the asset communication port, couples to the at least one tracking communication port via its asset communication port, query the asset for at least one unique asset identifier, present the at least one unique asset identifier to the communication bus, and a controller coupled to the communication bus, wherein the controller is configured to determine when the asset is coupled to the at least one tracking communication port by receiving the asset's at least one unique asset identifier from the communication bus.
Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. For a better understanding of the invention with the advantages and the features, refer to the description and to the drawings.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:
FIG. 1 is a schematic block diagram illustrating a security asset manager according to embodiments of the invention disclosed herein.
FIG. 2 is a schematic block diagram illustrating a security asset management system according to embodiments of the invention disclosed herein.
FIG. 3 is a schematic diagram of a security asset manager including a receptacle according to embodiments of the invention disclosed herein.
FIG. 4 is a schematic diagram illustrating a car fob that can be used with and according to embodiments of the invention disclosed herein.
FIG. 5 is a schematic illustration of a locking device that can be used with and according to embodiments of the invention disclosed herein.
FIG. 6 is a schematic illustration of an asset tracking receptacle according to embodiments of the invention disclosed herein.
FIG. 7 is a schematic illustration of a security asset manager including communication with a car fob according to embodiments of the invention disclosed herein.
FIGS. 8-11 are schematic flow diagrams illustrating aspects of a method of managing an asset according to embodiments of the invention disclosed herein.
FIG. 12 is a schematic illustration of an alternative configuration of a security asset manager according to embodiments of the invention disclosed herein.
FIGS. 13-15 are schematic illustrations of a fob arrangement according to embodiments of the invention disclosed herein.
FIGS. 16-18 are schematic illustrations of the security asset manager of FIG. 12 used with fob arrangements like those of FIGS. 13-15 according to embodiments of the invention disclosed herein.
DETAILED DESCRIPTION
With reference now to FIG. 1, a secure asset management system 100 can include a controller 110 that can monitor asset storage 120 in which assets 122 can be stored. In embodiments, the presence of one or more assets 122 can be monitored and/or detected by controller 110, and controller 110 can use a database 130 to determine whether access should be granted to an asset 122 in asset storage 120. Controller 110 can include, but is not limited to, a computer, a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), digital circuitry, analog circuitry, or any combination and/or plurality thereof, or any suitable computing device, whether local or distributed. Database 130, as well as software and/or computer program products that can be used to run secure asset management system 100, can be stored on at least one non-transitory computer readable storage medium 112, which can be part of controller 110, can be a standalone device, and/or can be part of another device with which controller 110 can communicate. In embodiments, controller 110 can include or be in communication with non-transitory computer readable storage medium 112 having computer-readable instructions stored thereon in the form of executable code that when executed by controller 110 causes or enables controller 110 to perform the various actions or functions described herein, as well as other actions or functions as can be suitable and/or desired. A user interface 140 can be used to interact with secure asset management system 100 so that administrators can set up, monitor, and/or manage assets 122 with system 100, and so that users can request and/or gain access to assets 122. For example, user interface 140 can include one or more displays, input devices, audio input/output devices, indicator lights, and/or any other device that allows a user to interact with system 100.
FIG. 2 illustrates an embodiment of a security asset management system 200 that includes at least one security asset manager (SAM) 202. Each SAM 202 can have a user interface as described above, comprising one or more of a variety of user identification (ID) devices, such as a keypad for personal identification number (PIN) entry, a fingerprint reader, and a proximity card reader. Those skilled in the art will understand that other types of user ID devices can be used, such as, but not limited to an iris ID device, a retinal scanning ID device, a hand shape ID device, and a magnetic card reader. Each SAM 202 can also control one or more locked doors and/or lockers (not shown) which can be unlocked by SAM 202 following user identification. Behind the one or more doors, authorized users can reach one or more assets 206. Each asset 206 can be associated with a unique electronic identifier that can be associated with its corresponding asset 206. One suitable non-limiting example of identification circuitry is a touch memory device, such as the DS2401P+ touch memory device from Maxim Integrated. Another non-limiting example of identification circuitry is a radio frequency identification (RFID) tag. Each SAM 202 can further include a controller as described above and that can be removably coupled to or placed in communication with identification circuitry of each asset 206 using a suitable electronic communication scheme, such as, but not limited the One Wire Communication Bus designed by Dallas Semiconductor Corp. The controller can thus detect when identification circuitry of an asset 206 has been connected to or removed from the bus. Since only known authorized users are given access to SAM 202, the respective controller can monitor what assets are present, who has taken removed assets, and who has returned them.
Where security asset management system 200 includes a plurality of SAMs 202, a network 201 can be used to couple SAMs 202 to and/or place SAMs 202 in communication with each other via a network 201. One or more networked controllers 203 can also be coupled to one or more of SAMs 202 via network 201. Network 201 can be, but is not limited to, a local area network (LAN), a wide area network (WAN), a wireless LAN, a wireless WAN, or any combination and/or plurality thereof. In some embodiments, one of networked controllers 203 can be a server running asset management software for coordinating and collecting data from one or more SAMs 202, as well as providing reports on authorized user activity, asset status, and alarms. One suitable example of asset management software is the Global Facilities Management System software available from Key Systems, Inc. In other embodiments, another of networked controllers 201 can include, but is not limited to, a computer, a laptop, a smartphone, and/or a cellular phone which is able to interact via a browser or other web enabled client with either a remote server running asset management software or an embedded web server in one of SAMs 202. In a networked system, such as illustrated in FIG. 2, an asset 206 can be removed from and returned to one of the SAMs 202, and the controllers in each SAM can communicate the asset status to other controllers either directly or via coordinating asset management software.
Some assets include identification circuitry or a communication port used as part of their normal operation. For example, car fobs that include remote control of the cars to which they belong can broadcast an identification code using one or more radio frequencies along with a command, such as to unlock the driver side door. The car can recognize the identification code and execute the command. This type of identification is a form of RFID, and it would be advantageous to use this existing RFID in monitoring and securing such car fobs in a SAM rather than add additional identification circuitry. To take advantage of pre-existing identifiers or the like, embodiments of a SAM 302 shown in FIG. 2 can include hardware and/or software to facilitate communication with and use of the circuitry or communication port of an asset. Several examples of suitable arrangements to achieve these ends can be seen in U.S. Provisional Patent Application Nos. 61/837,942, “System and Method for Communication Port Based Asset Management,” filed 21 Jun. 2013, and 61/990,707, “Security Asset Management System, Method, and Receptacle Therefor,” filed 8 May 2014, both owned in common herewith, the entire disclosures of which are incorporated by reference.
For example, as seen schematically in FIG. 2, SAM 302 can include, much as the SAM 100 in FIG. 1, a controller 310, which can include a computer-readable storage medium 312, asset storage 320, a database 330, and a user interface 340. In addition, SAM 302 can include a communication bus 350, such as the Dallas One-Wire Bus, with which controller 310 can be coupled to bus-compatible identification circuitry 208 of an asset 206. In addition, for any asset 306 including a communication port 308 or identification circuitry that is not bus-compatible, SAM 302 can include a tracking communication port 360 that can communicate with asset communication port 308, as well as translation circuitry 362 that converts signals from asset 306 into bus-compatible signals. For example, if bus 350 were a One-Wire bus and asset communication port 308 included an RFID tag, tracking communication port 360 could include an RFID sensor, and translation circuitry 362 could translate between the memory space of bus 350 and signals used by the RFID sensor and/or tag.
FIG. 3 shows an example of a fob 400 in which one or more buttons 402 can be in communication with control circuitry 404, a power source 406, and a transmitter 408. Each button 402 can cause control circuitry 404 to send an associated command and some form of identifier to a car 407 via transmitter 408 having antenna 409. An identifier can be, for example, an identification code 410 stored in control circuitry 404 or identification circuitry 412, and identification circuitry 412 can be part of control circuitry 404 or separate therefrom. As part of transmitting a command to car 407, control circuitry 404 can retrieve identification code 410 from identification circuitry 412 and transmit the identification code 410 to the car. Fob 400 in embodiments can act as a key, while in other embodiments, fob 400 can hold a key within its body, and in still other embodiments, fob 400 can be attached to one or more keys 414 via passage 416 and ring or the like 418. FIG. 4 shows the schematically illustrated SAM 302 of FIG. 2, in which assets 206 can be stored and including a receptacle, such as a bin 550, in which fob 400 or another asset can be stored. FIG. 4 also shows an example of a tag that can be used with fob 400, here taking the form of a latchable plug 420.
Turning now to FIG. 5, latchable plug 420 can include a phono plug or the like that can include a housing 421 that can be used to house a touch memory chip compatible with the One Wire bus from Dallas Semiconductor. Those of ordinary skill in the art are familiar with the features and operation of the One-Wire bus. In this embodiment, a groove 422 can be machined or otherwise formed in a portion of the phono plug which does not interfere with the conductors in the plug. One suitable location for such a groove 422 is near a tip 424 of the phono plug. In embodiments, first and second insulative bands 425, 427 can separate first and second contact surfaces 426, 428 of plug 420, substantially electrically isolating first contact surface 426 from second contact surface 428. Chip 424 can be in electrical communication with first and second contact surfaces 426, 428 using respective first and second conductors 427, 429 included in plug 420. A corresponding receptacle 430 can receive plug 420 and can include first and second contacts 432, 434 positioned to engage first and second contact surfaces 426, 428 of plug 420 when plug 420 is substantially fully inserted therein. In addition, a solenoid 436 can be mounted adjacent or on receptacle 430 with its pin 437 positioned to extend into groove 422 when plug 420 is substantially fully inserted therein, thereby retaining plug 420 within receptacle 430. Thus, when plug 420 is substantially fully inserted into receptacle 430, chip 424 can be accessed via first and second contacts 432, 434, first and second contact surfaces 426, 428, and first and second conductors 427, 429 by, for example, a SAM controller (not shown) in electrical communication with first and second contacts 432, 434 to retrieve data from chip 424, such as a unique identifier.
A variant of latchable plug 420 is shown in FIG. 6. In this embodiment, each contact surface 426, 428 can include a respective contact groove 426′, 428′ to enhance electrical communication between first and second contacts 432, 434 of receptacle 430 and first and second contact surfaces 426, 428. Each contact groove 426′, 428′ can be formed in its respective contact surfaces 426, 428 by, for example, machining, though in embodiments plug 420 can be cast or otherwise formed to include grooves 426′, 428′. In addition, each contact groove 426′, 428′ can be positioned to receive a respective contact 432, 434 of receptacle 430 when plug 420 is substantially fully inserted therein.
Embodiments of the invention disclosed herein can provide a system, method, and apparatus for recognizing and using identification codes borne by pre-existing identification circuitry in a security asset management system. In addition, embodiments provide a bin into which an asset must be inserted when stored in the SAM in order for the door to close. Such a bin can be sized to hold an asset, such as a car fob, and can extend from a panel of the SAM substantially to the plane where the inner surface of the SAM door rests when the door is closed. The asset can be connected to a tag or the like, such as a plug or a key or other device compatible with SAM positions, so that when the tag is inserted into a position in the SAM, the asset must be in the bin for the door of the SAM to close. The bin can be sized so that as long as the tag, such as a plug, is inserted in the panel, the asset can not be removed. For example, where the tag is a plug and the asset is a car fob, the fob must be in the bin when the plug is inserted in the panel for the door to close, and the fob can not be removed from the bin until the plug is removed from the panel. The SAM can include one or more RFID sensors that can receive and decode signals from the car fob. In some embodiments, each bin can include a respective RFID sensor, while in other embodiments, fewer RFID sensors can be used. The tag can be positively retained until a user is authorized to remove the asset. Upon authorization, the tag can be released, can be identified by a light source, such as an LED, and the user can remove the tag and asset. When the user returns the fob, any empty bin can be offered by the SAM to hold the fob. Upon authorization, the SAM can identify an empty bin for the user with a light source, such as an LED. The user can then place the fob in the bin, insert the tag in the position over the bin, and close the SAM door. In some embodiments, the user can press one of the fob buttons so that the SAM can record the associated identification code, while in other embodiments the SAM can read the code without action by the user.
FIGS. 7-13 show an example of the receptacle as bin 550 in more detail. It should kept in mind that not all of FIGS. 7-13 show all parts discussed below, and the reader is encouraged to refer to another of FIGS. 7-13 if a part or reference numeral is not shown in a FIG. the reader is currently viewing. In an embodiment, bin 550 can include a front wall 552, a bottom wall 554, and two side walls 556 defining a cavity 551 sized to receive fob 400. In the example embodiment shown in FIGS. 7-13, front wall 552 can be sized so that a top edge 557 of each of side walls 556 can extend downward at an angle from panel 510 to front wall 552. In addition, front and side walls 552, 556 can be dimensioned so that fob 400 can not be removed from bin 550 when a tag, such as latchable plug 420, is inserted into its corresponding receptacle 430 in panel 510. Bin 550 can be attached to SAM 302 (FIGS. 1 and 3), such as to a panel 510, so that an open top of bin 550 can be accessed by a user for insertion and removal of fob 400.
In the example of FIGS. 7-13, tracking communications port 360 can be included on, in, or behind panel 510 and oriented such that it can communicate with asset communication port 308 of fob 400. Thus, tracking communications port 360 can be oriented and located to receive signals from and/or send signals to fob 400 when fob 400 is in bin 550. While shown on, in, or near panel 510, it should be clear that tracking communication port 360 can be in any wall or other location so long as it can suitably communicate with an asset communication port (308 in FIG. 2) when an asset (306 in FIG. 2) is present therein, such as a fob (FIGS. 3-4). In embodiments in which RFID or another wireless communication protocol is used with tracking communications port 360 and asset communication port 308, identification circuitry, such as chip 424, can be omitted from plug 420. Where chip 424 is omitted, plug 420 can be used as a presence detector or only to selectively lock fob 400 in place.
FIG. 14 schematically illustrates an embodiment of a system for asset management having universal serial bus (USB) and radio frequency identification (RFID) tracking communication ports. As shown in FIG. 14, the embodied system for asset management 600 can include a secure asset manager (SAM) 302 as in the embodiment schematically illustrated in FIG. 2. SAM 302 can have a controller 310 with a user interface 340 and a database 330 both coupled to controller 310 as discussed in embodiments above. The SAM 302 can also include a communication bus 350, such as, but not limited to a Dallas Semiconductor 1-Wire Bus as also discussed above. The system 600 can further include an asset tracking device 610, which, in this embodiment, can have two tracking communication ports: a USB tracking communication port 620 and an RFID compatible tracking communication port 630. Additional details of USB tracking communication port 620 can be found in the application incorporated by reference above. RFID compatible tracking communication port 630 can include an RFID front end 632, for example, but not limited to the Multi-Standard Fully Integrated RFID Analog Front End model TRF7960 from Texas Instruments. The RFID compatible tracking communication port 630 can also have an RFID clock 634 coupled to RFID front end 632 to provide a clock at the desired RFID communication frequency. Those skilled in the art are easily familiar with many clock circuits which can provide a desired RFID clock frequency. A transmit connection 636 and a receive connection 638 of the RFID front end 630 are coupled to antenna driver and tuning circuitry 640, which is further coupled to an antenna 642. In this embodiment, the same antenna can be used for transmission and reception, however other embodiments may utilize separate transmission and reception antennas. RFID tracking communication port 630 can be wirelessly coupled with an asset communication port of an asset. For example, an asset can take the form of fob 400, which can include RFID tag 412′ (FIG. 3) and/or RF transmitter 408 (FIG. 3), in bin 550 with which RFID tracking communication port 630 can be coupled. In embodiments, antenna 642 can be attached to and/or formed in back wall 557 of bracket 552 so that when fob 400 is in bin 550 and bin 550 is closed, antenna 642 can be in proximity to fob transmitter 408 and/or RFID identifier 410′/tag 412′. Asset tracking device 630 can also include translation circuitry 650 coupled to tracking communication ports 620, 630. In this embodiment, translation circuitry 650 can include a microprocessor 652 coupled to USB tracking communication port 630 and RFID front end 632 of RFID tracking communication port 630. Microprocessor 652 may be suitably programmed to sense when an asset, such as fob 400, couples to RFID tracking communication port 630 via the asset communication port, and may also be programmed to query the asset via RFID tracking communication port 630 for at least one unique asset identifier, such as identifier 410. In other embodiments, an identification of fob 400 can be initiated by pressing a button 402 (FIG. 3) to transmit a command as described above. In the example shown, translation circuitry 650 can also include a clock 654 coupled to microprocessor 652. Translation circuitry 650 can further include electrostatic discharge (ESD) protection 656 for a communication connection between microprocessor 652 and communication bus 350 of the SAM 302. One non-limiting example for suitable ESD protection 656 is the ESD Protection Device for 1-Wire Interfaces, model DS9503 from Maxim Integrated. Some embodiments may not have ESD protection. One non-limiting example of a suitable microprocessor 652 is the model PIC24FJ256GB110 microprocessor from Microchip Technology Incorporated. In this embodiment, microprocessor 652 can present the at least one unique asset identifier to controller 310 via ESD protection 656 and as facilitated by communication bus 350 coupled to controller 310 as has been discussed previously.
Some assets coupled to asset tracking device 610 in the system for asset management 600 can be charged over its respective tracking communication port to asset communication port connection when coupled. For example, USB devices connected to USB tracking communication port can be charged by virtue of power circuitry 660 connected thereto. Power circuitry 660 in embodiments can be connected to an external power source 662 via a power connector 664, such as a USB port, which can include a voltage supply pin. The voltage supply pin may be configured to receive power from a variety of sources, including a connection from SAM 302. Those skilled in the art can choose from a variety of power circuitry 660 topologies to condition, if necessary, and pass through power to USB tracking communication port 620 or other tracking communication port. Where the tracking communication port is a USB tracking communication port 620, five volts may be provided to the USB VCC pin of connector 664 as known by those skilled in the art, thereby providing charging capability in addition to tracking capability for the coupled asset.
It should be understood that other wireless communication protocols besides RFID can be employed to track assets in embodiments. For example, a form of near field communication (NFC) can be employed instead of or in addition to RFID. Since NFC typically occurs over very short distances, bin 550 can act as an NFC alignment pad to ensure a user places their asset so that suitable range and/or orientation can be achieved. Many assets include NFC ports, such as, but not limited to smartphones. With some assets having NFC ports, the asset tracking device 610 may be able to query the asset over the NFC connection for a unique asset identifier without modifying the asset, similar to the use of fob 400's existing RF transmissions in embodiments. Some NFC-enabled assets, however, may need a software application to be installed on the asset and configured to provide a unique asset identifier in response to NFC communications from the asset tracking device 610. The software application may include instructions executable by a machine (the asset) and tangibly embodied on at least one program storage device. The instructions are for performing a method of asset management, wherein the method includes monitoring an asset communication port for an identification query from a tracking communication port. The method also includes sending at least one unique identifier to the tracking communication port via the asset communication port. In the case where the tracking communication port and the asset communication port are NFC-compatible, the communications by such an application could take place wirelessly with an NFC protocol. The use of NFC protocols is well within the capabilities of those skilled in the art.
FIG. 15 illustrates one embodiment of a method of asset management. In step 700, an asset having an asset communication port is sensed when it couples to a tracking communication port. This can be accomplished, for example, with translation circuitry coupled to a tracking communication port as discussed above. In step 702, the asset is queried, over the tracking communication port, for at least one unique asset identifier. Depending on the embodiment, “querying the asset” can mean the asset is queried via the tracking communication port connection, or it can mean the asset communication port is queried via the tracking communication port/asset communication port connection. The first case might occur with a USB type connection, while the second case might occur, for example, where an RFID tag has been added to an asset. This can also be accomplished, for example, with translation circuitry coupled to the tracking communication port as discussed above. In some embodiments, this query may occur using a first communication protocol 704. Non limiting examples of a first communication protocol include a radio frequency identification (RFID) protocol, a radio frequency (RF) protocol, a near field communication (NFC) protocol, a Bluetooth protocol, a universal serial bus (USB) protocol, a firewire protocol, a serial communication protocol, a parallel communication protocol, and an optical communication protocol. Examples of unique asset identifiers have also been discussed above, and may include, but are not limited to a media access control (MAC) address, a vendor identification (VID), a product identification (PID), a product serial string, or any combination thereof. In step 706, using translation circuitry, the at least one unique asset identifier is presented to a controller. In some embodiments, this presentation may occur using a second communication protocol 708. Non-limiting examples of a second communication protocol include a 1-Wire communication protocol and a communication bus protocol.
FIG. 16 illustrates another embodiment of a method of asset management. In step 710, a user is identified via a user interface. As discussed previously, examples of a suitable user interface include, but are not limited to a keypad, a fingerprint reader, a proximity card reader, an iris identification device, a retinal scanning identification device, a hand shape identification device, and a magnetic card reader. In step 712, an asset having an asset communication port is sensed when it couples to a tracking communication port. This can be accomplished, for example, with translation circuitry coupled to a tracking communication port as discussed above. In step 714, the asset is queried, over the tracking communication port, for at least one unique asset identifier. Depending on the embodiment, “querying the asset” can mean the asset is queried via the tracking communication port connection, or it can mean the asset communication port is queried via the tracking communication port/asset communication port connection. The first case might occur with a USB type connection, while the second case might occur, for example, where an RFID tag has been added to an asset. This can also be accomplished, for example, with translation circuitry coupled to the tracking communication port as discussed above. In some embodiments, this query may occur using a first communication protocol 704 as discussed previously. In step 716, using translation circuitry, the at least one unique asset identifier is presented to a controller. In some embodiments, this presentation may occur using a second communication protocol 708 as also discussed previously. In step 718, a record is stored corresponding to the at least one unique asset identifier and the identified user. Such a record could be stored in a database or other storage or memory. One example of a record stored could include the name and/or identification of the user identified via the user interface and a list of one or more assets removed and/or returned by the user. Such a record may also include information showing the date/time the transaction took place and/or an alarm or report status for the transaction.
FIG. 17 illustrates a further method of asset management. In step 720, an asset having an asset communication port is sensed when it interacts with a tracking communication port. This can be accomplished, for example, with translation circuitry coupled to a tracking communication port as discussed above. The interaction between the asset communication port and the tracking communication port can be a coupling, for example, when the asset is returned and plugged into the tracking communication port. Alternatively, the interaction between the asset communication port and the tracking communication port can be a decoupling, for example, when the asset is removed and unplugged from the tracking communication port.
A determination 722 is made whether or not the sensed interaction of the asset communication port with the tracking communication port is a coupling or a decoupling. If the interaction comprises a coupling, then in step 724, the asset is queried over the tracking communication port for at least one unique asset identifier. Depending on the embodiment, “querying the asset” can mean the asset is queried via the tracking communication port connection, or it can mean the asset communication port is queried via the tracking communication port/asset communication port connection. The first case might occur with a USB type connection, while the second case might occur, for example, where an RFID tag has been added to an asset. This can also be accomplished, for example, with translation circuitry coupled to the tracking communication port as discussed above. In some embodiments, this query may occur using a first communication protocol 704 as discussed previously. In step 726, a status for the at least one unique asset identifier is set as present. Alternatively, if determination 722 finds that the interaction comprises a decoupling, then in step 728, the status for the at least one unique asset identifier is set as not present. Whether the interaction was a coupling or a decoupling, after the status is set to present or not present, the status for the at least one unique asset identifier is communicated to a controller in step 730. In some embodiments, this communication may occur using a second communication protocol 708 as also discussed previously.
FIG. 18 illustrates another embodiment of a method for asset management. In step 732, a user is identified via a user interface. As discussed previously, examples of a suitable user interface include, but are not limited to a keypad, a fingerprint reader, a proximity card reader, an iris identification device, a retinal scanning identification device, a hand shape identification device, and a magnetic card reader. In step 734, an asset having an asset communication port is sensed when it interacts with a tracking communication port. Depending on the embodiment, “querying the asset” can mean the asset is queried via the tracking communication port connection, or it can mean the asset communication port is queried via the tracking communication port/asset communication port connection. The first case might occur with a USB type connection, while the second case might occur, for example, where an RFID tag has been added to an asset. This can be accomplished, for example, with translation circuitry coupled to a tracking communication port as discussed above. The interaction between the asset communication port and the tracking communication port can be a coupling, for example, when the asset is returned and plugged into the tracking communication port. Alternatively, the interaction between the asset communication port and the tracking communication port can be a decoupling, for example, when the asset is removed and unplugged from the tracking communication port.
A determination 736 is made whether or not the sensed interaction of the asset communication port with the tracking communication port is a coupling or a decoupling. If the interaction comprises a coupling, then in step 738, the asset is queried over the tracking communication port for at least one unique asset identifier. This can also be accomplished, for example, with translation circuitry coupled to the tracking communication port as discussed above. In some embodiments, this query may occur using a first communication protocol 734 as discussed previously. In step 740, a status for the at least one unique asset identifier is set as present. Alternatively, if determination 736 finds that the interaction comprises a decoupling, then in step 742, the status for the at least one unique asset identifier is set as not present. Whether the interaction was a coupling or a decoupling, after the status is set to present or not present, the status for the at least one unique asset identifier is communicated to a controller in step 744. In some embodiments, this communication may occur using a second communication protocol 708 as also discussed previously. In step 746, a record is stored corresponding to the at least one unique asset identifier and the identified user. Such a record could be stored in a database or other storage or memory. One example of a record stored could include the name and/or identification of the user identified via the user interface and a list of one or more assets removed and/or returned by the user. Such a record may also include information showing the date/time the transaction took place and/or an alarm or report status for the transaction.
Having thus described several embodiments of the claimed invention, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Many advantages for the systems and methods for communication port based asset management have been discussed. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested hereby, and are within the spirit and the scope of the claimed invention. As one example, it may be desirable to provide a feedback indicator, such as a light emitting diode (LED), near each asset tracking port or easily associated with each asset tracking port so that a controller may enable the feedback indicator following user authentication to show then which asset(s) may be validly removed by the user. In some embodiments, if the asset has a screen or other feedback indicator built into the asset, then the controller might send a command to the asset, over the tracking communication port/asset communication port connection to turn on a feedback indicator on the device (for example, by turning on the display of the device) when it's authorized user has authenticated with the system.
For example, another example of a SAM 302 is seen in FIGS. 12 and 16-18. Here, receptacle 550 can stretch across more than one position of SAM 302 to accommodate multiple fobs 400. In this example, it can be advantageous to employ a fob arrangement 400 such as that seen in FIGS. 13-15, where the ring or the like 418 can be replaced with a rivet or the like to hold key(s) 414 and fob(s) 400 together. With reference to FIGS. 16-18, a key 414 of each fob arrangement 400 can be inserted into a position of SAM 302 and used to retain fob arrangement 400 in receptacle 550. More specifically, key 414 can be retained in a corresponding lock cylinder until a controller releases a retention device. More specifically, the cylinder can be retained in a locked position as shown in FIG. 12, which can be maintained by a solenoid or other retention device behind the panel of SAM 302 to prevent rotation of the lock cylinder out of the locked position. Upon authorization, a controller can release the retention device so that key 414 can be rotated out of the locked position, as illustrated in FIGS. 16 and 17. Once in the unlocked position, shown in FIG. 17, key 414 can be removed from the cylinder and fob arrangement 400 can be removed from the SAM. Upon return, key 414 is inserted into the unlocked cylinder, then rotated into the locked position, at which point the retention device locks the cylinder in place. Because rotation of key 414 from the unlocked position into the locked position sweeps fob(s) 400 into bin 550, fob(s) 400 are retained therein. In many fobs, a valet key is held in the fob and can be released using a button or the like on the back of the fob. Such fobs often have passage 416 formed in a head of such a valet key so that release of the valet key would allow removal of the rest of the fob from SAM 302 were it not for receptacle 550 preventing access to the button on the back of the fob and withdrawal of the fob from the valet key, combined with the action of rivet 418 and key 414 to hold the valet key in place. Thus, embodiments as shown in FIGS. 12-18 prevent unauthorized removal of fob(s) 400 by release of fob(s) 400 from corresponding valet keys that are held in SAM 302 by key(s) 414 retained in locked cylinders of SAM 302.
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and/or computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
FIG. 7 shows a schematic block diagram of a general-purpose computer/system/computing device 700 that can be used to implement and/or practice the method(s) and/or system(s) described herein, which can be coded as a set of instructions on removable or hard media for use computer 700 as suggested above. Computer 700 can include at least one microprocessor or central processing unit (CPU) 705, which can also be construed as a computing device and can be interconnected via a system bus 720 to machine readable media 775. Machine readable media 775 can include, for example, a random access memory (RAM) 710, a read-only memory (ROM) 715, a removable and/or program storage device 755 and a mass data and/or program storage device 750. An input/output (I/O) adapter 730 can connect mass storage device 750 and removable storage device 755 to system bus 720. A user interface 735 can connect a keyboard 765 and a mouse 760 to system bus 720, and a port adapter 725 connects a data port 745 to system bus 720 and a display adapter 740 can connect a display device 770. ROM 715 can contain the basic operating system for computer system 700. Examples of removable data and/or program storage device 755 include magnetic media such as floppy drives, tape drives, portable flash drives, zip drives, and optical media such as CD ROM or DVD drives. Examples of mass data and/or program storage device 750 include hard disk drives and non-volatile memory such as flash memory. In addition to keyboard 765 and mouse 760, other user input devices such as trackballs, writing tablets, pressure pads, microphones, light pens and position-sensing screen displays may be connected to user interface 735. Examples of display device 770 include cathode-ray tubes (CRT) and liquid crystal displays (LCD).
A machine readable computer program may be created by one of skill in the art and stored in and/or executed by computer system 700 or a data and/or any one or more of machine readable medium 775 to simplify the practicing of this invention. In operation, information for the computer program created to run the present invention can be loaded on the appropriate removable data and/or program storage device 755, fed through data port 745 or entered using keyboard 765. A user can control the program by manipulating functions performed by the computer program and providing other data inputs via any of the above mentioned data input means. Display device 770 can provide a means for the user to accurately control the computer program and perform the desired tasks described herein.
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Patent Application
20150356846
