Storage and retrieval of identification tag data associated with an asset
Identification tags with NFC and RFID technologies facilitate efficient asset management in data centers by enabling precise location and tracking of assets, addressing the challenge of cable identification complexity.
Patent Information
- Application Number
- JP2022513082
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-08-30
- Filing Date
- 2020-08-27
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2040-08-27
AI Technical Summary
The increasing number of network and power cables in data centers makes it difficult to identify specific cables or assets for repair or replacement due to the large quantity and complexity of cables, leading to inefficiencies in maintenance and management.
The use of identification tags, such as NFC and RFID, attached to assets within the data center, which are read by a tag reader and processed by a computing device to generate a GUI for asset management, allowing for efficient scanning and tracking of assets using both short-range and long-range protocols.
Enables precise identification and management of assets within data centers, simplifying the process of locating and replacing malfunctioning cables by providing real-time tracking and visual/audio notifications, thereby improving maintenance efficiency.
Smart Images

Figure 0007590413000001 
Figure 0007590413000002 
Figure 0007590413000003
Abstract
Description
[Technical field]
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Application No. 62 / 894,166, filed August 30, 2019, which is incorporated herein by reference for all purposes. [Background technology]
[0002] The present invention relates generally to the technical field of associating identification tags with assets (e.g., servers, cables and cable bundles in a data center) and using the identification tags, tag readers configured to access data encoded in the identification tags, and computing devices in communication with the tag readers to store and read data regarding the assets. Summary of the Invention
[0003] The present invention provides systems and methods comprising one or more identification tags, one or more identification tag readers, and one or more computing devices communicatively coupled to a network, the computing devices configured to receive identification tag data from the identification tags using the identification tag readers, receive and store the identification tag data or additional data related to an associated asset received from the GUI, and display the identification tag or additional data in response to scanning an identification tag and receiving search parameters from the GUI used to identify previously scanned tags or associated resources.
[0004] The above features and advantages of the present invention will be better understood from the following detailed description taken in conjunction with the accompanying drawings. [Brief description of the drawings]
[0005] [Figure 1A] 1 shows a first non-limiting example of multiple identification tags coupled to a self-laminating label or marker. [Figure 1B]1 shows a second non-limiting example of multiple identification tags coupled to a self-laminating label or marker. [Figure 2A] Non-limiting examples of labels are shown below. [Figure 2B] 1 illustrates non-limiting examples of labels configured to be attached to assets. [Figure 3A] 1 shows a first non-limiting example of an identification tag reader. [Figure 3B] 1 illustrates a second non-limiting example of an identification tag reader that includes one or more antennas, embedded software, and an embedded database. [Figure 4A] 1 illustrates a possible system for storing and retrieving identification tag data associated with an asset. [Figure 4B] Illustrates a number of network assets, each labeled with an identification tag. [Diagram 5] FIG. 2 is a flow diagram illustrating method steps in a possible embodiment of a method for storing and retrieving identification tag data associated with an asset. [Figure 6] 1 is a user interface illustrating a possible embodiment for storing and retrieving identification tag data associated with an asset. [Figure 7] FIG. 2 is a flow diagram illustrating method steps in a possible embodiment of a method for storing and retrieving identification tag data associated with an asset. [Figure 8] 1 is a user interface illustrating a possible embodiment for storing and retrieving identification tag data associated with an asset. [Figure 9] FIG. 2 is a flow diagram illustrating method steps in a possible embodiment of a method for storing and retrieving identification tag data associated with an asset. [Figure 10] 1 is a user interface illustrating a possible embodiment for storing and retrieving identification tag data associated with an asset. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0006] The present invention will now be described in detail with reference to the accompanying drawings, briefly described above. In the following description, numerous specific details are set forth to illustrate the best mode for carrying out the applicant's invention and to enable those skilled in the art to make and use the invention. However, it will be apparent to those skilled in the art that the invention can be practiced without including some of these specific details. In other instances, known machines, structures and method steps have not been described in particular detail to avoid unnecessarily obscuring the invention. Unless otherwise specified, like parts and method steps will be referred to with like reference numerals.
[0007] Near Field Communication (NFC) and Radio Frequency Identification (RFID) are examples of technologies that use integrated circuits embedded in identification tags to track assets. NFC and RFID readers are used to determine the presence of active or passive NFC and / or RFID (or other identifier) tags within the reader's field and thus locate and identify one or more identification tags affixed to assets (including, for example, data center network assets, inventory, employee ID cards, etc.). Thousands of tags can be interrogated, read, identified, and located by a single reader in seconds.
[0008] As a non-limiting example described herein, NFC and / or RFID technology may also be used in combination with such identification tags to assist in the generation and reception of information describing attributes of assets in a data center, such as servers, server cables and / or bundles of cables used in a network accessible by the data center, etc. A network is a collection of links and nodes (e.g., multiple computers and / or other devices connected together) arranged such that information is passed from one part of the network to another through multiple links and through various nodes. Examples of networks include the Internet, the Public Switched Telephone Network, the Global Telex Network, computer networks (e.g., intranets, extranets, local area networks or wide area networks), wired networks, and wireless networks.
[0009] A well-known example of a network is the Internet, a worldwide computer network arranged to enable easy and robust information exchange between computers and users. Millions of people around the world access computers connected to the Internet through Internet Service Providers (ISPs). Content providers place multimedia information (text, graphics, audio, video, animation and other forms of data) at specific locations on the Internet called websites. The combination of all websites on the Internet and their corresponding web pages is commonly referred to as the World Wide Web, or simply the Web.
[0010] Within a data center, servers and / or other computers may be networked together using any network cables known in the art to interconnect or power all components within the data center. Non-limiting examples of such cables include fiber optic cables, Ethernet cables, Fibre Channel cables, copper cables, AC / DC power cables, ground cables, etc. As data centers grow, more servers and other network components (switches, routers, etc.) may be installed, each of which may be networked with each other and with external networks, such as the Internet and / or an Internet service provider. Often, the connections of these network resources are made using network cables, such as fiber optic cables, Ethernet cables, etc. Similarly, a lot of power is required to power the network components, the data center itself, and the cooling of the data center, requiring the data center to have multiple power and / or ground cables, as non-limiting examples.
[0011] As the number of network components in a data center grows, the number of network, power, and other associated cables required also grows proportionately, and may include thousands of cables. As with any resource, over time, these network and power cables may fail. In this case, the sheer number of cables may make it difficult to identify a particular cable or server, or a bundle of cables associated with a server, in order to repair or replace a problematic cable.
[0012] To simplify the task of identifying specific assets, the disclosed embodiments allow a user to attach or associate a first (e.g., short-range) identification tag (e.g., NFC) and / or a second (e.g., long-range) identification tag (e.g., RFID) to each asset or collection of assets. For example, in the disclosed embodiments, a user may attach an identification tag to each of a particular server, cable, and / or bundle of cables.
[0013] In the disclosed embodiments, a user can use an identification tag reader to scan each tag to read data stored in the tag, such as a unique identifier encoded within the tag, and transmit the scanned data over a network to a computing device, such as a server or client device.
[0014] In some embodiments, the identification tag reader may have built-in software and / or a database. In these embodiments, the scanned data from the tag may be processed by the software and stored in the built-in database. The data may then be transmitted over a network to a computing device that may receive the scanned data, process it, generate a database record associated with the tag, and store it in the system database. In some embodiments, the data record may be identified by a unique identifier encoded on the tag. In one embodiment, the reader may read the data stored on the tag and stream the data over a network to a computing device that may receive the scanned data, process it, generate a database record associated with the tag (possibly identified using the encoded unique identifier), and store it in the system database. In additional embodiments, it is envisioned that the data stored on the tag is read and processed using security, which may require some type of encryption as the data is passed from the tag to the reader, to the server, to the client, etc.
[0015] The computing device may then generate a graphical user interface (GUI) on a display screen of the computing device, and one or more GUI components of the GUI may enable a user to enter additional details related to the tag or the asset to which the tag is attached or in the vicinity of the tag, such as the name, associated resources, the purpose of the resource, user comments about the tag, etc. In an embodiment using long-range identification tags (e.g., RFID), the GUI may include a GUI component (e.g., a checkbox) that indicates that the asset is best identified if a particular identification tag protocol is used to locate the asset. In an embodiment including multiple computing devices, the server device may transmit the GUI to the client devices for display.
[0016] The computing device can use the generated and displayed GUI to receive user input, including additional input by the user related to the tag data, such as additional descriptors, images, or data. In embodiments where long-range identification tags are used and the appropriate GUI component is selected (e.g., a checkbox is checked), the data record can be updated to include a flag that the reader should scan using a long-range identification tag protocol such as RFID. In embodiments involving multiple computing devices, the client device may then transmit the received user input data to the server device. The computing device can then receive the input data and store the updated data in the appropriate data record associated with the tag identifier.
[0017] Once the database is populated with all the asset data (asset data is associated in the database with a particular tag identifier), a user can use an identification tag reader to scan any of the individual tags associated with the asset. In embodiments where the reader includes embedded software and a database, the reader may temporarily upload the database records to the embedded database. The reader may receive the tag data from each tag as it is scanned. In embodiments where the reader includes embedded software and a database, the embedded software in the tag reader may receive and process the scanned tag data from each tag and perform a database query that selects data records from the embedded database that have a common unique identifier. The embedded software of the reader may then send data from the matching data records to a computing device for processing. In embodiments where the reader streams the scanned tag data over a network to a computing device, the computing device may receive and process the scanned tag data from each tag and perform a database query that selects data records from the database that have a common unique identifier.
[0018] The computing device can then generate a GUI for displaying the data stored in the matching data record and display the GUI to the user. In embodiments including multiple computing devices, the server device may generate aspects of the GUI and transmit the GUI over a network to the client device for display.
[0019] In some embodiments, a user may wish to search for assets associated with a particular identification tag (e.g., an identification tag on a network cable that has been determined by the data center system to be malfunctioning may be found and replaced). In these embodiments, the user may access the system and indicate a desire to locate one or more assets associated with one or more particular identification tags. In response to this request, the computing device may generate a GUI that receives input from the user defining search parameters for finding the assets and their associated identification tags.
[0020] For example, the GUI may include one or more GUI components for receiving user input from the user, for each identification tag that the user wishes to locate, including a unique identifier for the identification tag, the asset associated with the identification tag, the name of the asset, the purpose of the asset, any notes entered by the user, etc. In an embodiment in which a long-range identification tag (e.g., RFID) is used to identify an associated asset (e.g., a server or network cable bundle associated with a cable being discovered), the system may first locate the first asset (e.g., a server or network cable bundle) using a long-range identification tag protocol and then indicate a flag indicating that a short-range identification tag protocol (e.g., NFC) should be applied to locate the particular cable.
[0021] In an embodiment including multiple computing devices, the server device may generate a GUI and transmit the GUI over a network to the client device for display. Once the GUI is displayed, the user device (e.g., the client device) may receive user input and transmit it over the network to the server device for processing. This processing may include using the input from the GUI to indicate data records in a database that contain data matching the data entered by the user into the GUI. The computing device may then select the matching data record(s) from the database, possibly using a database query command. The selected data may include the unique identifier of the tag stored in the data record as received above, and possibly the associated asset data.
[0022] In embodiments where the reader includes embedded software and a database, the computing device may transmit the selected data (selected identification tags and their associated asset data) over a network to the reader for processing by the embedded software and storage in the embedded database. In embodiments where the reader streams scanned tag data over a network to the computing device, the computing device may temporarily store the selected data from the database on the computing device. The user may then scan for the desired identification tags and their associated assets.
[0023] In embodiments that use long-range identification tags to identify associated assets (e.g., a server or network cable bundle associated with the cable being found), the selected data may include a database flag indicating that the reader should scan using a long-range identification tag protocol such as RFID. In embodiments where the reader includes embedded software and a database, the computing device may transmit a flag over a network to the reader, which may process the flag and automatically use the long-range identification tag protocol to scan the identification tag. In embodiments where the reader streams scanned tag data over a network to the computing device, the computing device may use a data flag to indicate that the reader should utilize the long-range identification tag protocol to scan the tag.
[0024] As the user scans for the required identification tags, the reader receives data from each identification tag and may compare the received data with data stored in an embedded database using embedded software or transmit the data over a network to a computing device for comparison with selected data temporarily stored on the computing device.
[0025] The reader may further include optical (e.g., LED) or audio components built into the reader for providing audio and visual notifications (e.g., audio alerts or LED signals) configured by the user, such that the device may trigger custom color LED illumination and / or custom audio alerts when the scanned and received identification tag data matches a unique identifier stored in an embedded database (for embodiments including embedded software and / or databases) or a unique identifier temporarily stored on the computing device (for embodiments in which the reader streams scanned tag data over a network to a computing device). The user may then identify the long-range identification tag associated with the asset (e.g., the server or network cable bundle to which the desired cable belongs).
[0026] In some embodiments, the identified match may be received by the computing device over a network from software logic on the computing device or from embedded software on the reader. In response to receiving the identified match, the computing device may generate a command to generate a GUI or update a currently displayed GUI, where the GUI displays a GUI component that includes a notification that the most recently scanned identification tag / asset matches one of the unique identifiers selected from the database record. This notification may then be displayed on the GUI of the computing device.
[0027] In embodiments that use long-range identification tags to identify associated assets, the embedded software may include logic to automatically switch from the long-range identification tag protocol to the short-range identification tag protocol for embodiments that include embedded software and / or a database. In embodiments in which a reader streams scanned tag data over a network to a computing device, the computing device may include logic to switch from the long-range identifier protocol to the short-range identification tag protocol after sending a signal that triggers a custom alert on the reader.
[0028] If the reader operates using a short-range identification tag protocol (e.g., NFC), or in embodiments that use short-range identification tags to identify an associated asset (e.g., an identified server or an individual cable associated with a network cable bundle that the user is attempting to find), the user can scan for the desired identification tag and its associated asset.
[0029] In an embodiment where the reader includes embedded software and a database, if there is no flag indicating the use of the long-range identification tag protocol, or if the reader is switched from the long-range to the short-range identification tag protocol after finding a matching identification tag using the long-range identification tag protocol, the reader can cooperate with the computing device to automatically scan the identification tag using the short-range identification tag protocol. In an embodiment where the reader streams the scanned tag data to the computing device over a network, the computing device may not be able to identify a flag indicating the use of the long-range identification tag protocol or data logic that currently indicates that the reader should use the short-range identification tag protocol to scan the tag.
[0030] As described above, when a user scans for a requested identification tag, the reader may receive data from each of the identification tags and compare the received data with data stored in an embedded database using embedded software or with selected data transmitted over a network to the computing device and temporarily stored. The reader may also include components embedded in the reader for providing audio and visual notifications (e.g., audio alerts or LED signals) configured by the user, such that the device triggers custom color LED illumination and / or custom audio alerts when the scanned and received identification tag data matches a unique identifier stored in the embedded database (for embodiments including embedded software and / or a database) or a unique identifier temporarily stored in the computing device (for embodiments in which the reader streams the scanned tag data to the computing device over a network). The user may then identify the short-range identification tag associated with the asset (e.g., a cable connected to a server or a cable included in a network cable bundle).
[0031] In some embodiments, the identified match may be received by the computing device from software logic of the computing device or from embedded software of the reader over a network. In response to receiving the identified match, the computing device may generate a command to generate a GUI or update a currently displayed GUI, where the GUI includes a GUI component that includes a notification that the most recently scanned identification tag / asset matches one of the unique identifiers selected from the database record. This notification may then be displayed on the GUI of the computing device.
[0032] A variety of different environments can be used to accomplish the steps of the methods of the embodiments disclosed herein. As seen in Figures 1A and 1B, the disclosed embodiments can utilize one or more identification tags 105, which can include one or more short-range identification tags and / or one or more long-range identification tags, optionally attached to or embedded in an adhesive backing. As non-limiting examples, the short-range identification tags can include one or more wireless NFC tags, and the long-range identification tags can include one or more wireless RFID tags, both of which may further include a microchip (each of which may include a unique identifier) that utilizes a user memory, and which may be optionally coupled to the label, and optionally embedded in the label, incorporated on the surface of the label, or affixed or attached to the label.
[0033] 2A and 2B show non-limiting examples of labels that may be used in the disclosed embodiments. In some non-limiting embodiments, such as that seen in FIG. 2A, these labels may include a rectangular body that generally includes three layers including a substrate, an adhesive, and a removable liner. In some embodiments, to use the label, a user may remove the release liner from the label to expose the adhesive on the underside of the substrate. In some embodiments, the substrate of the label may be wrapped over itself until no substrate remains.
[0034] In some embodiments, the label may include a self-laminating marker. In some embodiments, the label may include a printable area, where the user may include a label, a transparent film layer, and a tail end over the printable area. In some embodiments, the labels or markers may be provided as part of a media roll or strip, with individual labels or markers separated from the media roll or strip, as seen in Figures 1A and 1B.
[0035] In some disclosed embodiments, such as those seen in Figures 2B and 4B, the label can include a wire marker, which includes a label or tag attached to the wire or cable to identify the wire or cable and / or its purpose.
[0036] Non-limiting examples of such self-laminating labels incorporating long-range or short-range identification tags 105 are shown in Figures 1A-2B. However, these are non-limiting examples. The identification tag 105 in the disclosed embodiments may include a tag configured to be utilized in combination with any wireless interrogation technology known in the art (which may include, for example, any so-called short-range or long-range identification tag technology), which may be attached to an asset and configured to be read by an identification tag reader 300.
[0037] The tags 105 in the disclosed embodiments may utilize radio transmission broadcast communications, and the tags 150 may be read by the identification tag reader 300 in response to an interrogation signal transmitted by the identification tag reader 300. Thus, the tags 105 in the disclosed embodiments may be utilized to automatically identify and track the location and / or status of assets in real time, possibly within a building or other containment area, such as the data center 140 described herein. By way of non-limiting example, the assets may include people or things, such as network components (e.g., servers 110, server cables, groups or bundles of server cables, etc.), which are described in more detail below, inventory items, identification tags for people, etc.
[0038] These tags 105 can use any combination of passive or active short-range or long-range identification tag technologies. Active identification tag technologies utilize battery-powered beacons that continuously transmit a signal containing a unique identifier for each tag 105. Passive identification tag technologies do not use batteries, but are powered by collecting energy from a tag reader 300 (described below), and broadcast the unique identifier and any additional data on the tag 105 to the reader 300 in response to an interrogation signal broadcast by the reader 300. In some disclosed embodiments, only passive tags are used.
[0039] Thus, each asset in the disclosed system can be assigned a unique identification tag 105 by attaching a label containing the identification tag 105 to the asset. The identification tag 105 can be registered in software or a database as being associated with the asset, as described below. Each reader 300 can generate an alert or notify one or more servers 110 and / or clients 120 when a passive or active tag 105 enters or leaves the reader's 300 field.
[0040] 3A and 3B show an example of an identification tag reader unit 300. Each reader 300 may be freestanding and include one or more fixed-location or mobile passive and / or active EPC Gen 2 (and ISO 18000-63) compliant short-range or long-range identification tag reader / writer configurations. Each reader 300 may be a standalone device, as part of an integrated system used to track and locate tagged assets according to the proximity of the tag 105 to the nearest reader 300, or may be one of multiple devices within a designated location.
[0041] Each reader 300 may be configured to transmit interrogation signals configured to detect the presence of one or more tags 105 (and thus their associated assets) within the reader's 300 field of view and track their presence via radio transmission broadcast communications. This detection may be responsive to and / or dependent on each tag's 105 radio signal and a received signal strength indicator (RSSI) relative to a fixed reference point of the reader 300. The reader 300 may also optionally determine the location of each tag 105 within its field of view. As non-limiting examples, the reader 300 may track network components within a data center 140, cars on an assembly line, locate pallets of goods within a warehouse, find equipment or employees within an office building, etc.
[0042] The reader 300 may further receive input from the tag 105 in a form that uniquely identifies the tag 105, an RSSI for the signal received from the tag 105, and / or any additional data stored in the tag 105. In some embodiments, the reader 300 may be configured for sensory data collection. For example, each reader 300 may have a sensor that identifies, in association with each unique tag ID, the temperature associated with each unique tag ID, global motion such as that experienced during an earthquake, etc.
[0043] Tag data received by reader 300 may be analyzed and processed using on-board firmware or other software 310 and / or communicated (e.g., over a local network) to dedicated server 110 or proprietary software running on client 120 that processes the received data. This processed data may be used, for example, for asset identification, asset tracking, inventory control in data center 140, retail, and / or supply chain or logistics environments.
[0044] Identification tag reader technology, in combination with configurations executing programmable logic in each reader 300, enables each reader 300 to operate in a two-way cloud-based environment, as seen in Figure 4A, and further enables two-way bidirectional communication between the reader device 300 and the application server 110 and / or client device 120. For example, as described below, each reader 300 includes embedded software 310 and / or database 320 that are located and operate within the reader 300 itself and that are configured to communicate meaningful information to and from the reader 300.
[0045] This remote location and bidirectional communication between the reader device 300 and the server 110 and / or client 120 devices allows the server 110 and / or client 120 devices to manage, deploy and install customizable software 310 on the device 300, which may be programmed to communicate meaningful information at the installation location. This software 310 may program the device 300 to support configurable program logic, profiles and / or parameters that may determine the hardware behavioral operation of common applications (e.g., asset tracking) running on the device 300.
[0046] Each of these devices may incorporate electronics, software, sensors, actuators, and network connectivity capabilities that are either incorporated between or connected to each of these components, in the server 110 and / or client device 120, allowing data to be collected and exchanged by the devices 300 and their embedded software 310.
[0047] The programmable and configurable software logic described above may be configured to receive instructions to scan one or more tags, possibly in response to user input from a scan button 340 on the reader or via configurable logic within the software 310. The reader 300 may then transmit an interrogation signal. The reader 300 may receive radio transmission broadcast communications from the identifying tags 105, thereby receiving notification that a tag 105 has entered the field of view of the reader 300 operating in long-range and / or short-range reader settings, and storing the associated data in the internal database 320. The software 310 may process the received tag 105 information within the reader 300 itself to determine current tag data for each detected tag 105 based on conditions satisfied in the programmable and configurable logic. This messaging model also allows for messages to be sent to the server 110 and / or client 120 devices in response to different events occurring within the system, as a non-limiting example. Thus, in some embodiments, reader 300 may be a programmable reader capable of performing customized and independent actions and communicating with and receiving communications from additional devices.
[0048] For example, each reader 300 may download and install customizable software 310 and programmable logic, profiles and / or parameters from a central location (e.g., from application server 110). When a tag 105 associated with a particular asset or person enters the field of the reader 300 (possibly in response to user input with scan button 340), the reader 300 may detect the presence of the tag 105 and store the tag in the reader's 300's internal database 320. The programmable logic, profiles and / or parameters in the customized configurable software 310 may cause the reader 300 to conditionally respond to an identified tag 105.
[0049] In one non-limiting embodiment, the host server 110 can push customizable software 310 and programmable logic, profiles and / or parameters to one or more readers 300, thereby efficiently processing and communicating tag status data for each tag 105 within the field of view of the reader 300.
[0050] In some embodiments, the model included in the short-range or long-range identification tag reader 300 may not process the received tag data, but instead may simply read data from all tags 105 in the reader's 300 field at a given time, and stream data from all identified tags 105 (as many as 100 per second) over the local network 100 for processing by customizable software running on the server 110 and / or client 120. A server-based rules engine may then process the tag data collected by the reader 300. As mentioned above, the network 100 may be a wired network or a cloud-based network accessible via Wi-Fi and / or Bluetooth.
[0051] Thus, the reader 300 may include embedded programmable firmware (e.g., on-board software 310 and database 320) that identifies all readable tags and responds accordingly, or may be a read-only reader that receives information about assets and transmits the data to one or more servers 110 and / or client devices 120 for processing, thereby providing low-bandwidth, bidirectional, cloud-enabled communications between the reader 300 and computing devices 120 for asset identification, locating and tracking.
[0052] The identification tag reader 300 may further include one or more internal antennas 330 as part of a communication subsystem (e.g., for connecting to a network such as an Ethernet network, an optical fiber network, a Wi-Fi® wireless network, a Bluetooth® network, etc., and / or for detecting the presence of the identification tag 105 as described above) and may be a read / write unit in light of the above characteristics. Each of the one or more antennas 330 may include antenna circuitry for wirelessly receiving data from the identification tag(s) 105. In some embodiments, the one or more antennas 330 may include short-range antenna circuitry for wirelessly receiving data from the identification tag 105 using an NFC protocol. In some embodiments, the one or more antennas may include long-range antenna circuitry for wirelessly receiving data from the identification tag 105 using a radio frequency identification protocol.
[0053] The identification tag reader 300 may further include an implemented touch chip for use as input for devices such as tablets and smartphones with touch-sensitive capacitive screens. It may also include a Bluetooth interface that may be configured to connect to and operate with Windows, Android, and iOS devices, as non-limiting examples, for mobile data capture. It may further include a focus NFC / RFID antenna 330, main RF field direction, scan button 340, operating status LED 360, the touch chip as described above, etc.
[0054] The reader 300 may further include hardware 360 for providing visual or audio feedback. Configurable logic, profiles and / or parameters, possibly set by a user, can create audio and visual notifications (e.g., audio alerts or LED signals) built into the reader such that the reader device 300 is configured to trigger illumination of a custom color LED and / or trigger a custom audio alert 360 when a particular tag 105 passes by the reader device 300.
[0055] The long-range and / or short-range identification tag reader 300 can be set up and configured with additional hardware (e.g., power source or batteries) and software (e.g., customizable software specific to each label placement, as described above, if desired) so that results from the reader 300 can be accessed on the network 100 using a network cable configuration, a wireless network and / or Bluetooth® technology.
[0056] 4A illustrates a simplified example of an environment including systems and / or structures that may be used to accomplish the methods and embodiments disclosed and described herein. For example, FIG. 4A includes the data center 140 described above, which may host one or more servers 110 and / or other computers within the data center 140, and may also provide the general infrastructure required to provide hosting services to Internet users, including hardware (e.g., server computing machines, routers, switches, network cables, power cables, etc.), software, Internet websites, hosting servers, and electronic communication means required to connect multiple computers and / or servers to the Internet or any other network 100.
[0057] The embodiments shown and described herein exist within the framework of network 100 and are not intended to be limitations on possible network configurations or connectivity functions. Such networks 100 may include, by way of non-limiting examples, the Internet, a public switched telephone network, a global telex network, a computer network (e.g., an intranet, an extranet, a local area network, or a wide area network), a wired network, a wireless network, a telephone network, an enterprise network backbone, or any other combination of networks known or later developed.
[0058] The at least one server 110 and the at least one client 120 may be communicatively coupled to the network 100 via any method of network connection known in the art or developed in the future, including, but not limited to, wired, wireless, modem, dial-up, satellite, cable modem, digital subscriber line (DSL), asymmetric digital subscriber line (ASDL), virtual private network (VPN), integrated services digital network (ISDN), X.25, Ethernet, token ring, Fiber Distributed Data Interface (FDDI), Asynchronous Transfer Mode (ATM), Infrared Data Association (IrDA), wireless, WAN technologies (T1, Frame Relay), Point-to-Point Protocol over Ethernet (PPPoE), and / or any combination thereof.
[0059] The methods disclosed herein may be performed by any central processing unit (CPU) in any computing system, such as a microprocessor running on at least one of the servers 110 and / or clients 120 and executing instructions (perhaps as scripts and / or software, possibly as software modules / components) stored on a computer-readable medium accessible to the CPU, such as a hard disk drive on the servers 110 and / or clients 120.
[0060] Server(s) 110 may include any computing device or program that provides a service to other computers, programs, or users within the same computer or over computer network 100. By way of non-limiting example, server 110 may include application, communication, mail, database, proxy, fax, file, media, web, peer-to-peer, standalone, software, or hardware servers (i.e., server computing devices), and may use any server format known in the art or developed in the future (possibly a shared hosting server, a virtual private hosting server, a dedicated hosting server, a cloud hosting solution, a grid hosting solution, or any combination thereof), and may be used, for example, to provide access to data necessary for a combination of software requested by client 120.
[0061] Server 110 may reside within a server cluster. These clusters may include a group of tightly coupled computers that work together so that in many respects they can be viewed as if they were a single computer. The components may be connected together via a high-speed local area network that can provide improved performance and / or availability over that offered by a single computer.
[0062] The server 110 and / or the client 120 may be communicatively coupled to a data storage 130 that contains any information required or needed by the systems and / or described herein. The data storage 130 may be any computer component, device and / or recording medium capable of holding digital data for some interval of time used in calculations. The storage may hold stored content for any data needed within a single machine or a cluster of computers across the network 100, within separate memory areas of the same machine such as different hard drives, or within separate partitions within the same hard drive such as a database partition.
[0063] Non-limiting examples of data storage 130 may include, but are not limited to, network area storage ("NAS"), which may be a self-contained file-level computer data storage that is connected to a computer network and provides file-based data storage services to the computer network. The storage subsystem may be a storage area network ("SAN", which is an architecture for connecting remote computer storage devices to a server so that the devices appear to be locally attached), a NAS-SAN hybrid, or other means of central / shared storage now known or later developed, or any combination thereof.
[0064] Structurally, data storage 130 may include any collection of data. By way of non-limiting example, data storage 130 may include a local database, an online database, a desktop database, a server-side database, a relational database, a hierarchical database, a network database, an object database, an object-relational database, an associative database, a concept-oriented database, an entity-attribute-value database, a multidimensional database, a semi-structured database, a star-schema database, an XML database, a file, a collection of files, a spreadsheet, and / or other means of data storage, such as magnetic media, a hard drive, other disk drives, volatile memory (e.g., RAM), non-volatile memory (e.g., ROM or Flash), and / or any combination thereof.
[0065] The server(s) 110 and / or client(s), or software modules within the server(s) 110 and / or client(s), may retrieve content from the data storage 130 using a query language such as MSSQL or MySQL. The retrieved data may be processed using a server-side scripting language such as ASP, PHP, CGI / Perl, proprietary scripting software / modules / parts, etc. The retrieved data may be analyzed to determine actions to be taken by the scripting language, including performing steps of any method disclosed herein.
[0066] The server 110 and / or the client 120 may execute one or more software modules and / or components used in connection with the present invention, which may be stored in memory on at least one of the server 110 and / or the client 120. As a non-limiting example of such software, the following paragraphs will describe in detail the software modules / components that make up the software combination. These software modules / components may include software and / or scripts that include instructions that, when executed by a microprocessor on the server 110 or the client 120, cause the microprocessor to achieve the purpose of the module / component as detailed herein. The software combination may also share information, including data and / or variables from data sources used in various algorithms executed on the server 110 and / or the client 120 in the system, between each module / component of the software combination, as necessary.
[0067] 4A shows a more detailed embodiment of an environment for a system for performing steps of the methods disclosed herein. As a non-limiting example, all of the disclosed software modules may be executed on one or more servers 110 and may include one or more user interfaces generated by the server(s) 110 and transmitted to and displayed on the client(s) 120. The user interface(s) may be configured to receive input from a user and transmit this input to the server(s) 110 for managing and executing the software 200 using data in the data storage 130 associated with the software module 200. Thus, the disclosed system may be configured to perform any or all of the steps of the methods disclosed herein.
[0068] As mentioned above, in some embodiments, the disclosed system may store approved tag data associated with a unique long-range or short-range identification tag 105 that uniquely associates the tag 105 with the disclosed system. Thus, to simplify the task of identifying a particular asset (e.g., a network or power cable) according to the disclosed embodiments, an administrator may attach or associate a short-range and / or long-range identification tag to each of the assets, such as, by way of non-limiting example, attaching a tag to each of the particular servers, cables, and / or bundles of cables (as seen in FIG. 4B).
[0069] Using the present system, one or more identification tags, each having an embedded tag identifier, may be associated with a particular asset. Descriptions of these assets may be stored in association with one or more identification tags. For illustrative purposes, FIG. 5 shows a flow chart illustrating how the server 110 may store a data record that stores a unique identifier associated with a scanned tag 105 and further generate a GUI for a user to input additional data related to the scanned tag 105 or its associated asset. The server 110 may update the data record to include the received additional data. In step 500, a user (e.g., a data center administrator) may attach a tag 105 (possibly, as described above, a self-laminating label or marker having an embedded identification tag 105 is used) to each of one or more particular assets. Once the appropriate tag 105 is attached to the appropriate asset, a user of the disclosed system may then use appropriate identification tag reader 300 hardware and configuration to read the embedded data stored in the memory of the tag 105 (e.g., the tag's unique identifier) and transmit the scanned data over network 100 to a computing device such as server 110 and / or client device 120. In some embodiments, the user may press a scan button 340 on the reader 300 to activate the long-range or short-range antenna 330 and associated circuitry for scanning.
[0070] Continuing at step 500, the computing device 110, 120 may receive the scanned data and generate a database record storing the scanned data. In some embodiments, the unique identifier of the tag 105 and / or the asset may be used as the unique identifier of the database record. In embodiments in which the reader 300 includes embedded software 310 and / or database 320, the scanned data from the tag 105 may be processed by the software 310 and stored in the embedded database 320 as an interim step not shown in FIG. 5. Data may then be selected from the embedded database 320 and transmitted over the network 100 to the computing device 110, 120, which may receive and process the scanned data and generate a database record associated with the identified tag using the unique identifier and store it in the system database 130.
[0071] In some embodiments, the antenna 330 of the reader 300 and its associated circuitry may simply read the data stored in the tag 105, possibly in response to a scan button 340 being pressed, and stream the data over the network 100 to the computing devices 110, 120, which may receive and process the scanned data, generate a database record associated with the tag 105 (possibly both identified using a unique identifier), and store the tag data in the system database 130.
[0072] Returning to FIG. 5, in step 510, the computing devices 110, 120 then generate a GUI having one or more GUI components that allow the user to enter additional details about the tag 105 or the asset to which the tag 105 is attached or near the tag 105, such as the name, associated resources, names of tagged resources, purpose of the tag or tagged resource, user comments about the tag, etc. In an embodiment including multiple computing devices, the server device 110 may transmit the GUI or a portion of the GUI over the network 100 to the client device 120 for display. In an embodiment using an antenna 330 with a long range identification tag protocol, the GUI may include a GUI component (e.g., a checkbox not shown in FIG. 6) indicating that the asset would be best identified using a particular identification tag protocol (e.g., RFID) to locate the asset.
[0073] Returning to FIG. 5, in step 520, the computing devices 110, 120 may receive user input from the generated and displayed GUI, including confirmation of the previously generated and populated data, and additional user input related to the tag data. In an embodiment including multiple computing devices, the client device 120 may then transmit the received user input data to the server device 110. In steps 520 and 530, the computing devices 110, 120 may receive the input data and store the updated data in the appropriate data records. In an embodiment using an antenna 330 utilizing a long-range identification tag protocol, and in which an appropriate GUI component is selected (e.g., a checkbox indicating the use of RFID technology is checked), the data records may be updated to include a flag indicating that the reader 300 should scan using the particular long-range identification tag protocol.
[0074] As a non-limiting example illustrated by Figures 5 and 6, a data center worker may tag a server or a bundle of cables associated with a server with a long range identification tag 105. This identification tag 105 can identify a server or a router to which multiple cables are connected, or perhaps a bundle of cables that are grouped together, as shown in Figure 4B.
[0075] Since each tag 105 is coupled to a server or cable bundle, data center personnel may use reader 300 to scan the attached tag 105, possibly by pressing scan button 340 to activate antenna 330, and potentially capture the tag's 105's unique identifier. In this example, data center personnel may then access software running on client device 120 that includes a GUI as shown in FIG. 6 (possibly generated by server 110 after generating a data record for the scanned tag 105) to verify that the unique identifier is correct and / or to update the data record with additional data, which may include, by way of non-limiting examples, the network resource to which tag 105 is attached (e.g., "Server 1"), the purpose of the network resource ("Server 1's Ethernet cable 25 (in cable bundle 10)"), and additional user notes ("This cable connects Server 1 to a router"). Once the data center personnel transmits this data, computing devices 110, 120 may update their data records to reflect the newly received data.
[0076] FIG. 7 illustrates a non-limiting embodiment in which the server 110 receives scanned data from the tags 105, selects data records from the database 130 according to the unique identifiers of the tags 105, and generates a GUI to display the selected data to the user. In step 700, the user may use the reader 300 to scan any of the individual tags 105 associated with the individual assets, possibly by pressing the scan button 340 to activate the antenna 330. The reader 300 may then receive tag data from each tag 105 as it is scanned. In an embodiment in which the reader 300 includes the embedded software 310 and / or the database 320, the reader may temporarily upload database records to the embedded database 320. In an embodiment in which the reader 300 includes the embedded software 310 and the database 320, the embedded software 310 may receive and process the scanned tag data from each tag 105 and execute database commands to select data records from the embedded database 320 that have a common unique identifier or other stored tag data. In step 710, the embedded software 310 or other instructions of the reader 300 may cause data from the matching data records to be transmitted to the computing devices 110, 120 for processing.
[0077] In embodiments in which the reader 300 streams the scanned tag data over the network 100 to the computing devices 110, 120, in step 720, the computing devices 110, 120 may receive and process the scanned tag data from each tag 105 and perform a database query to select data records from the database 130 having a common unique identifier or related data.
[0078] In step 730, computing devices 110, 120 may generate a GUI for displaying the data stored in the matching data record and display the GUI to the user. In an embodiment including multiple computing devices, server device 110 may generate the GUI and send it over network 100 to client device 120 for display.
[0079] Continuing with the above example, as seen in FIG. 8, a data center worker may scan each of the tags 105 associated with various assets within the data center, and as each tag 105 is scanned, the data center worker's client device may display details within a data record for the scanned tag 105.
[0080] 9 shows a non-limiting example, in this embodiment, a user desires to find a particular cable or other particular asset. The server generates a GUI that receives the search criteria from the user. The user then scans various assets and the scanned data is sent back to the server 110 or on-board software 310 on the reader 300. The scanned data is compared to the search criteria and a notification is sent to the user when a match is found.
[0081] In some embodiments, a user may desire to search for assets associated with a particular identification tag 105. For example, the data center software may indicate to a data center worker that a particular network cable is malfunctioning and needs to be replaced. In these embodiments, the user may indicate a desire to access the system and locate one or more assets associated with one or more particular identification tags 105. In response to this request, as seen in step 900 of FIG. 9 and in FIG. 10, the computing devices 110, 120 may generate a GUI that receives input from the user defining search criteria including one or more parameters for finding assets and their associated identification tags 105.
[0082] For example, as seen in the non-limiting example of FIG. 10, for each identification tag 105 that a user wishes to locate, the GUI may include one or more GUI components for receiving user input from the user, where the user input includes a unique identifier for the identification tag, a network resource or other asset associated with the identification tag 105, the purpose of the asset and / or network resource, the purpose of the asset / resource, any notes associated with the asset / resource, or any additional data associated with the asset stored in database 130.
[0083] In an embodiment including multiple computing devices 110, 120, the server device 110 may generate a GUI and send it over the network 100 to the client device 120 for display, and the client device 120 may receive user input and send it over the network 100 to the server device 110 for processing.
[0084] Returning to FIG. 9, in step 910, the computing device 110, 120 may receive user input from the GUI and execute database commands to select any data records that match the input search criteria from the database 130. In an embodiment in which the antenna 330 or its associated circuitry is used to apply a long-range identification tag protocol (e.g., RFID) to identify an associated asset (e.g., a server or network cable bundle associated with the cable being found in FIG. 10), the database record may include a flag indicating that the long-range identification tag protocol should first be used to locate a first asset (e.g., the network cable bundle or associated server, i.e., Server 1, in FIG. 10), and then activate the controller and its associated circuitry configured to switch from the first antenna to the second antenna 330 to apply a short-range identification tag protocol (e.g., NFC) to locate a particular cable (e.g., Ethernet cable 25 in cable bundle 10 connecting Server 1 to the router in FIG. 8).
[0085] In embodiments in which the reader 300 includes embedded software 310 and / or database 320, the computing device 110, 120 may transmit the selected data (selected identification tags 105 and their associated assets) from the database 130 over the network 100 to the reader 300 for processing by the embedded software 310 and storage in the embedded database 320. In embodiments in which the reader 300 streams the scanned tag data over the network 100 to the computing device 110, 120, the computing device 110, 120 may temporarily store the selected data from the database 130 on the computing device 110, 120.
[0086] The user may then scan each of the multiple identification tags 105 using the appropriate identification tag protocol, possibly by pressing a scan button 340 to activate the antenna 330, to locate the requested asset by the associated tag 105 or by any other search criteria indicated. In an embodiment using a long-range identification tag protocol to identify the associated asset (e.g., a server or a network cable bundle associated with the cable being found in FIG. 10), the selected data may include a database flag indicating that the reader 300 should scan using a first antenna using a long-range identification tag protocol such as RFID. In an embodiment in which the reader 300 includes embedded software 310 and database 320, the computing device 110, 120 may transmit a flag over the network to the reader 300, which may process the flag and automatically use the first antenna to apply the long-range identification tag protocol to scan the identification tag 105. In embodiments in which the reader 300 streams scanned tag data over the network 100 to the computing devices 110, 120, the computing devices 110, 120 may use a data flag to indicate that the reader 300 should scan the tag 105 using the long-range identification tag protocol.
[0087] Returning to FIG. 9, in step 920, once the user has scanned for the required identification tags 105, the reader 300 receives data from each scanned identification tag 105 and compares the received data to data stored in the embedded database 320 using the embedded software 310, or may transmit the data over the network 100 to the computing devices 110, 120 for temporary storage and comparison.
[0088] As mentioned above, the reader 300 may include components 360 built into the reader 300 for providing audio and visual notifications (e.g., audio alerts or LED signals), possibly configured by the user, such that when the scanned and received identification tag data matches a unique identifier or other search criteria from a selected data record stored in the embedded database 320 (for embodiments including embedded software and / or databases) or matches a unique identifier or other search criteria temporarily stored in the computing device 110, 120 (for embodiments in which the reader streams the scanned tag data to a computing device over a network), the device triggers the output of a notification including illumination of a custom color LED and / or custom audio alert 360. The user can then identify the long range identification tag 105 associated with the asset (e.g., the server or network cable bundle to which the desired cable belongs).
[0089] In some embodiments, the identified match may be received by the computing device 110, 120 over the network 100 from software logic on the computing device or from embedded software 310 on the reader 300. In response to receiving the identified match, the computing device 110, 120 may generate a command to generate a GUI or update a currently displayed GUI, including a GUI component that displays a notification that the most recently scanned identification tag 105 and / or asset matches one of the selected unique identifiers or other search criteria from a database record. This notification may be displayed on the GUI on the computing device 110, 120.
[0090] In embodiments that use long-range identification tags to identify associated assets, for embodiments that include embedded software 310 and / or database 320, the embedded software 310 may include a controller and associated logic for automatically switching from a first antenna 330 and associated circuitry that wirelessly receives identification tag data using a long-range identification tag protocol (e.g., RFID) to a second antenna 330 and associated circuitry that wirelessly receives identification tag data using a short-range identification tag protocol (e.g., NFC). In embodiments in which the reader 300 streams scanned tag data to a computing device over the network 100, the computing device 110, 120 may include logic to switch from an antenna using a long-range identifier protocol to an antenna using a short-range identification tag protocol after a signal is transmitted that triggers a custom alert on the reader 300.
[0091] Once the reader 300 operates using a short-range identification tag protocol, or in embodiments that use short-range identification tags to identify an associated asset (e.g., a server to be discovered or an individual cable associated with a network cable bundle), a user may scan for the desired identification tag 105 and its associated asset (e.g., a particular cable in a cable bundle and / or a particular cable connected to an associated asset such as a server).
[0092] In embodiments in which the reader 300 includes embedded software 310 and database 320, if there is no flag indicating the use of the long-range identification tag protocol or if the reader is switched from long-range to short-range identification tag protocol after finding a matching identification tag 105 using the long-range identification tag protocol, the computing device 110, 120 may automatically configure the reader 300 to scan for identification tags 105 using the short-range identification tag protocol.
[0093] In embodiments in which the reader 300 streams scanned tag data over the network 100 to the computing devices 110, 120 may not be able to identify a flag indicating the use of the long-range identification tag protocol or data logic that currently indicates that the reader 300 should now utilize the short-range identification tag protocol to scan the tag 105.
[0094] As before, and similar to FIGS. 9 and 10, when a user scans for a desired identification tag 105 (step 920), the reader 300 receives data from each of the identification tags 105 and may compare the received data to data stored in the embedded database 320 using embedded software 310 or transmit the data over the network 100 to the computing devices 110, 120 for comparison with selected data temporarily stored therein.
[0095] Then, similar to step 930 above, the reader 300 may include a component 360 built into the reader 300 for audio and visual notifications (e.g., audio alerts or LED signals), possibly configured by the user, such that the device triggers a custom color LED illumination and / or custom audio alert 360 when the scanned and received identification tag data matches a unique identifier stored in the embedded database 320 (for embodiments including embedded software and / or databases) or a unique identifier temporarily stored in the computing device 110, 120 (for embodiments in which the reader streams the scanned tag data over a network to the computing device). The user can then identify the long range identification tag 105 associated with the asset (e.g., the server or network cable bundle to which the desired cable belongs).
[0096] In some embodiments, the identified match may be received by the computing device 110, 120 over the network 100 from software logic on the computing device or from embedded software 310 on the reader. In response to receiving the identified match, the computing device 110, 120 may generate a command to generate a GUI or update a currently displayed GUI, where the GUI includes a GUI component that displays a notification indicating that the most recently scanned identification tag 105 and / or asset matches one of the selected unique identifiers from the database record. The notification may be displayed on the GUI on the computing device 110, 120.
[0097] The steps included in the embodiments shown and described in connection with Figures 1 through 10 are not limited to the illustrated embodiments and can be combined in several different orders and modified in several other embodiments. The disclosed steps, although disclosed in certain combinations in the figures, may be independent and may be arranged and combined in any order and / or with any other step or combination of steps.
[0098] Other embodiments and uses of the above invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The specification and examples therein are exemplary only, and any other embodiments or modifications that fall within the true scope of the invention are intended to be covered by the appended claims.
[0099] The Abstract accompanying this specification is provided to enable the U.S. Patent and Trademark Office and the public to quickly determine the nature and gist of the technical disclosure from cursorial inspection, and is not intended to define, determine, or limit the invention or any embodiment thereof.
Claims
1. an identification tag coupled to a label configured to be attached to the asset; a second identification tag coupled to a second label configured to be attached to a second asset; an identification tag reader comprising a controller and configured to wirelessly read identification tag data received via wireless transmission from the identification tag; 1. A system comprising: a computing device coupled to a network, the computing device comprising at least one processor for executing instructions in a memory; The system, when the instructions are executed, outputting, using a display screen of the computing device, a graphical user interface (GUI) comprising at least one graphical user interface (GUI) component, the GUI being configured to receive search criteria to be used to locate the identification tag using the GUI component; receiving the search criteria; receiving identification tag data from the identification tag reader; determining whether the identification tag data matches the search criteria; generating a notification in response to the identification tag data being determined to match the search criteria; configured to output the notification to at least one of the identification tag reader and the GUI; The identification tag reader includes: a first antenna including a long range antenna circuit configured to wirelessly receive the identification tag data using a radio frequency identification protocol; a second antenna including a near-field antenna circuit configured to wirelessly receive second identification tag data from the second identification tag using a near-field wireless communication protocol; Equipped with The system, wherein the controller is configured to switch from receiving the identification tag data using the first antenna to receiving the identification tag data using the second antenna in response to determining that at least one of the identification tag data matches the search criteria.
2. the identification tag reader further comprising a user interface device including a light emitting diode or an audio output device; 2. The system of claim 1, wherein the computing device is configured to cause the identification tag reader to generate an output at the user interface device after at least one of the identification tag data is determined to match the search criteria.
3. The system described in claim 1, wherein the first antenna is configured to receive wireless transmission broadcast communications by the identification tag in response to an inquiry signal transmitted by the identification tag reader.
Citation Information
Patent Citations
RFID system, RFID cable system, RFID cable installation method
JP2007151383A
System and method for providing real time asset visibility
US20090327102A1
Methods and apparatus to facilitate proximity detection and location tracking
US20160026837A1
Terminal device, program, and information processing device
WO2015025619A1
Integrated stationary RFID reader
WO2018165386A1
