Patent ID: 12223382

DETAILED DESCRIPTION

For simplicity and clarity of illustration, where considered appropriate, reference numerals may be repeated among the Figures to indicate corresponding or analogous elements. In addition, numerous specific details are set forth in order to provide a thorough understanding of the embodiment or embodiments described herein. However, it will be understood by those of ordinary skill in the art that the embodiments described herein may be practiced without these specific details. In other instances, well-known methods, procedures and components have not been described in detail so as not to obscure the embodiments described herein. It should be understood at the outset that, although exemplary embodiments are illustrated in the figures and described below, the principles of the present disclosure may be implemented using any number of techniques, whether currently known or not. The present disclosure should in no way be limited to the exemplary implementations and techniques illustrated in the drawings and described below.

Various terms used throughout the present description may be read and understood as follows, unless the context indicates otherwise: “or” as used throughout is inclusive, as though written “and/or”; singular articles and pronouns as used throughout include their plural forms, and vice versa; similarly, gendered pronouns include their counterpart pronouns so that pronouns should not be understood as limiting anything described herein to use, implementation, performance, etc. by a single gender; “exemplary” should be understood as “illustrative” or “exemplifying” and not necessarily as “preferred” over other embodiments. Further definitions for terms may be set out herein; these may apply to prior and subsequent instances of those terms, as will be understood from a reading of the present description. It will also be noted that the use of the term “a” or “an” will be understood to denote “at least one” in all instances unless explicitly stated otherwise or unless it would be understood to be obvious that it must mean “one”.

Modifications, additions, or omissions may be made to the systems, apparatuses, and methods described herein without departing from the scope of the disclosure. For example, the components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses disclosed herein may be performed by more, fewer, or other components and the methods described may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

Any module, unit, component, server, computer, terminal, engine or device exemplified herein that executes instructions may include or otherwise have access to computer readable media such as storage media, computer storage media, or data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Computer storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Examples of computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by an application, module, or both. Any such computer storage media may be part of the device or accessible or connectable thereto. Further, unless the context clearly indicates otherwise, any processor or controller set out herein may be implemented as a singular processor or as a plurality of processors. The plurality of processors may be arrayed or distributed, and any processing function referred to herein may be carried out by one or by a plurality of processors, even though a single processor may be exemplified. Any method, application or module herein described may be implemented using computer readable/executable instructions that may be stored or otherwise held by such computer readable media and executed by the one or more processors. Hereinafter, the term “controller” shall mean processor and/or controller.

Directional terms such as “top,” “bottom,” “upwards,” “downwards,” “vertically,” and “laterally” are used in the following description for the purpose of providing relative reference only, and are not intended to suggest any limitations on how any article is to be positioned during use, or to be mounted in an assembly or relative to an environment. The use of the word “a” or “an” when used herein in conjunction with the term “comprising” may mean “one,” but it is also consistent with the meaning of “one or more,” “at least one” and “one or more than one.” Any element expressed in the singular form also encompasses its plural form. Any element expressed in the plural form also encompasses its singular form. The term “plurality” as used herein means more than one, for example, two or more, three or more, four or more, and the like.

In this disclosure, the terms “comprising”, “having”, “including”, and “containing”, and grammatical variations thereof, are inclusive or open-ended and do not exclude additional, un-recited elements and/or method steps. The term “consisting essentially of” when used herein in connection with a composition, use or method, denotes that additional elements, method steps or both additional elements and method steps may be present, but that these additions do not materially affect the manner in which the recited composition, method, or use functions. The term “consisting of” when used herein in connection with a composition, use, or method, excludes the presence of additional elements and/or method steps.

In this disclosure, a “blockchain” is a tamper-evident, shared digital ledger that records transactions in a public or private peer-to-peer network of computing devices. The ledger is maintained as a growing sequential chain of cryptographic hash-linked blocks.

In this disclosure, a “node” is a computing device on a blockchain network. The computing device has a controller connected to a controller-readable medium including memory having controller readable instructions thereon.

Over the past decade, and particularly in the last few years, the use of RFID-based tags (alternatively referred to as RFID tags) for identification of pets and other animals has been growing. Some of the end-use applications include authentication of pets, identification of owners of lost pets, limited tracking of the activities of pets, and the like.

RFID-based pet identification tags rely on RFID technology that has been standardized via standards such as ISO 11784 and ISO 11785 as well as ISO 14223. However, the use of RFID technology has been limited to professional settings to ensure security, traceability, and confidentiality. Further, as noted earlier, the use of RFID tags requires specific specialized reader equipment (called an RFID reader) for reading the RFID tag. The use of RFID tags limits the potential uses of pet tags to such professional settings where a reader is readily available. With the recent introduction of wearables for pets, the integration of sensors and flexible connectivity features creates many new opportunities for services, including behavior monitoring, localization, and health monitoring.

As noted earlier, RFID is a fairly limited technology in that an RFID reader simply detects and retrieves information stored in an RFID tag. Other wireless communication standards such as Bluetooth and near-field communication (NFC), on the other hand, offer the possibility of bi-directional communications. These capabilities include card emulation and peer-to-peer (P2P) communications, enabling flexible interaction with smartphones (most of which are now Wi-Fi, Bluetooth, NFC capable) and other mobile devices.

FIG.1depicts a simplified schematic diagram of one specific embodiment of a system100that is a non-limiting example. The system100includes a multipurpose ID tag102that can be implantable, and is implanted, in a pet106. The multipurpose ID tag102is equipped to communicate via both RFID and NFC, and provides the hardware link between a pet and the rest of the system100, enabling associated stakeholders to benefit from reliable pet identification, pet registration, tag authentication, and other related functions. The multipurpose ID tag102is implemented in a variety of ways according to the embodiments disclosed herein. As noted above, each implementation aims to combine dual frequencies or technologies to provide a secondary communication technology so that traditional RFID-based operations remain unaffected while the new communication technology enables new capabilities, within the constraints of small physical size for the multipurpose ID tag102.

In designing a tag having dual communication technologies, RFID and NFC in the currently described embodiment, there is a challenge of reducing interference between RFID and NFC signaling and communication without increasing the size of the tag. At least three different embodiments of a multipurpose ID tag are disclosed herein. In one embodiment, the antennas of the two technologies (e.g., NFC and RFID in this embodiment) are combined while the digital circuits remain separate and external to the antenna. In another embodiment, the same integrated chip (IC) is used having all of the necessary circuits and antenna contained on a single semiconductor die, following the principles of system-on-a-chip (SoC) design. In yet another embodiment, the two technologies are contained within in a unique casing, such as bioglass implant.

Now referring toFIG.2, the multipurpose ID tag102in accordance with the embodiment illustrated inFIG.1is shown including a combined antenna140that is used to facilitate communication with external RFID and NFC devices. An isolation block144in electrical communication with the antenna140isolates the parts of the combined antenna140, as well as other related components from one another. While the isolation block144is shown as a physical barrier, it can be provided via electrical insulation or shielding in other embodiments. These related components include an RFID circuit block including an RFID integrated circuit (IC)152and an NFC circuit block including an NFC IC148that are isolated from one another via the isolation block144. As the combined antenna140is shared for use with both NFC and RFID frequencies, there is a need to reduce the effect and impact of these two technologies on each other's performance. In one particular configuration, the isolation block144is implemented as a passive RLC circuit—that is, an electrical circuit consisting of a resistor (R), an inductor (L), and a capacitor (C), to reduce the impact of the NFC IC148and the RFID IC152on each other. In other configurations, an intermediate node may be involved. In still other configurations, no isolation block is used. Careful management and monitoring can be performed to ensure performance within desired parameters. The combined antenna140is equipped with multiple pads, and connected to the isolation block144to optimize performance and minimize the interference between both communication technologies. A bioglass shell155encloses the combined antenna140, the NFC IC148and the RFID IC152.

FIG.3Adepicts the RFID circuit block including the RFID IC152and the corresponding portion of the combined antenna140. The RFID IC152includes a storage medium154that stores identification data in the form of an RFID unique identifier (UID). The RFID UID is stored in a publicly accessible database, as discussed herein below, and can be used to relate the multipurpose ID tag102with the pet106.FIG.3Bdepicts the NFC circuit block including the NFC IC148and the corresponding portion of the combined antenna140. The NFC IC148includes a storage medium150that stores identification data, including a unique identifier (UID), a secret key (sometimes referred to as a secret object), authorization data (such as a universal resource identifier) encrypted by the data sharing computer system110, and clear (unencrypted) recovery data in NFC Data Exchange Format (NDEF). The secret key is an asymmetric encryption key provisioned to the multipurpose ID tag102that is used to authenticate the multipurpose ID tag102.FIG.3Cshows how the RFID IC152and the NFC IC148are combined with the common antenna140used in this embodiment.

As depicted, the common antenna140includes a core156, a coil160, a first antenna pad164, a second antenna pad168and a third antenna pad172. The location of the antenna pads164,168,172along the coil160can be adjusted as later described to tune one or more parameters related to reception, signal strength, and mitigation of interference. While conventional design of NFC antennas often uses a spiraling square antenna on a PCB board, the exemplary common antenna140employs a coil160on a core156, which results in a size reduction. A coil design comparatively increases inductance in the circuit while maintaining a small size, which is desirable property in miniaturization of circuits.

The RFID IC152has a first pad176and a second pad180connected to antenna pads164and172. The NFC IC148has a first pad184and a second pad188connected to antenna pads168and172.

The RFID IC152may be implemented using the HTSICH56 transponder from NXP semiconductors. The NFC IC148may be the SL2S5002 or SL2S5102 semiconductor package from NXP semiconductors. Other integrated circuit packages such as the NTA5332 from the same manufacturer NXP semiconductors can be used for boosting performance.

Referring again toFIG.1, a tag accessory in the form of a pet collar107is secured to the pet106. The pet collar107is in communication with the multipurpose ID tag102via NFC communications, however any other suitable wireless communications technology can be employed for communication by and between the multipurpose ID tag102and the pet collar107. The NFC interface of the pet collar107is an NFC transceiver as will be detailed below, and is further capable of at least receiving data from the multipurpose ID tag102via NFC communications.

The pet collar107is shown in greater detail inFIG.5, and includes a collar band formed from two collar band portions200a,200bextending from a communications module204. A releasably securable fastener in the form of a clip208includes a first clip portion208asecured to the collar band portion200aand a second clip portion208bsecured to the collar band portion200b. The clip portions208a,208benable the distal ends of the collar band portions200a,200bto be secured together. The communications module204includes an NFC transceiver212, a Bluetooth transceiver216, a security module220, a storage medium224, a controller228, and sensors230. The NFC transceiver212is configured to communicate with the multipurpose ID tag102via NFC communications, and the Bluetooth transceiver216is configured to communicate with a mobile device via Bluetooth communications. The security module220is provisioned with a digital certificate during manufacture to authenticate the pet collar107. In addition, the security module220is provisioned with a tag key to decrypt the authorization data stored by the multipurpose ID tag102, and with a sensor data key to encrypt sensor data generated by the sensors230. The tag key and the sensor data key are provisioned during pairing of the pet collar107with the multipurpose ID tag102, which generally occurs when the multipurpose ID tag102is implanted in the pet106. The storage medium224stores identification data that includes a collar unique identification (UID), as well as controller-executable instructions that can be executed by the controller228. The controller228is in communication with the NFC transceiver212, the Bluetooth transceiver216, the security module220, the storage medium224, and the sensors230. Further, the controller228is connected to contacts in a first clip portion208aof the clip208by one or more wires232to detect when the clip208is open or closed. A second clip portion208bincludes corresponding contacts to complete a circuit when the first clip portion208ais secured to the second clip portion208b. Other types of fasteners for securing the pet tag accessory to a pet and other types of closure detection systems can be used to detect the open or closed state of the fasteners. The sensors230can include a thermometer, an accelerometer, a gyroscope, a global positioning system receiver, skin sensor, blood pressure sensor, heart rate monitor, etc.

Referring again toFIG.1, an RFID scanner109can be used to energize and read the identification data from the multipurpose ID tag102via RFID communications. The RFID scanner109can be any suitable scanner for at least reading data via RFID communications from the multipurpose ID tag102. An example of a suitable RFID scanner is a ProScan700RFID pet reader.

A mobile device108is in communication with the pet collar107via Bluetooth communications, but can be any suitable wireless communications technology. The mobile device108is a computing device that can be handheld or otherwise mobile. In this embodiment, the mobile device108is a smartphone having various communications interfaces, including cellular, Wi-Fi, Bluetooth, and NFC. The NFC interface on the handheld device108is capable of reading the multipurpose ID tag102on the pet106and authenticating it with data sharing computer system110.

In a preferred implementation, the mobile device108is a handheld electronic computing device. Non-limiting examples of handheld electronic devices include a personal digital assistant (PDA), a cellular telephone, a smartphone (e.g. iPhone™, Blackberry™, Windows™ Phone), a media player device (e.g. iPod™), and a device which combines one or more aspects or functions of the foregoing devices. In other embodiments, the devices can be any other suitable electronic devices having a suitable data communications interface to communicate via the data communications network120. The mobile device108is equipped with an application (not shown). As contemplated in this first embodiment, applications communicate with the data sharing computer system110via the data communications network120. In some embodiments, localization can be delivered via the application running on the mobile device108.

Referring now toFIG.7, various components of the mobile device108are shown, including a controller802such as, but not limited to, a microprocessor, a random access memory (RAM)804, a touch input808, a battery820, and a display814. The controller802communicate with the RAM804through an interface circuit806. Temporarily stored in the RAM804are controller-executable instructions that, when executed by the controller802, cause the controller802to provide the functionality of the mobile device108described herein. The interface circuit806also interconnects with other components including, but not limited to, one or more wireless network interfaces816, a non-volatile storage810, an input-output (I/O) interface822, a camera826, an audio codec812, and a location module in the form of a global positioning system (GPS) module815. The location module can be any type of module for determining the location of the mobile device108, including via Wi-Fi assist or triangulation, cell tower triangulation, etc. The audio codec812in turn connects to one of more microphones818and one or more speakers824. While the storage media of the mobile device108includes both the RAM804and the non-volatile storage810that are described separately, other configurations of storage media can be substituted.

The wireless network interfaces816include one or more of an NFC transceiver and a controller, a wireless LAN transceiver (e.g. Wi-Fi™ transceiver), an infrared transceiver, a Bluetooth™ transceiver, and a cellular telephony transceiver. The I/O interface822may include one or more wired power and communication interfaces such as a USB port.

The touch input808may be a keypad or keyboard, a touch panel, a multi-touch panel, a touch display or multi touch display having a software keyboard or keypad displayed thereon.

Referring again toFIG.1, as contemplated in this embodiment, the mobile device108communicates with a registration server104and a data sharing computer system110via a data communications network120. The data communications network120can be wired, wireless, or any combination thereof. In a present implementation, the data communications network120includes the Internet. In other embodiments, the data communications network can be any other suitable homogeneous or mixed network including, but not limited to, a cellular data network, Wi-Fi™, WiMax™, IEEE 802.16 (WirelessMAN), and any suitable alternative thereof. The suitable data communications interface contemplated in this embodiment between the mobile device108and the data communications network120is wireless. The interface can be an antenna, transceiver, a network adapter, or a combination thereof.

The registration server104is provisioned with the public key of each pet collar107during manufacture of the pet collars107. The public key enables authentication of the pet collar107.

The data sharing computer system110is a computing device that acts as a hub for data sharing in the system100.

Referring toFIG.6, various components of the data sharing computer system110are shown, including a controller702such as, but not limited to, a microprocessor, a storage medium704, and interface circuit706adapted to provide a means of communication between the controller702and the storage medium704. The interface circuit706is also interconnected with input and output (I/O) components such as a display714, a network adapter716, a non-volatile storage710, a printer712, and one or more additional peripherals718ato718c(individually and collectively, peripherals718). Suitable peripherals718include, but are not limited to a keyboard, a camera, a scanner, a touch panel, a joystick, an electronic mouse, touch screen, track-pad, and other input or pointing devices, and any combination thereof. In other embodiments, the interface circuit does not interconnect a printer. In other embodiments, the interface circuit706does not interconnect any peripherals. While the storage media of the data sharing computer system110includes both the RAM704and the non-volatile storage710that are described separately, other configurations of storage media can be substituted.

The storage medium704may be in the form of volatile memory or a combination of volatile and non-volatile memory, including, but not limited to, dynamic or static random access memory (RAM), read-only memory (ROM), flash memory, solid state memory and the like.

The interface circuit706includes a system bus for coupling the various computer components710,712,714,716,718to the controller702. Suitable interface circuits include, but are not limited to, Industry Standard Architecture (ISA), Micro Channel Architecture (MCA), Extended Industry Standard Architecture (EISA), VESA Local Bus (VLB), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCI-X), Accelerated Graphics Port (AGP), Peripheral Component Interconnect Express (PCIe).

The non-volatile storage710can be any suitable storage medium including, but not limited to, a hard disk drive (HDD), a solid state drive (SSD), EEPROM, CD-ROM, DVD, and any other suitable data storage element or medium. The storage medium710is readable by the controller702. Stored in the memory medium704are controller-executable instructions that, when executed by the controller702, cause the controller702to provide the functionality of the data sharing computer system110described herein.

The display714can be any suitable display including, but not limited to, a touch screen.

The network adapter716facilitates wired or wireless connections to an Ethernet, Wi-Fi™, Bluetooth™, cellular network or other suitable network, thereby enabling connection to shared or remote drives, one or more networked computer resources, other networked devices, I/O peripherals and the like. The peripheral devices108also contain complementary network adapters therein for connecting with a suitable network, and are further equipped with browser or other thin-client or rich-client software. As contemplated in this embodiment, the network adapter716comprises a wireless network interface card that allows communication with other computers through a data network such as network120. In other embodiments, the network adapter does not comprise a wireless network interface card. In other embodiments, the network adapter communicates with the network via a wired connection.

The data sharing computer system110executes controller-executable instructions software that provides an authentication service118, a validation service122, and many other services (not shown) required on a server class computing device. The authentication service118performs functions associated with ensuring that the multipurpose ID tag102is an authentic tag issued from a known entity to ensure that the information read by the mobile device108is not tampered with or otherwise fake. In addition, the authentication service118authenticates the user of the mobile device108. Once the multipurpose ID tag102and the user login credentials received from the mobile device108have been authenticated, the validation service122enforces policies that determine what permissions the user of the mobile device108has. If the user is permitted to access the data associated with the multipurpose ID tag102, the validation service122provides the data associated with the UID of the multipurpose ID tag102, such as the name of the pet, address of the owner, and the like to the mobile device108. In this embodiment, the data sharing computer system110includes a data store114for storing data received from the mobile device108and the pet collar107, and a hardware security module (HSM)112. The HSM112is a computing device that provides cryptographic functions such as safeguarding and managing digital keys, performing encryption and decryption, providing strong authentication, and other cryptographic functions. The HSM112may include specialized cryptographic chips to perform these functions more efficiently. Stored by the HSM112are an asymmetric key corresponding to the secret key of the multipurpose ID tag102. A tag key used to encrypt and decrypt the authorization data provisioned to the multipurpose ID tag102and a sensor data key used to decrypt the sensor data from the pet collar107are also stored by the HSM112.

The data store114provides storage for persistent data in the form of a database116, such as, but not limited to, data pertaining to pet records, vaccination records, pet travel history, previous owners and the like. Persistent data is often required for applications that reuse saved data across multiple sessions or invocations.

As contemplated in this first embodiment, the data store114is used to store data, and includes one or more of a database116, a blockchain115, and other storage technologies. The database116may be a traditional relational database management system (RDBMS), an object-oriented database management system (OODMS), or the like. The database116may be encrypted. Suitable RDBMSes include, but are not limited to, the Oracle server, the Microsoft SQL Server database, the DB2 server, MySQL server, and any alternative type of database such as an object-oriented database server software. In other embodiments, the blockchain115can be used to replace or augment the database116as will be detailed later.

While the data sharing computer system110is illustrated as a single physical computer, the functionality of the data sharing computer system110can be provided by two or more computing devices that are locally or globally interconnected.

The RFID scanner109as well as an NFC reader, such as is present in the pet collar107, interact with portions of the same combined antenna140to retrieve their respective data via the associated digital circuits, RFID IC152and NFC IC148.

A server124that manages one or more services associated with the multipurpose ID tag102is also shown in communication with the data communications network120. The server124is one or more computer systems that provide the service or services. In one scenario, the server124manages a database of publicly accessible data corresponding to the RFID UID stored by the multipurpose ID tag102. Using login credentials, data relating to the RFID UID can be updated to reflect a change in ownership of the pet106, a change in the address of the pet106, a change in the veterinarian of the pet106, etc. These login credentials can be stored in the data store114of the data sharing computer system110so that changes to the data stored by the server124can be effected via the data sharing computer system110.

As noted above, the custom software application includes controller-executable instructions and is installed on a mobile device such as the mobile device108. The application is executed by the controller802of the mobile device108, and works in conjunction with the operating system of the mobile device108to access the storage medium804and various hardware components including wireless network interface816to exchange data and messages with a plurality of computing devices including other mobile devices108and servers.

In some embodiments, the application contains an “Always Found Alert” wherein if someone scans a pet having the multipurpose ID tag, the owner of the pet will be notified via an alert on their application. In other embodiments, a locator feature may be provided. A GPS locator feature will be able to display the coordinates where their pet was last scanned. This may be achieved by using the GPS module on the scanning mobile device along with the information read from the multipurpose ID tag, as will be described below.

In other embodiments, every pet or animal that wears an exemplary embodiment of a pet collar as described herein can interact with other pets having a multipurpose ID tag. Owners who have lost a pet can therefore track their lost animal according to where it was last detected by the application executing on a mobile device. This interaction may take place real time. Ultra wide band (UWB) powered enforcement can be used for UWB can then provide accurate (e.g., centimeter level) tracking of pets when associated to the UWB angle of arrival Bylaw enforcement officers can verify credentials and identify lost animals via mobile device.

Digital records that the application exposes to users by scanning the pet has several advantages. When a vet or customs official scans a pet with a mobile device having the application, the vet will be able to view all relevant and necessary digital identifiers and records which may include but are not limited to: license, ownership, medical history, vaccination records, lineage and the like. Application users will be able to also verify credentials of individuals and organizations to ensure authenticity. Tamper resistant or tamper proof digital records of certifications and other records may be viewable from within the application. Pet owners may carry all necessary digital certifications, health records etc. in the application at all times, without the need to request paper documents. In addition, gamification may be incorporated into the application, to teach and encourage responsible pet ownership. Further, loyalty programs may be incorporated into the application to incentivize desired behavior and reward pet owners.

Now referring toFIG.8, the general method300of collecting and storing data in the system100ofFIG.1is show and commences with the securing of the pet collar107on the pet106(304). The pet collar is fitted around the neck of the pet106and the clip208is closed. The controller228directs a small voltage to be applied to the wires232and monitors the current along the wires232to determine when the clip208is closed. Upon closure of the clip208, the controller228detects the closure (308). The pet collar107then authenticates the multipurpose ID tag102(312). During the initial pairing of the pet collar107and the multipurpose ID tag102, the pet collar107is provisioned by the data sharing computer system110with the key required to decrypt the authentication data stored by the multipurpose ID tag102. The pet collar106queries the multipurpose ID tag102and receives an authentication code from the multipurpose ID tag102generated using the secret key. The authentication code received from the multipurpose ID tag102is authenticated using the secret key stored by the pet collar107. Upon authenticating with the multipurpose ID tag102, the status of the pet collar107is set to valid (316). That is, when the pet collar107is secured on the pet106, and detects and has authenticated the multipurpose ID tag102, the pet collar107can collect data relating to the pet106, and it is assumed that the data collected is valid for that pet106. The sensors230then collect data (320). Sensor data can include temperature, blood pressure, heart rate, steps, etc. The data collected is encrypted using the digital certificate and stored in the memory medium804of the pet collar107(324). In this manner, the collected data stored on the pet collar107is not readily accessible to unauthorized parties.

The pet collar107is then authenticated (328). When a user of the mobile device108opens the application, the application queries the pet collar107for authentication data. The pet collar107passes its digital certificate to the application executing on the mobile device108. In turn, the mobile device108sends the digital certificate to the registration server104. The registration server attempts to authenticate the pet collar107using the digital certificate, and returns a response of authorized or not authorized. If the pet collar107is authorized by the registration server104, the application sends sensor data from the pet collar107to the data sharing computer system110(332). The application queries the pet collar107for the sensor data, which is encrypted by the pet collar107, and transmits it to the data sharing computer system110. In addition, the application sends the time and location data (that is, its geolocation) determined from the GPS module815that acts as a proxy for the location of the pet collar107and thus pet106. The user of the mobile device336is then authenticated (336). The user of the mobile device108enters login credentials the first time the user uses the application. Upon the login credentials being authenticated by the authentication service118of the data sharing computer system110, the mobile device108is sent an authentication token that it uses thereafter. In order to add, edit, or read the data in the data sharing computer system110, the application on the mobile device108is authenticated to ensure that an unauthorized party does not upload untrustworthy data. The authentication token is passed to the data sharing computer system110with the encrypted sensor data to authenticate the user.

If the authentication service118authenticates the user of the mobile device108at336, the user identity is passed to the validation service122to determine the permissions of the user (340). The validation service122determines the user permissions for the particular pet106using the authentication token. In one configuration, the validation service122uses policies to determine these permissions. If the user has the appropriate permissions, the data collected by the pet collar107is then decrypted and stored in the data store114of the data sharing computer system110(344). The data can be stored in the database and/or the blockchain.

The system100enables the tracking of pets via registration of the location of the multipurpose ID tag102and/or the pet collar107. For example, multiple instances of the application may cooperatively form a network community whereby whenever a lost dog with a multipurpose ID tag and/or pet collar as described herein walks by, any participating mobile device running the application receives a ping or a packet of data that includes the location of the pet and a time stamp. This information is then recorded in a storage on the network (e.g., by the data sharing computer system110) that records the location and is available to help the owner with locating the missing pet. If the pet collar107is removed from the pet106, the system100can help register the last recorded location.

Any mobile device108can connect to the multipurpose ID tag and retrieve the recovery data to report the found pet. If the mobile device108is within Bluetooth range and has the application installed, the pet collar107can send the recovery data via Bluetooth to the application on the mobile device108. The application, in turn, can then display the recovery data, enabling reporting of the found pet. Also, if the mobile device108is within range of NFC communications, the multipurpose ID tag102or the pet collar107can send an NDEF-formatted message with the recovery data.

FIG.9shows the general method400of registering removal of the pet collar107used by the system100. The method400commences with the detection of the opening of the clip208(404). When the clip208is opened, it is assumed that the pet collar107is removed from the pet106. Upon opening of the clip208of the pet collar107, the controller228of the pet collar107detects a termination of a current flowing through the wires232and determines that the pet collar107has been opened and is no longer reliably on the pet106. The pet collar107then notifies the application on the mobile device108that the pet collar107is no longer secured to the pet106(408). This notification is sent via Bluetooth. In addition, the pet collar107transmits its UID and any previously untransmitted collected data to the mobile device108(412). The UID is in plain text and the previously untransmitted collected data is encrypted using the sensor data key so that the data sharing computer system110can authenticate the communicated data. Upon being notified of the removal of the pet collar107from the pet106, the application on the mobile device108transmits a notification of the event, the UID of the pet collar107, the encrypted sensor data received from the pet collar107, and the application's authentication token to the data sharing computer system110(416). In addition, the application sends the time and the current location information received from the GPS module815. This time and location serves as the last confirmed time and location of the pet collar107and thus the pet106.

The pet collar107and the user's authentication token are then authenticated (420). The authentication service118of the data sharing computer system110authenticates the application's authentication token and the pet collar107using the UID passed and the corresponding sensor data key it has stored in the HSM112. Upon authenticating the pet collar107and the application's authentication token, the data for the event is stored in the data store114(424). The event data, together with the time and location data, and the decrypted sensor data, are stored in the data store114. The data sharing computer system110then sends a notification of the collar opening to one or more interested parties registered for the pet collar107. That is, while it may not be the pet owner that is proximal to the pet when the pet collar107is removed and the event is registered, the pet owner can be notified that the pet collar107has been removed, where, and when.

In an alternative embodiment, removal of the pet collar107from the pet can be determined by detecting an absence of the multipurpose ID tag102(that is, no longer detecting a presence of the multipurpose ID tag102), via a skin sensor, or another suitable sensor.

As the data is collected from the pet collar107and the mobile device108, the data registered by the data sharing computer system110can be shared with third parties, assuming that the user has the appropriate permissions.

FIG.10shows the general method500of sharing data using the system100. In order to share data, a user authenticates (logs in) in the application on the mobile device108(504). The login credentials are sent to the data sharing computer system110and are authenticated by the authentication service118, which generates an authentication token and sends it back to the mobile device108. Upon authenticating, the application requests a list of shareable data from the data sharing computer system110(508). The data sharing computer system110uses the authentication token passed with the request by the mobile device108to determine the data for which the user has sharing permissions and sends a list back to the mobile device108. The user then selects the data that is to be shared and the third party with which to share the data (512). The data sharing computer system110then registers the permissions granted to the third party for the particular data (such as the data for a particular pet). The data sharing computer system110then notifies the third party of the new data access permissions (520). This can be done in any sort of suitable manner, such as via an email, an in-app notification, etc. The third party can then access the data through the data sharing computer system (524).

FIG.11shows a system600that is similar to the system ofFIG.1except that a pet collar is not employed. Instead, the mobile device108communicates directly with a multipurpose ID tag602via NFC. The multipurpose ID tag602is the same as or very similar to the multipurpose ID tag102of the system100ofFIG.1. As will be appreciated, due to the range of RFID communications, the mobile device108would likely need to be held closer to the pet106than would otherwise be required where the pet collar107is used.

In operation, the application, when executed on a suitable mobile device, allows interaction with a multipurpose ID tag102implanted in any pet. A mobile device with the application will be able to communicate with the multipurpose ID tag102directly without hardware that is not typically found in such mobile devices, which empowers anyone to identify any animal or at least determine how to report the pet as found and identify the pet in a manner that will be understood by the registrar of pets or another authorized party.

FIG.12shows the general method900of collecting and storing data in the system ofFIG.11. The method900commences with the mobile device108authenticating with the multipurpose ID tag602(904). The mobile device108, when the application is being paired with the multipurpose ID tag602, receives the UID and the key required to decrypt the authentication data stored by the multipurpose ID tag102that it then uses thereafter to authenticate the multipurpose ID tag602. Upon authenticating with the multipurpose ID tag602, the multipurpose ID tag602provides at least its previously untransferred data to the mobile device108(908). Any data that the multipurpose ID tag602has collected since last transmitting data to the mobile device108is transmitted to the mobile device108. This data can include any log data captured by the multipurpose ID tag602. The mobile device108then transmits the previously untransferred data from the multipurpose ID tag602to the data sharing computer system110together with the authentication token previously received from the data sharing computer system110(912). The mobile device108can also share the time and the location of the mobile device108as a proxy for the location of the multipurpose ID tag602. Upon receiving the data, the authentication service118authenticates the authentication toke of the mobile device108and the multipurpose ID tag602(916). Once authenticated, the validation service122determines what permissions the user associated with the authentication token has with respect to the multipurpose ID tag602(924). If the user has permission to submit data from the multipurpose ID tag602, then the data sharing computer system110stores the received data in the data store114(928).

FIG.13shows a multipurpose ID tag1000employing a system-on-a-chip design in accordance with another embodiment, wherein a physical combination of dual technology (RFID and NFC) is implemented inside the same integrated chip on the same silicon or other semiconductor die. The general principles of combining two physical circuits previously configured on separate IC packages on a single chip are known. Many systems-on-a-chip (SoCs) operate on the same principle. Other factors remaining the same, integrating separate circuits onto the same die typically leads to lower cost, smaller footprint on a circuit board and better performance. However, combining circuits on the same SoC requires a new integrated circuit design and a new silicon die.

NFC is a specialized subset within the family of RFID technologies. The combination of NFC and RFID technologies therefore requires careful interference management so as to reduce the impact on performance utilizing a shared frequency. Due to size constraints, physical proximity of antennas and other components cannot be avoided. In the depicted embodiment, the frequency range used is the low frequency (LF) RFID range of 125 KHz to 134.2 KHz. The multipurpose ID tag1000has a glass or bioglass shell1004enclosing a common antenna1008connected to a single physical integrated chip (IC)1012. Internally, the same physical IC1012has individual implementations of an RFID IC1016and a NFC IC1020.

When the dual technology (e.g. RFID and NFC) is combined inside the same integrated chip (IC), the circuit and firmware associated with the two technologies, including their analog antenna design is implemented on the same piece of silicon die.

In another embodiment, the solution fora physical combination of dual communication technologies (RFID and NFC) may be provided by combining two physical circuits in a unique casing, such as a bioglass implant. As shown inFIG.14, two components1104and1108corresponding to the two technologies (e.g., RFID and NFC) are coupled together to form a multipurpose ID tag1100, each with its own separate antenna and separate IC may be used for each technology.

FIG.15shows a system1200in accordance with yet another embodiment that is similar to that ofFIG.1, wherein a conventional ID tag1204is implanted in a pet106. A pet collar1208includes an RFID reader for reading identification data from the conventional ID tag1204, and a Bluetooth or other suitable wireless communication standard transceiver for communicating the identification data to a mobile device108.

FIG.16shows the pet collar1208in greater detail. Elements very similar to or the same as the corresponding component in the pet collar107shown inFIG.5are numbered accordingly and are not described again. Instead of including an NFC transceiver, the communications module1304of the pet collar1208includes an RFID reader1308that is configured to read data from the conventional RFID-based ID tag1204.

In alternate embodiments, a subset of the data store may be implemented as part of wider system employing blockchain technology. Specifically, a blockchain and optionally a relational database and other data management solutions can be used.

Blockchain transactions work via consensus. Blockchain technology maintains a reliable record of transactions by means of collective participation and consensus among participants. Blockchain has often been understood and described as a distributed ledger technology (DLT), jointly maintained by multiple networked devices called nodes. Blockchain can thus be thought of as a distributed database system. The records are tamper-evident, accessible to application participants, and cannot be changed without consensus which helps build trust and confidence.

Both public and private blockchains are decentralized peer-to-peer networks, where each participant or node maintains a replica of a shared append-only ledger of digitally signed transactions; and provide certain guarantees on the immutability of the ledger, even when some participants are faulty or malicious.

A private blockchain is generally a permissioned network so that there are restrictions on who is allowed to participate in the network, and what type of transactions. Participants need to obtain an invitation or permission to join. The access control mechanism may vary so that existing participants could decide future entrants; a regulatory authority or the owner or administrator of the blockchain may issue licenses for participation; or a consortium could make the decisions. Once an entity has joined the network, the entrant will play a role in maintaining the blockchain in a decentralized manner.

Information such as medical records, breed information, certifications, ownership information on a private blockchain that would be accessible to trusted stakeholders. This will facilitate trust, transparency, accuracy and improve efficiency across borders and between stakeholders.

Current microchip databases operate individual siloed databases and include simple relational data models such as pet chip number, owner name and contact address. The database operator is under no obligation to disclose its data or operation. Using the multipurpose ID tag and/or pet collar described above can enable a central system for aggregation and management of all data related to the pet.

The owner of a pet can establish a geofence for the location of the pet so that an alert is generated and delivered to the owner when the pet is detected in a location outside the geofence.

In the depicted embodiment inFIG.1, the blockchain115can be a private blockchain with permissions to create a data store that can be accessed by key stakeholders such as government, vets, shelters and breeders. While an authority may administer and maintain the ledger in blockchain115, all parties will have access to the data and assume responsibility for entering accurate information and keeping records current. Storing important information such as lineage, medical history, license, ownership, travel history on a private blockchain has several benefits including immutability, privacy, security and transparency.

Linking the information stored in the database directly to a microchip ensures that such critical data follows the animal for the entirety of its life rather than depending on a wearable device.

The blockchain115may thus provide a detailed and trusted animal identification that encompasses all aspects of a pet's life. For example, when an animal needs to cross a border, a customs official can scan the animal's multipurpose ID tag with a mobile device and know with certainty that the records and documents were inputted directly from trusted parties to facilitate safer and more efficient travel.

FIGS.4A and4Bdepict two alterative implementations of the common antenna140design providing both RFID and NFD portions by varying the location at which pads are formed.

As shown inFIG.4A, antenna140has core156with the coil160wound around the core156. The coil160is made up electrically conductive material and is apportioned into a first NFC portion192and a second RFID portion196implemented on the same antenna140. The antenna pads are formed along the core156. The core156in this embodiment is a ferrite core. InFIG.4A, the NFC portion192is shorter than its counterpart in the embodiment ofFIG.4B. Consequently RFID portion196is longerFIG.4Athat its counterpart in the embodiment ofFIG.4B. In the implementations shown in bothFIGS.4A and4B, the components are encased in a shell197of bioglass or another suitable material.

The arrangement of the pads, particularly the common pad, along length of the coil is used to apportion the antenna between the first NFC portion192and a second RFID portion198.

In addition to the lengths of the portions192,198, the winding turns of the coil160may be different (denser or more sparse) so that more or less turns are accommodated per unit length in the individual portions. As depicted, RFID which uses a lower frequency (f), requires higher inductance and thus a higher number of turns than NFC. Accordingly, a greater proportion of the antenna will be used for RFID signals.

Many other applications are possible with tags exemplary of the present disclosure. Some pet doors can be programmed to be activated by the microchips of specific animals, allowing only certain animals to use the door.

The demonstrated miniaturization of circuits with dual technologies (NFC and RFID, and/or others) enables incorporation of sensors and battery boosting inventions. Other applications involving—booting the tag signal (e.g., nano-batteries) can be implemented. Temperature sensors that operated via external NFC field on collar or other accessories are also possible.

It is contemplated that any part of any aspect or embodiment discussed in this specification may be implemented or combined with any part of any other aspect or embodiment discussed in this specification. While particular embodiments have been described in the foregoing, it is to be understood that other embodiments are possible and are intended to be included herein. It will be clear to any person skilled in the art that modification of and adjustment to the foregoing embodiments, not shown, is possible.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as is commonly understood by one of ordinary skill in the art to which this invention belongs. In addition, any citation of references herein is not to be construed nor considered as an admission that such references are prior art to the present invention.

The scope of the claims should not be limited by the example embodiments set forth herein, but should be given the broadest interpretation consistent with the description as a whole.