Method, apparatus, and system for dynamically managing assets

Abstract

Disclosed herein are devices, methods, and systems for unlocking a tracking device attached to an asset. In one example, a method of unlocking a tracking device attached to an asset is provided. The tracking device can include an electronic tag electrically coupled to a fixed component that includes an actuation element. The method can include receiving asset information associated with the tracking device, generating and storing a secure machine-readable code in conjunction with the asset information, determining whether a received input corresponds to the stored secure machine-readable code in response to receiving a request to unlock the tracking device, and providing an indication to cause an electronic reader in electronic communication with the tracking device to trigger deactivation of the actuation element.

Description

BACKGROUND

[0001] Various methods, devices, and systems, such as paper-based techniques, can be used to track assets (e.g., baggage, packages, objects) in different environments (e.g., airports, warehouses, etc.). Such methods, devices, and systems suffer from technical challenges and limitations. Through effort, wisdom, and innovation, including the development solutions in embodiments of the present disclosure, many of these identified problems have been solved, many examples of which are described in detail herein. SUMMARY

[0002] Various embodiments described herein relate to methods, devices, and systems for dynamically managing assets.

[0003] According to various examples of the present disclosure, a method of unlocking a tracking device affixed to an asset is provided. The tracking device can include an electronic tag electrically coupled to a securing component having an actuation element. The method can include receiving asset information associated with the tracking device, generating and storing a secure machine-readable code in conjunction with the asset information, in response to receiving a request to unlock the tracking device, determining whether a received input corresponds to the stored secure machine-readable code, and providing an indication to cause an electronic reader in electronic communication with the tracking device to trigger deactivation of the actuation element.

[0004] According to various examples of the present disclosure, a method of locking a tracking device affixed to an asset is provided. The tracking device can include an electronic tag electrically coupled to a securing component having an actuation element. The method can include, in response to receiving a request to lock the tracking device, determining whether a received input corresponds to the stored secure machine-readable code, and providing an indication to cause an electronic reader in electronic communication with the tracking device to trigger activation of the actuation element.

[0005] According to various examples of the present disclosure, a device is provided. The device can include an electronic tag, a securing component configured to affix the tracking device to an asset, the securing component having an actuation element, and a display element configured to display asset information, wherein the tracking device is configured to provide a control indication that triggers deactivation of the actuation element in response to receiving an indication from an electronic reader in electronic communication with the electronic tag.

[0006] The foregoing exemplary summary, as well as other exemplary objects and / or advantages of the present disclosure and means for materializing them, are further explained in the following detailed description and in conjunction with the appended drawings. BRIEF DESCRIPTION OF DRAWINGS

[0007] The description of illustrative embodiments can be read in connection with the accompanying drawings. It is to be understood that the elements shown in the figures are not necessarily to scale and that, unless otherwise noted, certain sections of the figures can be exaggerated in scale and used for illustrative purposes only. For example, the dimensions of some of the elements in the figures can be exaggerated relative to other elements in order to more clearly demonstrate the exemplary embodiments of the present disclosure. Embodiments incorporating the teachings of the present disclosure can be implemented in the context of the following figures in which:

[0008] Figure 1 An exemplary system is shown in accordance with various embodiments of the present disclosure;

[0009] Figure 2 An exemplary apparatus is shown in accordance with various embodiments of the present disclosure;

[0010] Figure 3 An exemplary apparatus is shown in accordance with various embodiments of the present disclosure;

[0011] Figure 4 An exemplary electronic reader in electronic communication with an electronic tag is shown in accordance with various embodiments of the present disclosure;

[0012] Figure 5A is a flowchart showing exemplary operations in accordance with various embodiments of the present disclosure;

[0013] Figure 5B is a flowchart showing exemplary operations in accordance with various embodiments of the present disclosure;

[0014] Figure 6A is a flowchart showing exemplary operations in accordance with various embodiments of the present disclosure; and

[0015] Figure 6B is a flowchart showing exemplary operations in accordance with various embodiments of the present disclosure. DETAILED DESCRIPTION

[0016] Some embodiments of the present disclosure will hereinafter be described in conjunction with the appended drawings, which show certain embodiments of the disclosure, but are not intended to limit the present disclosure, wherein like numerals designate like elements throughout. In fact, the disclosure can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Throughout the disclosure, like reference numerals are used to designate like elements.

[0017] The components illustrated in the figures represent components that can or can not be present in the various embodiments of the present disclosure described herein, such that the embodiments can include fewer or additional components than those shown in the figures without departing from the scope of the present disclosure. Some components can be omitted from one or more of the figures, or lines showing components can be shown in phantom in order to make the underlying components visible.

[0018] The phrases “in exemplary embodiments,” “some embodiments,” “various embodiments,” etc., generally refer to a particular feature, structure, or characteristic that follows these phrases and may be included in at least one embodiment of this disclosure, and may be included in more than one embodiment of this disclosure (importantly, such phrases do not necessarily refer to the same embodiment).

[0019] As used herein, the terms “example” or “exemplary” mean “serving as an example, instance, or illustration.” Any specific implementation described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other specific implementations.

[0020] If the specification states that a component or feature “may,” “can,” “should,” “will,” “preferably,” “possibly,” “usually,” “optionally,” “for example,” “often,” or “may” (or other such language) be included or have that characteristic, then the specific component or feature is not necessarily included or has that characteristic. Such components or features may be optionally included in some embodiments or may be excluded.

[0021] The terms “electrically coupled” or “electronic communication” in this disclosure may refer to a circuit of two or more electronic components (e.g., but not limited to exemplary processing circuitry, communication components, input / output module memory) and / or connected via wired means (e.g., but not limited to conductive lines, system buses, wired Ethernet connections or traces) and / or wireless means (e.g., but not limited to wireless networks, electromagnetic fields, Wi-Fi, Bluetooth, Zigbee) such that data and / or information (e.g., electronic indications, signals) can be transmitted to and / or received from the electrically coupled electrical components and / or circuitry.

[0022] The term "antenna element" in this disclosure can refer to a device or apparatus (e.g., an active element) that can be configured to generate a radio frequency (RF) signal when a voltage signal is applied at the antenna element. For example, the antenna element can be configured to generate an RF signal in a high frequency (HF) band, an ultra-high frequency (UHF) band, and / or any other band. In some examples, the antenna element may also include a matching circuit, which is electrically coupled to the active element, for example, to generate the RF signal.

[0023] The terms "Radio Frequency Identification (RFID) tag" or "electronic tag" in this disclosure may refer to articles, devices, or apparatuses including, for example, integrated circuits (ICs), antenna elements, and / or substrates. In some examples, the antenna elements and ICs may be fabricated on a substrate. In some examples, the IC may be communicatively coupled to the antenna element via interconnects on the substrate. In exemplary embodiments, the IC in the electronic tag may be configured to store coded information or coded data. In some examples, the electronic tag (e.g., an RFID tag) may be configured to operate in one or more RF bands, such as, but not limited to, 3 MHz to 30 MHz (HF band (e.g., 13.56 MHz)) and / or 860 MHz to 960 MHz (UHF band). In some embodiments, the electronic tag (e.g., an RFID tag) may have a dedicated power supply (e.g., an active electronic tag) that enables the electronic tag (e.g., an RFID tag) to communicate with one or more components. In some embodiments, the exemplary electronic tag (e.g., an RFID tag) may not have a dedicated power supply (e.g., a passive electronic tag). In such implementations, the electronic tag (e.g., an RFID tag) may include a power coupler capable of inducing an electric charge when the electronic tag (e.g., the RFID tag) is within a predetermined range of an RF field. The induced charge can then be used to power the electronic tag (RFID tag) itself.

[0024] An exemplary RFID system may include one or more electronic readers (e.g., RFID readers). One or more electronic readers (e.g., RFID readers) may be configured to read one or more electronic tags (e.g., RFID tags) attached to one or more assets. Furthermore, one or more electronic readers (e.g., RFID readers) may be configured to periodically or in response to receiving a request transmit data obtained from one or more electronic tags (e.g., RFID tags) to another computing entity (e.g., a computing entity such as a central server). To facilitate the transmission of data to the other computing entity (e.g., the central server), the one or more electronic readers (e.g., RFID readers) may be communicatively coupled to the central server via a backbone network (such as, but not limited to, wireless networks, Ethernet networks, etc.). In various embodiments, the electronic reader (e.g., RFID reader) may be or include handheld devices, portable devices or mobile devices, fixed devices (e.g., fixedly attached to one or more surfaces within a given environment), or combinations thereof.

[0025] In many examples, assets such as material handling applications (e.g., luggage, parcels, packages, boxes, etc.) can be moved from one location to another. In one example, luggage might be stored at a check-in counter at an airport and transported via a facility to a second location on a through flight, where it can be collected from a baggage conveyor. In some examples, paper tags or electronic tags may be attached to assets (e.g., luggage) to provide asset information to handling equipment and agents as the asset is moved / transferred through the facility. Exemplary paper tags may include passenger names, flight information, destination information, etc. However, in many cases, paper tags and electronic tags are insufficient to provide real-time information about the asset's location. For example, such solutions may not be configured to update the information provided while the asset is being moved within the environment (e.g., via paper tags or electronic tags). Therefore, assets are often misplaced during transport / transfer and / or may not be transported correctly. By way of example, a passenger or agent may inadvertently collect the wrong asset from a pickup point (e.g., belonging to another passenger or intended for a different destination). In another example, even if the asset information displayed on the paper or electronic tag is correct, a human agent may inadvertently send a specific asset to an aircraft at the wrong destination. This can lead to operational inefficiencies, requiring additional time and resources to resend the asset within the system. In yet another example, a human agent could be responsible for verifying that the asset was collected by the correct passenger / agent. However, these efforts can be time-consuming and inefficient.

[0026] Exemplary methods, apparatuses, computer program products, and systems are provided according to various embodiments of this disclosure.

[0027] In some examples, a method is provided for unlocking a tracking device attached to an asset. The tracking device may include an electronic tag electrically coupled to a fixed component having an actuating element. The method may include: receiving asset information associated with the tracking device; generating and storing a security machine-readable code in conjunction with the asset information; determining, in response to receiving a request to unlock the tracking device, whether a received input corresponds to the stored security machine-readable code; and providing an indication to cause an electronic reader in electronic communication with the tracking device to trigger deactivation of the actuating element. In some examples, the electronic tag includes a passive radio frequency identification (RFID) tag, and the electronic reader includes an RFID reader. In some examples, according to claim 2, the passive RFID tag includes an EM4325 integrated circuit (IC) utilizing the EPC Global Class 1 Generation 2 (EPC C1G2) protocol. In some examples, according to claim 1, the tracking device further includes a display element, and the tracking device is configured to display at least a portion of the asset information via the display element. In some examples, the display element includes an electronic ink display. In some examples, the tracking device also includes a power harvesting element configured to store energy obtained from an RFID reader for operating the tracking device. In some examples, the input is provided via a mobile application running on a user computing entity. In some examples, the actuating element includes a solenoid actuator operatively coupled to a locking mechanism. In some examples, the secure machine-readable code includes a one-time password (OTP), a QR code, a password, or any other type of security code. In some examples, the method further includes transmitting the secure machine-readable code to the user computing entity after generating and storing the security code.

[0028] In another example, a method for locking a tracking device attached to an asset is provided. In some examples, the tracking device includes an electronic tag electrically coupled to a fixed component having an actuating element. In some examples, the method includes: in response to receiving a request to lock the tracking device, determining whether received input corresponds to a stored security machine-readable code; and providing an indication to trigger activation of the actuating element by an electronic reader that is electronically communicating with the tracking device. In some examples, the electronic tag includes a passive radio frequency identification (RFID) tag, and the electronic reader includes an RFID reader. In some examples, the passive RFID tag includes an EM4325 integrated circuit (IC) utilizing the EPC Global Class 1 Generation 2 (EPCC1G2) protocol. In some examples, the fixed component includes an electromagnetic lock or a digital lock.

[0029] In yet another example, an apparatus is provided. The apparatus may include: an electronic tag; a fixing component configured to attach the tracking device to an asset, the fixing component having an actuating element; and a display element configured to display asset information, wherein the tracking device is configured to provide a control indication to trigger deactivation of the actuating element in response to receiving an indication from an electronic reader in electronic communication with the electronic tag. In some examples, the electronic tag includes a passive RFID tag, and wherein the electronic reader includes an RFID reader. In some examples, the electronic reader includes a user computing entity. In some examples, the display element includes an electronic ink display. In some examples, the passive RFID tag includes an EM4325 IC utilizing the EPC C1G2 protocol. In some examples, the tracking device includes a power harvesting element configured to store energy obtained from the RFID reader for operating the tracking device. In some examples, an indication from the electronic reader is provided in response to an authentication operation performed via a mobile application executed on the user computing entity. In some examples, the actuating element includes a solenoid actuator operatively coupled to the locking mechanism. In some examples, the authentication operation includes providing a secure machine-readable code, OTP or QR code, or any type of security code. In some examples, the authentication operation is initiated by a user scanning a machine-readable code displayed via a display element.

[0030] Therefore, this disclosure provides a tracking device for dynamically managing assets within an environment to increase operational throughput in various applications.

[0031] See now Figure 1 Exemplary schematic diagrams are provided illustrating an exemplary system 100 according to various embodiments of the present disclosure. As shown, the exemplary system 100 includes a tracking device 102, one or more computing entities 106 (e.g., servers), one or more databases 104, one or more networks 105, one or more user computing entities 108, one or more electronic readers (e.g., RFID readers) 110, etc. In various examples, system 100 is operable to facilitate the identification, monitoring, and / or tracking of assets within a specific location or environment.

[0032] In various embodiments, the tracking device 102 may be or include an electronic tag (e.g., an RFID tag). In various examples, the electronic tag (e.g., an RFID tag) may be an active electronic tag (e.g., including a power harvesting unit) or a passive electronic tag. Alternatively, in some examples, the tracking device 102 may include a near-field communication (NFC) tag. In some examples, the tracking device 102 / electronic tag (e.g., an RFID tag) may include an EM4325 interface. In some examples, the tracking device 102 may include an electronic tag (e.g., an RFID tag) with an integrated barcode.

[0033] like Figure 1 As further shown, system 100 includes one or more electronic readers 110. Exemplary electronic readers 110 are operable to identify, monitor, and / or track assets within a specific location or environment. In some embodiments, tracking device 102, one or more computing entities 106, one or more databases 104, one or more electronic readers 110, and / or one or more user computing entities 108 communicate electronically with each other via one or more networks 105, enabling them to exchange data (e.g., receive and transmit data) with each other (e.g., periodically and / or in response to requests). Each component of system 100, including tracking device 102, one or more computing entities 106, one or more databases 104, one or more user computing entities 108, and / or one or more electronic readers 110 (e.g., RFID readers), can communicate with each other via the same or different wireless or wired networks 105, including, for example, wired or wireless personal area networks (PANs), local area networks (LANs), metropolitan area networks (MANs), wide area networks (WANs), cellular networks, etc. Although Figure 1 Some system components are shown as separate, independent devices, but various implementations are not limited to this particular architecture.

[0034] like Figure 1As shown, the exemplary system 100 includes one or more computing entities 106. Generally, the terms computing device, entity, device, system, and / or similar terms used interchangeably herein can refer to, for example, one or more computers, computing devices, computing entities, desktop computers, mobile phones, tablets, phablets, laptops, distributed systems, terminals, servers or server networks, blade servers, gateways, switches, processing devices, set-top boxes, relays, routers, network access points, base stations, etc., and / or any combination of devices suitable for performing the functions, operations, and / or processes described herein. Such functions, operations, and / or processes may include, for example, transmitting, receiving, operating, processing, displaying, storing, determining, generating / creating, monitoring, evaluating, comparing, and / or similar terms used interchangeably herein. In one embodiment, these functions, operations, and / or processes may be performed on data, content, information, and / or similar terms used interchangeably herein.

[0035] In some examples, computing entity 106 may also include one or more network and / or communication interfaces for communicating with various computing entities, such as by transmitting data, content, information and / or similar terms that may be used interchangeably herein, which can be transmitted, received, manipulated, processed, displayed, stored, etc.

[0036] In one embodiment, computing entity 106 may further include or communicate with a nonvolatile medium (also referred to as a nonvolatile storage device, memory, memory storage device, memory circuit, and / or similar terms used interchangeably herein). In one embodiment, the nonvolatile storage device or memory may include one or more nonvolatile storage devices or memory media as described above, such as hard disks, ROMs, PROMs, EPROMs, EEPROMs, flash memory, MMC, SD memory cards, memory sticks, CBRAMs, PRAMs, FeRAMs, RRAMs, SONOS, racetrack memory, etc. As will be appreciated, a nonvolatile storage device or memory medium may store databases, database instances, database management system entities, data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc. The terms database, database instance, database management system entity, and / or similar terms used interchangeably herein may refer to a structured collection of records or information / data stored in a computer-readable storage medium, such as via a relational database, hierarchical database, and / or web database.

[0037] In one embodiment, computing entity 106 may further include volatile media (also referred to as non-volatile storage device, memory, memory storage device, memory circuitry, and / or similar terms used interchangeably herein) or communicate with said volatile media. In one embodiment, the volatile storage device or memory may further include one or more volatile storage devices or memory media as described above, such as RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, etc. As will be appreciated, volatile storage devices or memory media can be used to store at least a portion of databases, database instances, database management system entities, data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc., executed by, for example, processing elements. Therefore, databases, database instances, database management system entities, data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, interpreted code, machine code, executable instructions, etc., can be used to control certain aspects of the operation of computing entity 106 with the help of processing elements and operating systems.

[0038] As noted, in one embodiment, computing entity 106 may also include one or more network and / or communication interfaces for communicating with various computing entities, such as by transmitting data, content, information, and / or similar terms used interchangeably herein, that can be transmitted, received, manipulated, processed, displayed, stored, etc. Such communication may be performed using wired data transmission protocols, such as Fiber Distributed Data Interface (FDDI), Digital Subscriber Line (DSL), Ethernet, Asynchronous Transfer Mode (ATM), Frame Repeater, Cable Service Interface Data Specification (DOCSIS), or any other wired transmission protocol. Similarly, computing entity 106 can be configured to communicate via a wireless external communication network using any of a variety of protocols, such as Embedded SIM (eSIM), Remote SIM Propagation (RSP), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 200 (CDMA200), CDMA200 1X (1xRTT), Wideband Code Division Multiple Access (WCDMA), Global System for Mobile Communications (GSM), Enhanced Data Rate Evolution of GSM (EDGE), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Evolved Data Optimization (EVDO), High-Speed ​​Packet Access (HSPA), High-Speed ​​Downlink Packet Access (HSDPA), IEEE 802.11 (Wi-Fi), and Wi-Fi. Direct, 802.16 (WiMAX), Ultra Wideband (UWB), IR protocol, NFC protocol, RFID protocol, IR protocol, ZigBee protocol, Z-Wave protocol, 6LoWPAN protocol, Wibree, Bluetooth protocol, Wireless Universal Serial Bus (USB) protocol and / or any other wireless protocol. Computing entity 106 may use such protocols and standards to communicate using: Border Gateway Protocol (BGP), Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), TLS / SSL / secure HTTP, Internet Message Access Protocol (IMAP), Network Time Protocol (NTP), Simple Mail Transfer Protocol (SMTP), Telnet, Transport Layer Security (TLS), Secure Sockets Layer (SSL), Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Datagram Congestion Control Protocol (DCCP), Stream Control Transfer Protocol (SCTP), Hypertext Markup Language (HTML), etc.

[0039] It should be understood that one or more components of computing entity 106 may be located remotely from other components of computing entity 106, such as in a distributed system. Furthermore, one or more of these components may be aggregated, and additional components performing the functions described herein may be included in computing entity 106. Therefore, computing entity 106 can be adapted to various needs and situations, such as including the various components described with reference to a mobile application executing on user computing entity 108, including various input / output interfaces.

[0040] like Figure 1 As shown, system 100 includes a user computing entity 108. In various embodiments, user computing entity 108 may be or include one or more mobile devices, wearable computing devices, etc. An exemplary user computing entity 108 may include an antenna, a transmitter (e.g., a radio), a receiver (e.g., a radio), and a processing element that provides signals to the transmitter and receives signals from the receiver, respectively. The signals provided to the transmitter and received from the receiver may include signaling information / data according to the air interface standard of an applicable wireless system for communication with various devices such as a computing entity (e.g., a central server), another user computing entity 108, etc. In one exemplary embodiment, the transmitter and / or receiver are configured to communicate via one or more SRC protocols. For example, the transmitter and / or receiver may be configured to transmit and / or receive information / data, transmissions, etc., from at least one of the following short-range communication protocols: Bluetooth, Bluetooth Low Energy, NFC, RFID, IR, Wi-Fi, ZigBee, Z-Wave, 6LoWPAN, and / or other short-range communication protocols. In various implementations, the antenna, transmitter, and receiver may be configured to communicate via one or more remote protocols such as GPRS, UMTS, CDMA2000, 1xRTT, WCDMA, GSM, EDGE, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, Wi-Fi Direct, WiMAX, etc. User computing entity 108 may also include one or more network and / or communication interfaces for communicating with various computing entities, such as by transmitting data, content, information, and / or similar terms used interchangeably herein, that can be transmitted, received, manipulated, processed, displayed, stored, etc.

[0041] In this regard, user computing entity 108 may be able to operate using one or more air interface standards, communication protocols, modulation types, and access types. More specifically, user computing entity 108 may operate according to any of a plurality of wireless communication standards and protocols. In one particular embodiment, user computing entity 108 may operate according to a plurality of wireless communication standards and protocols (such as GPRS, UMTS, CDMA200, 1xRTT, WCDMA, TD-SCDMA, LTE, E-UTRAN, EVDO, HSPA, HSDPA, Wi-Fi, WiMAX, UWB, IR protocol, Bluetooth protocol, USB protocol) and / or any other wireless protocol.

[0042] Through these communication standards and protocols, user computing entity 108 can communicate with various other devices using concepts such as Unstructured Supplemental Service Message / Data (USSD), Short Message Service (SMS), Multimedia Messaging Service (MMS), Dual-Tone Multi-Frequency Signaling (DTMF), and / or Subscriber Identity Module Dialer (SIM Dialer)). User computing entity 108 can also download changes, plugins, and updates to, for example, its firmware, software (e.g., including executable instructions, applications, and program modules), and operating system.

[0043] According to one implementation, the user computing entity 108 may include location determination aspects, devices, modules, functions and / or similar terms that may be used interchangeably herein, to acquire location information / data periodically, continuously or in response to certain triggers.

[0044] User computing entity 108 may also include a user interface device, which includes one or more user input / output interfaces (e.g., a display and / or speaker / speaker driver coupled to a processing element, and a touch interface, keyboard, mouse, and / or microphone coupled to a processing element). For example, the user interface may be configured to provide mobile applications, browsers, interactive user interfaces, dashboards, web pages, and / or similar terms interchangeably used herein to enable information / data display or audible presentation, and to facilitate user interaction with said applications via one or more user input interfaces. Furthermore, the user interface may include any of a plurality of devices that allow user computing entity 108 to receive or communicate with information / data, such as a keypad (hard or soft), touch display, sound / voice or motion interface, scanner, reader, or other input device. In embodiments including a keypad, the keypad may include (or cause to be displayed) conventional numbers (0-9) and associated keys (#, *) and other keys for operating user computing entity 108, and may include a full set of alphabetic keys or a set of keys that can be activated to provide a full set of alphanumeric keys. In addition to providing input, the user input interface can also be used to activate or deactivate certain functions, such as screen savers and / or sleep modes. Through these inputs, the user computing entity 108 can capture, collect, and store information / data, user interactions / inputs, etc.

[0045] User computing entity 108 may also include volatile storage devices or memories and / or non-volatile storage devices or memories, which may be embedded and / or removable. For example, non-volatile memory may be ROM, PROM, EPROM, EEPROM, flash memory, MMC, SD memory card, Memory Stick, CBRAM, PRAM, FeRAM, RRAM, SONOS, racetrack memory, etc. Volatile memory may be RAM, DRAM, SRAM, FPM DRAM, EDO DRAM, SDRAM, DDR SDRAM, DDR2 SDRAM, DDR3 SDRAM, RDRAM, RIMM, DIMM, SIMM, VRAM, cache memory, register memory, etc. Volatile and non-volatile storage devices or memories may store databases, database instances, database management system entities, information / data, applications, programs, program modules, scripts, source code, object code, bytecode, compiled code, decoded code, machine code, executable instructions, etc., to implement the functions of user computing entity 108.

[0046] like Figure 1 As shown, Figure 1Any two or more exemplary components of system 100 may be configured to communicate with each other via one or more networks 105. Network 105 may include, but is not limited to, any combination of suitable communication networks of one or more different types, such as, for example, cable networks, public networks (e.g., the Internet), private networks (e.g., Frame Relay networks), wireless networks, cellular networks, telephone networks (e.g., the Public Switched Telephone Network), or any other suitable private and / or public networks. Furthermore, network 105 may have any suitable communication range associated with it and may include, for example, a global network (e.g., the Internet), MAN, WAN, LAN, or PAN. Additionally, network 105 may include any type of medium capable of carrying network traffic, including but not limited to coaxial cable, twisted pair, optical fiber, hybrid fiber-coaxial (HFC) media, microwave terrestrial transceivers, radio frequency communication media, satellite communication media, or any combination thereof, as well as various network devices and computing platforms provided by network providers or other entities.

[0047] Although Figure 1 An exemplary system 100 is provided, but it should be noted that the scope of this disclosure is not limited to such a system. Figure 1 The example shown. In some examples, system 100 may include one or more additional and / or alternative elements, and / or may differ from those shown. Figure 1 The components shown.

[0048] See now Figure 2 An exemplary schematic diagram is provided, showing a perspective view of an exemplary tracking device 200. In various examples, the tracking device 200 may be part of a system configured to identify, monitor, and / or track assets within a specific environment (e.g., a warehouse, airport, etc.). Figure 2 As shown, the exemplary tracking device 200 includes a display element 202, an electronic tag 204 (e.g., a passive RFID tag), a power acquisition element 210, and a fixing component 208.

[0049] like Figure 2As shown, the tracking device 200 includes an electronic tag 204 (e.g., a passive RFID tag). An exemplary electronic tag 204 (e.g., an RFID tag) may be or includes an IC disposed on a semiconductor die. The electronic tag 204 may be configured to receive RF signals (e.g., energy, information) from an electronic reader (e.g., an RFID reader). For example, the electronic reader may generate an RF signal to query the electronic tag 204. In some examples, the electronic tag 204 may generate a reflected RF signal (e.g., by backscattering a portion of the reflected RF signal) in response to sensing / receiving an RF signal from the electronic reader (e.g., an RFID reader). The reflected RF signal may include data / information stored by the electronic tag 204 (e.g., encoded data / information). In some examples, the electronic reader may be configured to decode and / or demodulate the reflected RF signal containing encoded data / information. In various examples, the electronic tag 204 may be or includes an active electronic tag or a passive electronic tag. The electronic tag 204 may be or includes an EM4325 IC. The electronic tag 204 may include a configurable Serial Peripheral Interface (SPI) to facilitate communication with other components or devices. In one example, the SPI may enable the electronic tag 204 (e.g., an RFID tag) to provide information for display via the display element 202 of the tracking device 200. As described above, the electronic tag 204 (e.g., an RFID tag) may be a passive electronic tag (e.g., an RFID tag) that communicates electronically with an electronic reader, allowing the electronic reader to exchange data and / or information with the electronic tag. In some examples, the electronic tag 204 (e.g., an RFID tag) may utilize the EPC Global Class 1 Generation 2 Protocol (EPC C1G2).

[0050] In some examples, such as Figure 2 As shown, the tracking device 200 includes a power harvesting element 210, such as a capacitive element / capacitor configured to store power harvested from another device (e.g., an electronic reader) that is in electronic communication with the tracking device 200, in order to provide power to the tracking device 200 for various operations (e.g., providing power to the electronic tag 204 (e.g., an RFID tag), the fixed component 208, and / or the display element 202). Thus, as described herein, one or more components of the tracking device 200 may be powered by power harvested from another device / device (e.g., an electronic reader) with which it is in electronic communication. In other examples, the tracking device 200 may include an active electronic tag (e.g., an RFID tag) having an onboard power supply element (e.g., a replaceable or rechargeable battery).

[0051] As stated above, and as Figure 2As shown, the tracking device 200 includes a display element 202. An exemplary display element 202 may be or include electronic paper / e-paper (e.g., electronic ink, electrophoretic display, electrohydraulic display, CLEARink, etc.) or any other type of reflective panel or display. The display element 202 may be configured to display at least a portion of data / information provided (i.e., written by) an electronic tag 204 (e.g., an RFID tag) with which it communicates electronically. By way of example, the display element 202 may be configured to display information associated with an asset to which the tracking device 200 is attached. The display element 202 may be electrically coupled to the electronic tag 204 (e.g., an RFID tag) via SPI. In some examples, the electronic tag 204 (e.g., an RFID tag) may provide control indications / signals to actuate a capacitor element 205 (e.g., a supercapacitor) to write information to the display element 202 via SPI. The display element 202 may continue to store and / or display the data / information provided by the electronic tag 204 (e.g., an RFID tag) until it receives another control indication / signal.

[0052] As stated above, and as Figure 2 As shown, the tracking device 200 includes a fixing component 208. In various examples, the fixing component 208 may be removably attached or affixed to an asset (e.g., luggage, packaging, or object) to provide location information of the asset and / or other assets within a specific environment (e.g., for tracking and / or identifying exemplary assets). The fixing component 208 may be actuated (e.g., fixed, attached) and / or deactivated (e.g., released, removed) in response to a control indication / signal provided by an electronic tag 204 (e.g., via a control element or switch) electrically coupled thereto.

[0053] like Figure 2As shown, an exemplary fastening component 208 includes an actuating element 201, a fastening strap 203, and a capacitor element 205 (e.g., a supercapacitor). In some examples, as shown, the fastening strap 203 is a circular strap (e.g., a cable lock, cable tie, wire harness, etc.) configured to be removably attached to or attached to an asset (e.g., luggage). The exemplary fastening strap 203 may comprise plastic, textile, or similar materials. The fastening strap 203 may be operatively coupled to the actuating element 201 and the capacitor element 205 such that the fastening strap 203 can be securely attached to and / or detached from the asset. For example, the fastening strap 203 may include a serrated configuration similar to a cable tie or wire harness, which allows a user to mechanically attach the fastening strap 203 to the asset. However, in such examples, without providing electronic indication / signals (e.g., deactivating the actuating element 201 operatively coupled to the fastening strap 203), the user may not be able to detach or remove the fastening strap 203. Therefore, after the retaining strap 203 is mechanically attached to the asset, in some examples, control signals or indications may be needed to detach or remove the retaining strap 203 from the asset (e.g., to deactivate the actuator element 201 and capacitor element 205 so that the retaining strap 203 can be detached or removed from the asset). In some examples, a first electronic indication / signal may be needed to attach the retaining strap 203 to the asset, and a second electronic indication / signal may be needed to detach or remove the retaining strap 203 from the asset.

[0054] In some examples, the actuating element 201 may be a solenoid actuator. An exemplary solenoid actuator may be actuable to release a locking mechanism (e.g., a mechanical rod disposed within a shaft adjacent to the solenoid actuator). Thus, in response to receiving a control instruction / signal, the actuating element 201 may release the locking mechanism operatively coupled to it, allowing the tracking device 200 to be removed or detached from the asset. In some examples, the actuating element 201 may cause a switch to open in response to receiving a control instruction / signal provided by the tracking device 200 using an SPI. In other examples, the fixing member 208 may include an electromagnetic lock or a digital lock that operates to lock the tracking device 200 attached to the asset (e.g., in response to receiving a control instruction / signal).

[0055] Although Figure 2 An exemplary tracking device 200 is provided, but it should be noted that the scope of this disclosure is not limited to such a device. Figure 2 The example shown. In some examples, the tracking device 200 may include one or more additional and / or alternative elements, and / or may differ from those shown. Figure 3 The components shown.

[0056] See now Figure 3The diagram illustrates an exemplary tracking device 300. In various examples, the tracking device 300 may be part of a system configured to identify, monitor, and / or track assets within a specific location. Figure 3 As shown, the exemplary tracking device 300 includes an actuation element 301, a display 302, a switching element 303, an electronic tag 304 (e.g., an RFID tag), a charge pump 305, a matching network circuit 30, a rectifier circuit 308, and a receiving antenna 310.

[0057] In various examples, the tracking device 300 may include a fixing component that can be removably attached or affixed to an asset (e.g., luggage, packaging, or object) to provide location information of the asset and / or other assets within a specific environment (e.g., for tracking and / or identifying exemplary assets). In various examples, the fixing component may be operatively coupled to an actuating element 301 that can be actuated and / or deactivated in response to a control indication / signal provided by an electronic tag 304 (e.g., an RFID tag), for example via a control element or switching element 303 operatively coupled thereto.

[0058] like Figure 3 As shown, the tracking device 300 includes an electronic tag 304 (e.g., an RFID tag). An exemplary electronic tag 304 (e.g., an RFID tag) may be or include an IC disposed on a semiconductor die. The electronic tag 304 (e.g., an RFID tag) may be configured to receive RF signals (e.g., energy, information) from an electronic reader (e.g., an RFID reader). In various examples, the electronic tag 304 (e.g., an RFID tag) may be or include an active or passive electronic tag. The electronic tag 304 (e.g., an RFID tag) may be or include an EM4325 IC. The electronic tag 304 (e.g., an RFID tag) may include a configurable Serial Peripheral Interface (SPI) to facilitate communication with other components or devices. In one example, the SPI may enable the electronic tag 304 (e.g., an RFID tag) to provide information for display via a display element 302 of the tracking device 300. The electronic tag 304 (e.g., an RFID tag) may be a passive electronic tag (e.g., an RFID tag) that communicates electronically with an electronic reader (e.g., an RFID reader), enabling the electronic reader to exchange data and / or information with the electronic tag. In some examples, the electronic tag 304 (e.g., an RFID tag) may utilize the EPC Global Class 1 Generation 2 Protocol (EPC C1G2).

[0059] As described above, the tracking device 300 includes a receiving antenna 310 configured to exchange data / information with another device (e.g., an electronic reader (e.g., an RFID reader)) in conjunction with a matching network circuit 306. The receiving antenna 310 can be configured to receive RF signals (e.g., generated by the electronic reader). As shown, the matching network circuit 306 includes an L-network impedance circuit operable to maximize / amplify the received RF signal.

[0060] As further shown, the tracking device 300 includes a rectifier circuit 308. As illustrated, the rectifier circuit 308 includes a two-stage Dickson rectifier circuit that operates to regulate a signal (e.g., a received RF signal) into a DC output voltage signal, such that the capacitor element 307 (e.g., a supercapacitor) of the rectifier circuit 308 can store / utilize energy generated for the operation of the tracking device 300. In some examples, the capacitor element 307 can begin charging / storing energy in response to the detection of an RF signal. The capacitor element 307 can begin charging / storing energy when the voltage at the terminals of the capacitor element 307 reaches a predetermined threshold. Therefore, the receiving antenna 310, the matching network circuit 306, and the rectifier circuit 308 can be configured to harvest / receive energy to charge the capacitor element 307, thereby providing / storing power for use by various components of the tracking device 300 (e.g., actuation element 301, display element 302, electronic tag 304, etc.). Additionally, the receiving antenna 310, matching network circuit 306, and rectifier circuit 308 can generate control signals / indications to facilitate and / or control various operations of the tracking device 300.

[0061] As stated above, and as Figure 3As shown, the tracking device 300 includes a display element 302. An exemplary display element 302 may be or include electronic paper / e-paper (e.g., electronic ink, electrophoretic display, electrohydraulic display, CLEARink, etc.) or any other type of reflective panel or display. The display element 302 may be configured to display at least a portion of data / information provided (i.e., written by) an electronic tag 304 (e.g., an RFID tag) with which it communicates electronically. By way of example, the display element 302 may be configured to display information associated with an asset to which the tracking device 300 is attached. The display element 302 may be electrically coupled to the electronic tag 304 (e.g., an RFID tag) via SPI. In some examples, the electronic tag 304 (e.g., an RFID tag) may provide control indications / signals to actuate a charge pump 305 operably coupled thereto in order to provide / write information to the display element 302 via SPI. The display element 302 may continue to store and / or display the data / information provided by the electronic tag 304 (e.g., an RFID tag) until it receives another control indication / signal. For example, as an asset moves through a facility, it can be scanned at multiple fixed locations by multiple fixed electronic readers. Therefore, as the asset to which the electronic reader is attached moves through the environment, the electronic reader can provide an indication to update the asset information stored by the tracking device.

[0062] like Figure 3 As shown, the exemplary tracking device 300 includes an actuation element 301 operatively coupled to a switching element 303. In some examples, an electronic indication / signal may be provided to the actuation element 301 to release or deactivate a locking mechanism operatively coupled thereto, allowing the tracking device 300 to be removed or detached from the asset. Similarly, an electronic indication / signal may be provided to the actuation element 301 to actuate / activate a locking mechanism, preventing the tracking device 300 from being removed or detached from the asset. The actuation element 301 may be a solenoid actuator (e.g., a mechanical rod disposed within a shaft adjacent to the solenoid actuator) actuable to release the locking mechanism. In some examples, the actuation element 301 may be or include an electromagnetic lock or a digital lock.

[0063] like Figure 3 As shown, the tracking device 300 includes a switching element 303. The switching element 303 can be configured to operate in conjunction with the actuating element 301 and to release the locking mechanism in response to receiving a control instruction / signal, so as to remove or detach the tracking device 200 from the asset.

[0064] Although Figure 3 An exemplary tracking device 300 is provided, but it should be noted that the scope of this disclosure is not limited to such a device. Figure 4The example shown. In some examples, the tracking device 300 may include one or more additional and / or alternative elements, and / or may differ from those shown. Figure 4 The components shown.

[0065] See now Figure 5A A schematic diagram is provided illustrating an exemplary processing unit 400 of an exemplary electronic reader (e.g., an RFID reader) according to various embodiments of the present disclosure, which communicates electronically with an electronic tag (e.g., an RFID tag) of a tracking device. As shown, the processing unit 400 includes a processing circuit 401, a communication element 403, an antenna element 405, a memory 407, and / or other components configured to perform the various operations, programs, functions, etc., described herein.

[0066] Processor 401 can be implemented as an apparatus including one or more microprocessors having an accompanying digital signal processor, one or more processors without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements (including integrated circuits, such as, but not limited to, application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs)) or some combination thereof. Therefore, although in Figure 4 While illustrated as a single processor, in embodiments, processing circuitry 401 may include multiple processors and signal processing modules. Multiple processors may be embodied in a single electronic device or distributed across multiple electronic devices that are collectively configured to function as circuitry for an electronic reader (e.g., an RFID reader). Multiple processors may operatively communicate with each other and may be collectively configured to perform one or more functions of the circuitry for an electronic reader (e.g., an RFID reader) as described herein. In an exemplary embodiment, processing circuitry 401 may be configured to execute instructions stored in memory 407 or otherwise accessible to processing circuitry 401. When executed by processing circuitry 401, these instructions may cause the circuitry for an electronic reader (e.g., an RFID reader) to perform one or more of these functions as described herein.

[0067] Regardless of whether the processing circuitry 401 is configured by a hardware method, a firmware / software method, or a combination thereof, the processing circuitry may include an entity capable of performing operations and making corresponding configurations according to embodiments of this disclosure. Thus, for example, when the processing circuitry 401 is implemented as an ASIC, FPGA, etc., the processing circuitry 401 may include hardware specifically configured to perform one or more of the operations described herein. Additionally or alternatively, when the processing circuitry 401 is embodied as an instruction executor (such as that which can be stored in memory 407), these instructions may specifically configure the processing circuitry 401 to perform one or more algorithms and operations described herein.

[0068] Therefore, the processing circuit 401 used herein may refer to a programmable microprocessor, microcomputer, or one or more multiprocessor chips that can be configured by software instructions (application programs) to perform functions including those described in the various embodiments above. In some devices, multiple processors may be provided dedicated to wireless communication functions and one processor dedicated to running other applications. The software application may be stored in internal memory before being accessed and loaded into the processor. The processor may include sufficient internal memory to store the application software instructions. In many devices, the internal memory may be volatile memory, or non-volatile memory such as flash memory, or a combination of both. The memory may also be located within another computing resource (e.g., enabling computer-readable instructions to be downloaded via the Internet or another wired or wireless connection).

[0069] Memory 407 may include suitable logic, circuitry, and / or interfaces adapted to store a set of instructions executable by processing circuitry 401 to perform predetermined operations. Additionally or alternatively, memory 407 may be configured to store data / information (obtained from electronic tag 409). Exemplary memory implementations may include, but are not limited to, hard disks, random access memory, cache memory, read-only memory (ROM), erasable programmable read-only memory (EPROM) and electrically erasable programmable read-only memory (EEPROM), flash memory, magnetic tape cassettes, magnetic tape, disk storage devices or other magnetic storage devices, optical disc read-only memory (CD-ROM), digital versatile optical disc read-only memory (DVD-ROM), optical discs, circuitry configured to store information, or some combination thereof. In one exemplary embodiment, without departing from the scope of this disclosure, memory 407 may be integrated with processing circuitry 401 on a single chip.

[0070] Communication element 403 may include suitable logic and / or circuitry that enables it to facilitate the transmission and reception of messages and data to and from various devices. For example, communication element 403 may be communicatively coupled to a server. Examples of communication element 403 may include, but are not limited to, an antenna, an Ethernet port, a USB port, a serial port, or any other port suitable for receiving and transmitting data. Communication element 403 may transmit and receive data and / or messages according to various communication protocols, such as, but not limited to, EPC Global, DOD, I2C, TCP / IP, UDP, and 2G, 3G, 4G, or 5G communication protocols.

[0071] In some examples, communication element 403 may facilitate communication with electronic tag (e.g., RFID tag) 409. In some examples, communication element 403 may be communicatively coupled to antenna element 405. In some examples, communication element 403 may be configured to transmit / receive data via antenna element 405 using one or more of the EPC global communication standard or DOD communication standard.

[0072] The processing circuitry 401 of the electronic reader (e.g., an RFID reader) may include suitable logic and / or circuitry for reading data / information provided by the electronic tag 409. To read the data / information, the processing circuitry 401 / communication element 403 may cause the antenna element 405 to transmit an interrogation command. The processing circuitry 401 may cause the communication element 403 to modulate the interrogation command using one or more modulation techniques, such as amplitude shift keying (ASK) and phase jitter modulation (PJM). In response to the interrogation command, the processing circuitry 401 / communication element 403 may receive data / information from the electronic tag 409 (e.g., an RFID tag).

[0073] In some examples, processing circuitry 401 may include one or more of a filter, an analog-to-digital (A / D) converter, a digital-to-analog (D / A) converter, a matching circuit, an amplifier, and / or a tuner that enables communication element 403 to transmit data (e.g., interrogation commands) and receive data / information via antenna element 405 in one or more frequency bands. Processing circuitry 401 may be implemented using one or more application-specific integrated circuits (ASICs) and field-programmable gate arrays (FPGAs). The electronic reader may include noise cancellation circuitry comprising suitable logic and / or circuitry to reduce interference between signals transmitted / received by antenna element 405. In some examples, noise cancellation circuitry may include one or more filters, one or more phase shifters, etc.

[0074] See now Figure 4The present disclosure provides flowcharts of exemplary operations 500 according to various embodiments thereof. In some examples, method 500 may be comprised of various system components (e.g., but not limited to those referenced above). Figure 1 The processing circuitry 401 of the electronic reader (e.g., an RFID reader) performs the operation. In some examples, the processing circuitry may be electrically coupled to and / or electronically communicate with other circuitry, such as, but not limited to, tracking devices including electronic tags (e.g., RFID tags), memories (e.g., random access memory (RAM) for storing computer program instructions).

[0075] Exemplary method 500 begins at step / operation 501. At step / operation 501, processing circuitry (such as, but not limited to, the above-described combination)... Figure 5B The processing circuitry 401 of the electronic reader (e.g., RFID reader) activates the electronic reader (e.g., RFID reader). In some examples, the electronic reader (e.g., RFID reader) may be activated in response to receiving a control instruction / signal (e.g., from a computing entity). In various embodiments, the electronic reader (e.g., RFID reader) may be a handheld device (e.g., a user-operated device) or a fixed electronic reader that is set / attached to a surface in the environment (e.g., near a baggage carousel in an airport). An exemplary fixed electronic reader (e.g., RFID reader) may be in a dormant or latent state until it detects an asset (e.g., a tracking device including an electronic tag (e.g., RFID tag)). In some examples, an exemplary fixed electronic reader (e.g., RFID reader) may continuously scan electronic tags (e.g., per second).

[0076] Following step / operation 501, exemplary method 500 proceeds to step / operation 503. At step / operation 503, the processing circuitry establishes a connection with an asset information system (e.g., a central server), enabling the electronic reader (e.g., an RFID reader) and the asset information system to exchange data / information with each other. The asset information system may be or include computing entities, such as, but not limited to, those described above. Figure 1 The computing entity 106.

[0077] Following step / operation 503, exemplary method 500 proceeds to step / operation 505. At step / operation 505, processing circuitry determines whether a new asset has been detected. In some examples, a user (e.g., an agent) may mechanically attach the exemplary tracking device to an asset (e.g., luggage) before or after the processing circuitry determines that a new asset has been detected.

[0078] In some implementations, exemplary tracking devices may include electromagnetic locks or digital locks. In such examples, to lock the tracking device in conjunction with attaching it to an asset, a user may initiate a request to lock the tracking device (e.g., by providing input to an asset information system via a user computing entity). In some examples, in response to receiving a request to lock the tracking device, the asset management system may determine whether the received input corresponds to a stored security machine-readable code. The asset information system may then provide an instruction to cause an electronic reader that communicates electronically with the tracking device to trigger an activation actuator to lock the tracking device to the asset.

[0079] Following step / operation 505, exemplary method 500 proceeds to step / operation 507. At step / operation 507, the processing circuitry transmits asset information to the electronic tag (e.g., RFID tag) of the tracking device to write the information into its memory. For example, an electronic reader (e.g., RFID reader) may obtain (e.g., request, receive) asset information from an asset information system (e.g., a central server) and transmit an RF signal including the asset information. In one example, the asset information may describe the destination, passenger information (e.g., name, address), flight information (e.g., gate information, flight time), etc. The electronic tag (e.g., RFID tag) may be configured to decode and / or demodulate the RF signal containing encoded data / information. In some examples, the electronic reader (e.g., RFID reader) may provide control instructions to enable the SPI interface on the electronic tag (e.g., RFID tag) IC. The electronic reader (e.g., RFID reader) may then use a specific protocol to provide the asset information. For example, an electronic reader (e.g., an RFID reader) can use the EPC C1G2 protocol to transmit RF signals including asset information, which includes instructions for displaying at least a portion of the asset information via a display element of the tracking device.

[0080] Following step / operation 507, exemplary method 500 proceeds to step / operation 509. At step / operation 509, the processing circuitry verifies the actuation of the fixed component of the tracking device. For example, an electronic reader (e.g., an RFID reader) may read the input / output (I / O) pins of an electronic tag (e.g., an RFID tag) to ensure that the locking mechanism (e.g., a solenoid actuator) is connected / properly actuated. If the electronic reader (e.g., the RFID reader) detects that the locking mechanism is not properly actuated, the electronic reader (e.g., the RFID reader) may provide an indication (e.g., via a display element of the electronic reader (e.g., the RFID reader)) to alert the user (e.g., an agent).

[0081] After step / operation 509, method 500 proceeds to step / operation 511. At step / operation 511, the processing circuitry transmits an indication confirming the asset's status to the asset information system (e.g., a central server). For example, the processing circuitry may transmit an indication requesting the asset information system (e.g., the central server) to generate a security code (e.g., a machine-readable code, QR code, one-time password (OTP), dynamic PIN, etc.) associated with the asset / tracking device entry. After transmitting the indication requesting the generation of the security code, method 500 may return to step / operation 505, and the processing circuitry may restart method 500 in response to the detection of a new asset.

[0082] See now Figure 4 A flowchart illustrating exemplary operation 502 according to various embodiments of the present disclosure is provided. In some examples, method 502 may be comprised of various system components (e.g., but not limited to those referenced above). Figure 1 The processing circuitry of the computing entity 106 is executed. The computing entity 106 may be or include an asset information system (e.g., a central server). In some examples, the processing circuitry may be electrically coupled to and / or electronically communicate with other circuits, such as, but not limited to, electronic readers (e.g., those mentioned above). Figure 1 The aforementioned electronic reader.

[0083] Exemplary method 502 begins at step / operation 504. At step / operation 504, processing circuitry (such as, but not limited to, the above-described combination)... Figure 1 The processing circuitry of the computing entity 106 establishes a connection with an electronic reader (e.g., an RFID reader). For example, the processing circuitry may establish a connection in response to a request received from the electronic reader (e.g., an RFID reader), allowing the electronic reader (e.g., an RFID reader) and the processing circuitry (e.g., an asset information system) to exchange data / information with each other.

[0084] Following step / operation 504, the method proceeds to step / operation 506. At step / operation 506, the processing circuitry receives asset information from an exemplary electronic reader (e.g., an RFID reader). The processing circuitry may store the received asset information in a database (such as, but not limited to, the database described above). Figure 6AIn the database 104, as described above, in one example, asset information may describe destination, passenger information (e.g., name, address), flight information (e.g., gate information, flight time), etc. For example, the processing circuitry may receive an instruction including asset information and a request to generate a security code (e.g., machine-readable code, QR code, OTP, etc.). The processing circuitry may receive an instruction from an electronic reader (e.g., an RFID reader) that has provided / written asset information to the tracking device, and confirm that the locking mechanism of the tracking device has been properly actuated.

[0085] Following step / operation 506, method 502 proceeds to step / operation 508. At step / operation 508, the processing circuitry generates a security code (e.g., a machine-readable code, QR code, OTP, etc.). The processing circuitry may store the security code (e.g., OTP) in association with asset information (e.g., in a database).

[0086] Following step / operation 508, the method proceeds to step / operation 510. At step / operation 510, the processing circuitry transmits a security code (e.g., machine-readable code, QR code, OTP). The processing circuitry may transmit the security code to the user computing entity (such as, but not limited to, the combination of the above). Figure 4The user computing entity 108 is mentioned above. Additionally, the processing circuitry can transfer at least a portion of the stored asset information to the user computing entity. In some examples, the user can interact with the asset information system using a mobile application executed on the user computing entity. In some embodiments, various sources may provide (e.g., transmit, send) mobile applications for download and execution on the user computing entity (e.g., in response to a request to download the mobile application generated at the user computing entity). In another example, the mobile application may be a browser executed on the user computing entity. The mobile application may include computer-executable program code (e.g., a software application) that provides the functionality described herein. The mobile application is executable to enable the various functions discussed herein. Furthermore, although specifically referred to as a mobile application, it should be understood that the mobile application can be executed by any of a variety of computing entity types, such as desktop computers, laptop computers, mobile devices, wearable devices, etc. In some embodiments, step / operation 510 is performed as part of registering a user. For example, a user profile for the user may be generated / created as part of registration. However, as will be appreciated, a user profile may already exist and be stored in a user profile database; in this case, registration may simply be linked to an existing user profile. Each user profile can be identified via one or more identifiers configured to uniquely identify the user profile (e.g., participant ID, username, globally unique identifier (GUID), universally unique identifier (UUID), etc.). Therefore, as part of registering / signing a user, a mobile application (executing on the user's computing entity) can request and receive various types of information / data. For example, the mobile application (executing on the user's computing entity) can request a user identifier or username. If a user profile corresponding to the user and associated with the user identifier already exists (e.g., stored in a user profile database), the user information / data may include the user's access credentials (e.g., username, password, etc.). If a user profile corresponding to the user does not yet exist, the user information / data may include information / data identifying the user (e.g., username, date of birth, etc.), user contact information / data (e.g., electronic destination address, email address, instant messaging username, social media username, application username, telephone number associated with the user's computing entity, and / or other relevant information / data). In various implementations, a mobile application (executing on a user computing entity) (e.g., via one or more user interfaces) receives user information / data and may provide that user information / data to the computing entity (e.g., an asset management system) for generating / creating user profiles and / or storing them together with the user profiles. Asset information associated with the tracking device may be associated with and / or otherwise stored together with the user profiles.In some implementations, the computing entity may be configured to automatically and / or periodically (e.g., at predetermined times) update asset information to the user computing entity. In other implementations, the computing entity may be configured to provide information / data in response to requests / queries received from the user computing entity.

[0087] See now Figure 4 A flowchart of exemplary operation 600 according to various embodiments of the present disclosure is provided. In some examples, method 600 may be comprised of various system components (e.g., but not limited to those referenced above). Figure 1 The processing circuitry 401 of the electronic reader (e.g., an RFID reader) performs the operation. In some examples, the processing circuitry may be electrically coupled to and / or electronically communicate with other circuitry, such as, but not limited to, tracking devices including electronic tags (e.g., RFID tags), memories (e.g., random access memory (RAM) for storing computer program instructions).

[0088] Exemplary method 600 begins at step / operation 601. At step / operation 601, processing circuitry (such as, but not limited to, the above-described combination)... Figure 6B The processing circuitry 401 of the electronic reader (e.g., RFID reader) activates the electronic reader (e.g., RFID reader). In some examples, the electronic reader (e.g., RFID reader) may be activated in response to receiving a control instruction / signal (e.g., from a computing entity). Alternatively / in addition, method 600 may begin with the user retrieving assets (e.g., baggage), in some examples, with the assistance and / or cooperation of an assisting agent (e.g., airport agent) to retrieve the assets.

[0089] Following step / operation 601, exemplary method 600 proceeds to step / operation 603. At step / operation 603, the processing circuitry establishes a connection with an asset information system (e.g., a central server), enabling the electronic reader (e.g., an RFID reader) and the asset information system to exchange data / information with each other. The asset information system may be or include computational entities, such as, but not limited to, those described above. Figure 1 The computing entity 106.

[0090] Following step / operation 603, exemplary method 600 proceeds to step / operation 605. At step / operation 605, processing circuitry determines whether a new asset has been detected. For example, an electronic reader (e.g., an RFID reader) may transmit control indications / signals such as RF signals (e.g., interrogation commands) to an electronic tag (e.g., an RFID tag) / tracking device. In some examples, the tracking device may also include a barcode with asset information that can be accessed (e.g., scanned) using a computing entity, a user computing entity (e.g., via a mobile application running on a user computing entity or mobile device), etc. Thus, the detection of a new asset can be initiated by a user scanning the barcode attached to the asset to access the asset information associated with the tracking device. By way of example, a printed barcode may be attached to the asset and / or the tracking device.

[0091] Following step / operation 605, exemplary method 600 proceeds to step / operation 607. At step / operation 607, the processing circuitry obtains asset information from the tracking device / electronic tag (e.g., RFID tag). For example, in response to transmitting an RF signal (e.g., an interrogation command), an electronic reader (e.g., an RFID reader) may receive a reflected RF signal from the electronic tag (e.g., an RFID tag). The electronic reader (e.g., an RFID reader) may be configured to decode and / or demodulate the reflected RF signal containing encoded data / information (e.g., asset information). In one example, asset information may include destination, passenger information (e.g., name, address), flight information (e.g., gate information, flight time), etc.

[0092] Following step / operation 607, method 600 proceeds to step / operation 609. At step / operation 609, the processing circuitry transmits an authentication request associated with the tracking device (e.g., to an asset information system / central server). Additionally and / or alternatively, in some examples, a user (e.g., via a mobile application running on the user's computing entity) may scan a barcode attached to the asset or displayed via a display element to initiate an authentication request.

[0093] Following step / operation 609, method 600 proceeds to step / operation 611. At step / operation 611, in response to a transmission authentication request, the processing circuitry receives a security code (e.g., machine-readable code, QR code, OTP, dynamic PIN, etc.) stored in association with asset information provided by the asset information system for tracking the device. Additionally and / or alternatively, in response to an authentication request initiated, for example, via a mobile application, authentication information may be transmitted to the user computing entity (i.e., provided via a mobile application or browser). In some examples, the authentication information may include user identifier information, biometric information, etc.

[0094] Following step / operation 611, method 600 proceeds to step / operation 613. At step / operation 613, the processing circuitry determines whether the received security code matches user input. In some embodiments, step / operation 611 is performed as part of receiving / requesting user input. In various examples, the user may provide user input via a mobile application running on the user computing entity or via a browser running on the user computing entity. In some embodiments, step / operation 613 may be performed by an asset management system (e.g., a central server). For example, the asset management system may determine whether a security code provided by the user (e.g., via a mobile application or browser) matches a stored security code and transmit an indication confirming successful authentication to the processing circuitry (i.e., an electronic reader). In other embodiments, the processing circuitry (i.e., the electronic reader) may directly receive user input (e.g., via a user interface). In the event of unsuccessful authentication, the electronic reader (e.g., an RFID reader) may provide an alert to the user (e.g., via a display) or via the user computing entity (e.g., via a mobile application or browser).

[0095] Following step / operation 613, and if authentication is successful, method 600 proceeds to step / operation 615. At step / operation 615, the processing circuitry provides a control indication / signal to trigger the deactivation of the fixing element. As described above, authentication can be confirmed by transmitting the indication directly to the processing circuitry (i.e., the electronic reader) and / or via a mobile application or browser running on the user's computing entity. For example, an electronic indication / signal can be provided to an actuating element of the tracking device to release or deactivate a locking mechanism operatively coupled thereto, allowing the tracking device to be removed or detached from the asset. The actuating element can be a solenoid actuator (e.g., a mechanical rod disposed within a shaft adjacent to the solenoid actuator) that can be actuated to release the locking mechanism.

[0096] After step / operation 615, method 600 proceeds to step / operation 617. At step / operation 617, the processing circuitry transmits an indication confirming the status of the tracking device to the asset information system (e.g., a central server). For example, the processing circuitry may transmit an indication confirming the deactivation of the fixed element / tracking device. In some examples, the user computing entity may transmit the indication confirming the status of the tracking device. After transmitting the indication confirming the status of the tracking device, method 600 may return to step / operation 605, and the processing circuitry may wait for new assets to be detected (e.g., receiving a new request). In some examples, attempting to leave the environment without removing the tracking device may trigger an alarm or alert.

[0097] See now Figure 4A flowchart illustrating exemplary operation 602 according to various embodiments of the present disclosure is provided. In some examples, method 602 may be comprised of various system components (e.g., but not limited to those referenced above). Figure 1 The processing circuitry of the computing entity 106 is executed. The computing entity 106 may be or include an asset information system (e.g., a central server). In some examples, the processing circuitry may be electrically coupled to and / or electronically communicate with other circuits, such as, but not limited to, electronic readers (e.g., those mentioned above). Figure 5A The aforementioned electronic reader.

[0098] Exemplary method 602 begins at step / operation 604. At step / operation 604, processing circuitry (such as, but not limited to, the above-described combination)... Figure 5B The processing circuitry of the computing entity 106 establishes a connection with an electronic reader (e.g., an RFID reader). For example, the processing circuitry may establish a connection in response to a request received from the electronic reader (e.g., an RFID reader), allowing the electronic reader (e.g., an RFID reader) and the processing circuitry (e.g., an asset information system) to exchange data / information with each other.

[0099] After step / operation 604, method 602 proceeds to step / operation 606. At step / operation 606, the processing circuitry receives an authentication request. For example, the processing circuitry receives from an electronic reader (e.g., an RFID reader) a request for a stored security code (e.g., a machine-readable code, QR code, OTP, etc.) associated with the tracking device.

[0100] Following step / operation 604, method 602 proceeds to step / operation 608. At step / operation 608, the processing circuitry transmits the stored security code to an electronic reader (e.g., an RFID reader). In some examples, as described above, instead of transmitting the stored security code, the processing circuitry may request the user to enter a security code (e.g., via a mobile application or browser running on the user's computing entity) and determine whether the received security code matches a security code stored in association with the asset information of the tracking device.

[0101] Following step / operation 608, method 602 proceeds to step / operation 610. At step / operation 610, the processing circuitry receives an indication confirming the deactivation of the fixed element / tracking device. For example, the processing circuitry receives the indication from an electronic reader (e.g., an RFID reader) after the electronic reader (e.g., an RFID reader) provides a control instruction to deactivate the fixed element / tracking device. The processing circuitry may update stored asset information, such as by deleting asset information associated with the tracking device in anticipation of the tracking device being reused with another asset (e.g., luggage).

[0102] In some examples, Figure 6A , Figure 6B , ​ and ​ One or more programs described herein may be embodied in computer program instructions, which may be stored in the memory (such as non-transitory memory) of a system employing embodiments of this disclosure and executed by the processing unit / circuit of the system. These computer program instructions may instruct the system to operate in a particular manner, causing the instructions stored in the memory circuitry to produce an article of art whose execution implements the function specified in the flowchart steps / operations. Furthermore, the system may include one or more other circuits. Various circuits of the system may be electrically coupled to each other and / or among each other to transmit and / or receive energy, data, and / or information. In some examples, embodiments may take the form of a computer program product stored on a non-transitory computer-readable storage medium containing computer-readable program instructions (e.g., computer software). Any suitable computer-readable storage medium may be utilized, including non-transitory hard disks, CD-ROMs, flash memory, optical storage devices, or magnetic storage devices.

[0103] Those skilled in the art to which these embodiments pertain will, having benefited from the teachings presented in the foregoing description and related drawings, conceive of numerous modifications and other embodiments of the present disclosure set forth herein. Therefore, it should be understood that the present disclosure is not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and related drawings describe exemplary embodiments in the context of certain exemplary combinations of elements and / or functions, it should be understood that different combinations of elements and / or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, combinations of elements and / or functions different from those explicitly described above, as may be shown in some of the appended claims, are also contemplated. Although specific terminology is used herein, it is used only in a general and descriptive sense and not for limiting purposes.

Claims

1. A system comprising: Tracking device; An electronic reader that communicates electronically with the tracking device; Computational entities; as well as User-computable entity, The tracking device includes: Electronic tags; A fixing component, configured to attach the tracking device to the asset, the fixing component having an actuating element; and A display element configured to display asset information. The computational entity is configured as follows: Receive asset information associated with the tracking device; In response to receiving a request to generate security code, the system generates and stores secure machine-readable code based on the received asset information. The generated machine-readable code is transmitted to the user computing entity associated with the user of the asset; and The machine-readable code is transmitted to the electronic reader; The electronic reader is configured as follows: Receive machine-readable code from the user computing entity; In response to receiving a request to lock or unlock the tracking device, determine whether machine-readable code received from the user computing entity matches machine-readable code received from the computing entity; and In response to determining that machine-readable code received from the user computing entity matches machine-readable code received from the computing entity, the actuation element is deactivated. In response to determining that the machine-readable code received from the user computing entity does not match the machine-readable code received from the computing entity, the actuation element is activated.

2. The system of claim 1, wherein the electronic tag comprises a passive RFID tag, and wherein the electronic reader comprises an RFID reader.

3. The system of claim 2, wherein the passive RFID tag comprises an EM4325 integrated circuit IC utilizing the EPC Global Class 1 Generation 2 EPC C1G2 protocol.

4. The system of claim 2, wherein the tracking device includes a power acquisition element configured to store energy obtained from the RFID reader for operating the tracking device.

5. The system according to claim 1, wherein the fixing component comprises an electromagnetic lock or a digital lock.

6. The system of claim 1, wherein the display element comprises an electronic ink display.

7. The system of claim 1, wherein the asset information includes passenger information, flight information, or destination.

8. A method for unlocking a tracking device attached to an asset, the tracking device comprising an electronic tag electronically coupled to a fixed component having an actuating element, the method comprising: The computing entity receives asset information associated with the tracking device; In response to receiving a request to generate security code, the computing entity generates and stores secure machine-readable code in conjunction with the received asset information. The generated machine-readable code is transmitted by the computing entity to the user computing entity associated with the user of the asset; The computing entity transmits the machine-readable code to an electronic reader that communicates electronically with the tracking device; The electronic reader receives machine-readable code from the user computing entity; In response to receiving a request to unlock the tracking device, the electronic reader determines whether the machine-readable code received from the user computing entity matches the machine-readable code received from the computing entity. as well as In response to determining that machine-readable code received from the user computing entity matches machine-readable code received from the computing entity, the electronic reader triggers the deactivation of the actuator. The electronic reader triggers activation of the actuation element in response to determining that the machine-readable code received from the user computing entity does not match the machine-readable code received from the computing entity.

9. The method of claim 8, wherein the electronic tag comprises a passive radio frequency identification (RFID) tag, and wherein the electronic reader comprises an RFID reader.

10. The method of claim 9, wherein the passive radio frequency identification RFID tag comprises an EM4325 integrated circuit IC utilizing the EPC Global Class 1 Generation 2 EPC C1G2 protocol.

11. The method of claim 8, wherein the tracking device further includes a display element, and wherein the tracking device is configured to display at least a portion of asset information via the display element.

12. The method of claim 11, wherein the display element comprises an electronic ink display.

13. The method of claim 9, wherein the tracking device further comprises a power acquisition element configured to store energy obtained from the RFID reader for operating the tracking device.

14. The method of claim 8, wherein the secure machine-readable code comprises a one-time password (OTP), a QR code, or a pass.

15. A method for locking a tracking device attached to an asset, the tracking device comprising an electronic tag electronically coupled to a fixed component having an actuating element, the method comprising: The computing entity receives asset information associated with the tracking device; In response to receiving a request to generate secure machine-readable code, the computing entity generates and stores secure machine-readable code in conjunction with the received asset information. The generated machine-readable code is transmitted by the computing entity to the user computing entity associated with the user of the asset; The computing entity transmits the machine-readable code to an electronic reader, which communicates electronically with the tracking device and is configured to read one or more electronic tags. The electronic reader receives machine-readable code from the user computing entity; In response to receiving a request to lock the tracking device, the electronic reader determines whether the machine-readable code received from the user computing entity matches the machine-readable code received from the computing entity. as well as The electronic reader triggers activation of the actuation element in response to determining that the machine-readable code received from the user computing entity does not match the machine-readable code received from the computing entity.

16. The method of claim 15, wherein the electronic tag comprises a passive radio frequency identification (RFID) tag, and wherein the electronic reader comprises an RFID reader.

17. The method of claim 16, wherein the passive radio frequency identification RFID tag comprises an EM4325 integrated circuit IC utilizing the EPC Global Class 1 Second Generation EPC C1G2 protocol.

18. The method of claim 15, wherein the fixing component comprises an electromagnetic lock or a digital lock.

Images