Pet-Owner Monitoring and Location Tag

The present disclosure generally relates to dependent identification systems, and more particularly, includes a system and method to identify lost and/or unintentionally abandoned pets.

Millions of pets are owned by single people (i.e. single pet parents), and/or elderly pet parents. If people living alone have some emergency (e.g. a medical emergency, storm, etc.), that prevents their return home from work or some social gathering, nobody may be aware that their pet is alone at home. In addition, if the pet is able to escape the confines of the home, or is stolen, no one, including the pet owner, may know the pet is missing until they return home. In addition, a human dependent, such as an elderly or incapacitated person, or a child, may leave the premises or require medical treatment.

Embodiments of the present disclosure provide a system and method for checking a pet's welfare and providing identification.

In one embodiment, a dependent welfare and identification system includes a dependent tag including identifying information about a dependent. A communication processor is configured to receive the identifying information and status information regarding a condition of the dependent. The communication processor is further configured to notify at least one designee after a predetermined time period has passed without receiving at least the status information.

In an embodiment, the communication processor includes a server, and wherein the identifying information and status information about the dependent is received from a mobile communication terminal.

In an embodiment, the server is configured to communicate with a host website in which the identifying information of the dependent is registered.

In an embodiment, the dependent is a pet.

In an embodiment, the owner has a separate tag (e.g., a military tag or a card). If something happens to the owner, then first responder can use their phone to scan owners QR code which will allow them to alert backup guardians for all the pets under the owner's care.

In an embodiment, the server is further configured to provide the website with status information and/or subsequent status information updates.

In an embodiment, the communication processor is a smartphone app.

In an embodiment, the communication processor generates an alert that is wireless transmitted to the at least one designee after a predetermined time period has passed without receiving at least the status information.

In an embodiment, when the at least designee totals two or more designees, the communication processor transmits the alert to the two or more designees at the same time or in succession until one of the two or more designees acknowledges receipt of the alert.

In an embodiment, the communication processor is a smartphone or smartwatch.

In an embodiment, the pet tag includes a wireless frequency transponder to communicate with the smartphone or smartwatch.

In an embodiment, the pet tag includes a transmitter configured to output information in Bluetooth or Near Frequency Communication (NFC).

In an embodiment, the identifying information is stored on the pet tag as a scannable code.

In an embodiment, the identifying information is stored on the pet tag as a QR code or

bar code.

In an embodiment, wherein the communication processor is further configured to output a pet profile to a display in response to detecting the pet tag has been scanned by a mobile communication device; receive a check-in status periodically and update a storage with the latest status information; and generate an alert to notify the at least one designee after the predetermined time period has passed without receiving at least the status information.

In an embodiment, the communication processor is smartphone or smartwatch further configured to output a pet profile to a display in response to detecting activation of a touchscreen; receive a check-in status periodically and update a storage with the latest status information; and generate an alert to notify the at least one designee after the predetermined time period has passed without receiving at least the status information.

In an embodiment, the smartphone or smartwatch generates at least one text message or one email to the at least one designee when a predetermined period time period has elapsed without receiving an update status information.

In an embodiment, the smartphone or smartwatch generates at least one audible alert, tactile alert, or visual alert as a reminder that updated status information regarding the pet has not been received.

In an embodiment, a method of providing a pet welfare and identification includes providing a pet tag including identifying information about a pet; receiving, by a communication processor, the identifying information and a status information regarding a condition of the pet, and notifying at least one designee after a predetermined time period has passed without receiving at least the status information. The providing of identification information is wirelessly transmitted by the pet tag, or the pet tag includes scannable code that is read and received by the communication processor.

In an embodiment, a host website is notified in which the identifying information of the pet is registered with at least the status information, or an indication is provided that the status information has not been received.

In an embodiment, the host website is provided with status information and/or subsequent status information updates regarding the pet via a wireless communication device.

In an embodiment, the identification information is transmitted by the pet tag via a wireless transmitter and received by the communication processor. The pet tag transmits in Bluetooth or Near Frequency Communication (NFC).

These and other features will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings.

In the following detailed description, numerous specific details are set forth by way of examples to provide a thorough understanding of the relevant teachings. However, it should be understood that the present teachings may be practiced without such details. In other instances, well-known methods, procedures, components, and/or circuitry have been described at a relatively high level, without detail, to avoid unnecessarily obscuring aspects of the present teachings. The order of operation shown and described in the flowchart(s) are provided for illustrative purposes, and the claimed subject matter is not limited to the order and/or operations shown in the flowchart(s).

As used herein, the term “dependent” is to be interpreted broadly and may be defined as any of a pet, an elderly person, and/or a child. A dependent may also be a patient in a home, hospital, or hospice setting.

As used herein, the term “wireless frequency” is to be interpreted broadly and includes various versions of Bluetooth (e.g. Bluetooth Low energy, etc.), Near Frequency Communication (NFC), 802.11x, Wi-Fi, WiMAX, WiBro, etc., just to name a few non-limiting possible protocols.

As used herein, the term “communication processor” typically includes circuitry configured for operation and in various embodiments includes a server, proxy server, website host server, smartphone, smartwatch, tablet, phablet, smart glasses, etc. The communication processor may also be an app for a mobile communication terminal such as a tablet, smartphone, or smartwatch. The app would be loaded into a smartphone or smartwatch for execution, for example, and operated by the mobile communication terminal.

In the case where the dependent is a pet, a pet tag may be attached or embedded in a dog/cat collar, or may be a microchip that is implanted in/under a pet's skin. While it may be desirable to a transmitter or transceiver, the pet tag may also be an RFID tag, etc. It is to be understood the system and method are not limited in application to dogs and cats. In the case of a dependent person, a wristband, ankle band, arm tag/leg tag may be temporarily adhered to the skin. It is also possible to embed a microchip in a dependent person. In addition, a smartwatch could also be worn by a dependent person with an app activated for this purpose.

1 FIG. 100 105 is an overview of a pet welfare and identification system, according to an illustrated embodiment. There is shown a dependent, which may contain identifying information regarding the dependent, (and the guardian, family member, nurse, doctor, etc.). In the case where the dependent is a pet, the identifying information may include information about the pet owner, pet's veterinarian, etc.). This identification information may be accessible on a website via smartphone or an app. The pet tag may have a scannable code, such as a bar code, QR code, etc. The term “scannable code” is to be interpreted broadly and may take other forms than QR codes and bar codes.

105 Alternatively, or in addition thereto, the dependent tagmay have a transmitter or transponder, and/or be a microchip implanted in, or on a dependent's skin.

115 A scanner, which may be part of a smartphone, smartwatch, tablet, etc., may be used to scan the dependent tag when it is a scannable code such as a QR code or a bar code. Scanning the QR code may bring up a website with a list of dependents and their identifying information. The website may have registered users, but there may be an option if someone finds a dependent (such as a dog or cat) to scan the tag and notify a pet owner that they are in possession of the pet. In the case of a human dependent who is unable to speak or comprehend sufficiently to communicate, some identifying card or tag may be used for a similar purpose.

150 150 160 165 160 165 160 165 165 160 A communication processormay be part of a smartphone, smartwatch, tablet, etc. Alternatively, the communication processormay also be a network server, proxy server, etc., that communicates with the scanner device via wireless transmission, including but not in any way limited to Wi-Fi. The communication processor may be configured to check on whether the status information regarding a pet is received within a predetermined time period, and the communication processor may send out reminders to the guardian, family member, pet owner, etc., and/or may contact one or more designees/backup guardians,with an alert that the dependent status has not been received. Both the first designee/guardianand the second designee guardian, may be contacted successively with the alert. Upon receiving an acknowledgment from the first designee/guardianthe communication processor may set a timer to determine if the dependent status has been received. If dependent status is not received, the alert may be sent to a second designee/guardian. There may be more than two designees, and they may be contacted in succession or together, to see which designee responds first. For example, when the second guardian designeeacknowledges, then the dependent owner and the first designeemay receive another message (text and/or email, for example) indicating that the second designee will check on and provide the status of the dependent.

2 FIG. 2 FIG. 2 FIG. is a flowchart illustrating according to an embodiment of the present disclosure. With the foregoing overview of the example architecture, it may be helpful now to consider a high-level discussion of an example process. To that end,is a flowchart of a method of checking pet welfare and identification, consistent with an illustrative embodiment.is shown as a collection of blocks, in a logical order, which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer-executable instructions that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions may include routines, programs, objects, components, data structures, and the like that perform functions or implement abstract data types. In each process, the order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or performed in parallel to implement the process.

205 At operation, a dependent tag is provided including identifying information about a dependent. This information may be in a scannable code, such as a QR code, bar code, etc., or may be electronically stored on a dependent tag in a transmittable, such as text. As disclosed herein above, the dependent may be a human such as an elderly person, child, incapacitated person, or a pet, just to name some non-limiting examples. It is to be understood that in other embodiments, there may be an owner tag that includes the owner's information.

210 150 150 150 1 FIG. At operation, a communication processor receives the identifying information and status information regarding a condition of the dependent. The communication processor, such as shown in(element) may be a server, tablet, smartphone, smartwatch, etc., just to name some non-limiting examples. The communication processormay communicate with the pet tag via any wireless protocol, including but not in any way limited to Bluetooth, Near Frequency Communication (NFC), 802.11x, Wi-Fi, WiBro, WiMAX, etc. The communication processoris configured to track receipt of the status update including a time elapsed since the last time the status information has been received.

225 225 240 At operation, the communication processor determines whether the status information has been received within the predetermined time period. In other words, if there are approximate six-hour intervals, then after six hours have passed the communication processor as to whether the status information was provided. The status information may be provided by the dependent's guardian using, for example, an app, where they tap the touchscreen and check in with an indication that everything is okay. If the status information was received at operation, then at operationa website or storage is updated with status. In an alternative embodiment, instead of an app, the dependent's guardian may have logged into a website and provided the status information regarding the dependent.

225 230 240 235 245 With continued reference to operation, in the event that the status was not received within the predetermined time period, there is an option to send a reminder to the dependent's guardian to request that they send the information as soon as possible. The owner may provide this status information operation (), and then the website or storage is updated in operation. However, if no acknowledgment is received from the dependent's guardian, or a predetermined period has passed without an acknowledgment, then at operationat least the first designee/backup guardian is notified with a request to check on the status of the pet. If the first designee/backup guardian provides the status information (operation), the communication processor may begin counting a new time period. Alternatively, the time periods may be fixed in length (e.g., 4 hours, 6 hours) and at such intervals the communication processor will check whether the latest status information has been received. If the first designee does not respond, the communication processor may contact successive designees approximately simultaneously or successively. After updating the website or storage, the method ends until the next time period.

The updating of the website may be performed via cellular transmission, or from another wireless protocol.

3 FIG. is a flowchart illustrating the process of providing identifying information and status information regarding a dependent using a QR code, NFC chip, or both, consistent with an illustrated embodiment. In this embodiment, the flowchart refers to a pet tag. However, it is to be understood that the tag is not limited to pets, and may be a dependent tag for people (e.g., elderly, infants, incapacitated, etc.) or for animals that are not pets.

305 310 315 320 330 335 340 305 340 345 350 355 At operation, a pet tag is scanned by a user. At operation, it is determined whether the pet to which the pet tag has been scanned belongs to the user. If the pet does not belong to the user, a public view of the pet profile is loaded (operation). However, if the pet does belong to the user, the owner's view of the pet profile is loaded (operation). The user's view of the pet profile may contain more information about the pet, and possibly the user who in this case may be an owner. The user (e.g., subscriber) clicks a check-in (operation) and the system updates the check-in with a timestamp in the database (operation). It is then determined with whether a predetermined number of minutes has passed since the last check-in (operation). If not, the workflow returns to the start and may begin with operationagain. However, if at operationthere has been a sufficient amount of time (e.g., minutes) since the last check-in, the backup guardian or caretaker is notified (operation). At operation, there is a confirmation received by the backup guardian regarding the pet owner's well-being and whereabouts. At operation, the guardian claims the ownership of the pet listed on the application and the method ends. In the aforementioned illustrative example, the backup guardian, rather than the guardian, was the one confirming the well-being and whereabouts of the pet.

4 FIG. 3 FIG. 405 410 415 420 425 430 435 345 350 355 is a flowchart illustrating the process of providing identifying information and status information regarding a dependent using a tag with a check-in button, fingerprint sensor, or both, consistent with an illustrated embodiment. In this illustrative embodiment, there is a precondition that each tag is linked with a pet profile. At operation, a user/subscriber presses a check-in button on the pet tag. There may be a validation that the button is pressed by the user/subscriber (e.g. fingerprint identification, etc. (operation). The system updates the check-in with a timestamp in the database (operation). Thus, this pressing of the check-in button, which can be performed by the owner, dog sitter, dog walker provides a status about the well-being and/or whereabouts of the pet. Operations,,, andare similar to operations,, andillustrated and discussed with regard to.

5 FIG. 5 FIG. 505 505 515 505 510 511 510 512 512 513 is a flowchart illustrating the process of providing identifying information and status information regarding a dependent using a tag with Bluetooth capability, consistent with an illustrated embodiment. A precondition inis that a user/subscriber has a mobile app loaded onto their smartphone, smartwatch or other device, and a Bluetooth tag for their pet is connected and linked. At operationit is determined whether the pet is still connected to the smart device (operation). If the pet tag is still connected, then it is determined whether the smart device has been used within a predetermined period of time (e.g., minutes) (operation). However, if at operationthe pet tag is not connected to the smart device, first at operationit is determined if a predetermined time period has passed since the loss of connection was detected. At operationthe backup guardian or caretaker is notified if the determination at operationis that the predetermined time period has been reached. At operationthe backup guardian confirms with the pet owner the well-being and whereabouts of the pet (operation). Then at operationthe guardian claims the ownership of the pet on the application, and the method ends.

6 FIG. 5 FIG. 605 605 615 605 615 610 611 612 613 611 612 613 511 512 513 is a flowchart illustrating the process of providing identifying information and status information regarding a dependent using a tag with GPS capability, consistent with an illustrated embodiment. A precondition is that a user/subscriber has a mobile app loaded onto their smartphone, smartwatch or other device, and a GPS tag is linked to the pet profile. It is first determined at operationif the pet tag and the smart device are within a predetermined vicinity (e.g., the pet may be outside the house in a yard, and the user with a smart device may be inside the house, so there is a range of distance that would be considered proximate. If the determination at operationis affirmative, then it is determined if the smart device has been used within a predetermined time (e.g., minutes) (operation). If the smart device has been used, then the method goes back to the beginning for a periodic reperformance of operation. However, if at operationthe smart device has not been used within a predetermined time period, or if at operationit has been over a predetermined time period since the distance between the pet tag and the smart device grew, then operations,andare performed. The operations,, andare similar to the operations,anddiscussed regarding the flowchart shown in.

7 FIG. 5 FIG. 705 715 715 705 715 710 711 712 713 711 712 713 511 512 513 is a flowchart illustrating the process of providing identifying information and status information regarding a dependent using a tag with a smart camera, consistent with an illustrated embodiment. A precondition of this illustrative embodiment is that a user/subscriber has a mobile app loaded onto their smartphone, smartwatch or other device, and a pet tag with a smart camera is linked to the pet profile. The camera may also record and save the pet's point of view, for example, on the cloud. At operation, it is determined with a pet camera that human motion has been detected. If the human motion has been detected, then at operationit is determined whether the owner's smart device is nearby and in user. If operationis affirmative, the method reverts to operationagain. However, if the response to operationis negative, or in the case of operation, where it is determined there has been more than a predetermined period of time (e.g. minutes) since the last human motion, then operations,, andare performed. The operations,, andare similar to operations,, and, respectively as discussed herein above with regard to.

8 FIG. 5 FIG. 805 805 810 811 812 813 811 812 813 511 512 513 is a flowchart illustrating the process of providing identifying information and status information regarding a dependent using a tag with a smart camera and facial recognition, consistent with an illustrated embodiment. A precondition of this illustrative embodiment is that a user/subscriber has a mobile app loaded onto their smartphone, smartwatch or other device, and a pet tag with a smart camera is linked to the pet profile. The user/subscriber has registered their facial recognition on the app. At operationit is determined whether the per tag camera has detected the pet owner's movement nearby. The pet owner is recognized via facial recognition. If operationis affirmative, the method periodically restarts to check for the owner's motion. If at operationit is determined there has been more than a predetermined period of time (e.g. minutes) since the last detection of the pet owner's motion, then operations,, andare performed. These operations,, andare similar to operations,, and, respectively as discussed herein above with regard to.

9 FIG. 10 FIG. 905 910 915 920 930 932 935 940 1005 1015 1020 1030 1035 1040 is a flowchart illustrating the process of providing identifying information and status information regarding a dependent using an owner/guardian tag consistent with an illustrated embodiment. The tag used in the illustrative embodiment is not a pet tag, but rather an owner tag. A notification is made to the backup guardian if something happens to the pet owner so that the pet is always looked after. A precondition is that a user/subscriber gets a card/tag with a QR code, NFC tag, or both. In other words, in this illustrative embodiment, this tag is not a pet tag, but a pet-owner tag. At operation, the pet owner tag is tapped. The tap may be made by someone who found the dependent (e.g. pet). At operationit is determined if a user profile exits. If there is no profile, at operationa static information page is loaded and information can be entered and/or displayed. If a profile exits, at operationa page loads with a message and options regarding whether the card (or tag) was found, and options about the dependent and whether they are injured, sick, etc. At operation, the person who tapped the tag (the person who found the pet) is prompted to enter their name, number, question of there are other pets, and any brief message to assist with reuniting the pet with its owner. At operationthe system sends a message to the owner of the pet and a guardian with the information from the person who found the pet. Then at operationthe instructions are displayed to the finder. Alternatively, at operationthe owner and guardian may both receive a message that someone activated a tag or scanned a card regarding the pet. The message may also provide a location, as well as additional instructions for the guardian to contact the owner, who may not be well.is a flowchart illustrating the process of providing identifying information and status information regarding a pet using a lost pet workflow, consistent with an illustrated embodiment. The lost pet workflow is operational with all variations as discussed herein above. Each pet has a tag with a QR code, NFC tag, or both. The link has all the pet's information as well as the owner's information. In the case of a GPS tag, the owner can locate the pet in real-time. In the case of Bluetooth, the user/subscriber can locate the tag using a nearby smart device location. Smart devices that are within a predetermined distance of the lost pet will get an alert notifying that a lost pet is nearby. This alert will include a link to the pet's profile and to the owner, so that a nearby person can notify the owner. It is also possible for the nearby smart device to use the information and generate a message notifying the owner without any intervention by a person nearby (generated automatically). At operation, a pet (or person) finder scans a QR code that is attached to the pet. At operation, the system determines whether a profile exists and whether a privacy setting is on (operation). If there is no privacy setting, the dog profile and the contact information of the owner and a temporary caretaker are displayed. If there is a privacy setting on, the dog profile is loaded but the contact information of the owner is masked. A button may be displayed that when activated calls or sends a message to the owner, caretaker, etc. (operation). At operationthe finder can call or message the owner through the site hosting the application instead of direct contact with the owner. At operationan automated message is sent to the owner that the code for their pet was scanned at a specific location that is displayed. In this way, the owner and their pet can be reunited.

11 FIG. 11 FIG. is a list of the process of certain specifications associated with providing identifying information and status information regarding a dependent consistent with an illustrated embodiment.lists the notifications that may be made to pet owners, guardians, backup guardians, the ASPCA, or animal control, and to identify a legal custodian (a pet will) in the event the owner becomes deceased or incapacitated.

It is to be understood that all of the illustrative embodiments that refer to pets are also applicable to persons, etc. The descriptions of the various embodiments of the according to present disclosure have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

The components, operations, steps, features, objects, benefits, and advantages that have been discussed herein are merely illustrative. None of them, nor the discussions relating to them, are intended to limit the scope of protection. While various advantages have been discussed herein, it will be understood that not all embodiments necessarily include all advantages. Unless otherwise stated, all measurements, values, ratings, positions, magnitudes, sizes, and other specifications that are set forth in this specification, including in the claims that follow, are approximate, not exact. They are intended to have a reasonable range that is consistent with the functions to which they relate and with what is customary in the art to which they pertain.

Numerous other embodiments of the disclosure are also contemplated. There are also embodiments of the disclosure in which the components and/or operations are arranged and/or ordered differently than described and shown herein.

It will be understood that the terms and expressions used herein have the ordinary meaning as is accorded to such terms and expressions with respect to their corresponding respective areas of inquiry and study except where specific meanings have otherwise been set forth herein. Relational terms such as first and second and the like may be used solely to distinguish one entity or action from another without necessarily requiring or implying any such actual relationship or order between such entities or actions. The terms “comprises,” “comprising,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by “a” or “an” does not, without further constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.