System and method for electronic transactions in communication with external pet-taking system

Abstract

The invention discloses a computer-implemented method for dynamically managing electronic transactions of pet adoption data. The method comprises the following steps: receiving pet selection; sending confirmation information indicating that the pet is adopted; determining whether at least one pet owner file corresponding to the at least one user record exists in the data storage or not; in response to determining that the at least one pet owner file does not exist in the data storage, creating a new pet owner file based on the at least one user record; determining whether at least one pet file corresponding to the at least one pet record exists in the data storage or not; in response to determining that the at least one pet file does not exist in the data storage, creating a new pet file based on the at least one pet record; and associating the new pet file with the new pet owner file.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of priority to U.S. Provisional Application No. 63 / 353,687, filed on June 20, 2022, which is incorporated herein by reference in its entirety. Technical Field

[0002] Various embodiments of the present disclosure are generally directed to systems and methods for an integrated platform for dynamic electronic transactions with external pet adoption systems. Background Art

[0003] Pet owners can feel overwhelmed when it comes to finding a pet to adopt. Current solutions are siloed, generic, inefficient, and not specifically tailored to the needs of future pet owners. Additionally, current solutions do not take into account that pets may have existing medical records as well as other types of pet-specific records. This is especially true when a pet is surrendered to a pet shelter. Additionally, traditional technology fails to provide a single destination for the data management needs of future pet owners and pet owners’ pets.

[0004] The present disclosure is intended to address the above challenges. The background description provided herein is intended to present the background of the present disclosure in general. Unless otherwise indicated herein, the materials described in this section are not admitted to be prior art or suggestions of prior art. Summary of the invention

[0005] According to certain aspects of the present disclosure, methods and systems for conducting electronic transactions with external pet adoption systems are disclosed.

[0006] In one aspect, an exemplary embodiment of a computer-implemented method for dynamically managing electronic transactions of pet adoption data is disclosed. The method may include receiving, by one or more processors, a pet selection from a user device, the pet selection indicating that the user wants to adopt the pet. The method may include, in response to the user completing the adoption of the pet, sending, by the one or more processors, a confirmation message indicating that the pet has been adopted, the confirmation message including at least one user record and at least one pet record. The method may include determining, by the one or more processors, whether there is at least one pet owner profile corresponding to the at least one user record in the data store. The method may include, in response to determining that the at least one pet owner profile does not exist in the data store, creating, by the one or more processors, a new pet owner profile based on the at least one user record. The method may include determining, by the one or more processors, whether there is at least one pet profile corresponding to the at least one pet record in the data store. The method may include, in response to determining that the at least one pet profile does not exist in the data store, creating, by the one or more processors, a new pet profile based on the at least one pet record. The method may include associating, by the one or more processors, the new pet profile with the new pet owner profile.

[0007] In another aspect, an exemplary embodiment of a computer system for dynamically managing electronic transactions of pet adoption data is disclosed, the computer system including at least one memory storing instructions, and at least one processor configured to execute the instructions to perform operations. The operations may include receiving a pet selection from a user device, the pet selection indicating that the user wants to adopt the pet. The operations may include: in response to the user completing the adoption of the pet, sending a confirmation message indicating that the pet has been adopted, the confirmation message including at least one user record and at least one pet record. The operations may include determining whether there is at least one pet owner profile corresponding to the at least one user record in the data store. The operations may include creating a new pet owner profile based on the at least one user record in response to determining that the at least one pet owner profile does not exist in the data store. The operations may include determining whether there is at least one pet profile corresponding to the at least one pet record in the data store. The operations may include, in response to determining that the at least one pet profile does not exist in the data store, creating a new pet profile based on the at least one pet record. The operations may include associating the new pet profile with the new pet owner profile.

[0008] In another aspect, an exemplary embodiment of a non-transitory computer-readable medium storing instructions is disclosed that, when executed by at least one processor, cause the at least one processor to perform operations for dynamically managing electronic transactions of pet adoption data. The operations may include receiving a pet selection from a user device, the pet selection indicating that the user wants to adopt the pet. The operations may include, in response to the user completing the adoption of the pet, sending a confirmation message indicating that the pet has been adopted, the confirmation message including at least one user record and at least one pet record. The operations may include determining whether there is at least one pet owner profile corresponding to the at least one user record in the data store. The operations may include creating a new pet owner profile based on the at least one user record in response to determining that the at least one pet owner profile does not exist in the data store. The operations may include determining whether there is at least one pet profile corresponding to the at least one pet record in the data store. The operations may include, in response to determining that the at least one pet profile does not exist in the data store, creating a new pet profile based on the at least one pet record. The operations may include associating the new pet profile with the new pet owner profile. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various exemplary embodiments and, together with the description, serve to explain the principles of the disclosed embodiments.

[0010] Figure 1 An exemplary platform environment is depicted in accordance with one or more embodiments.

[0011] Figure 2 Depicted are exemplary environments of pet owner profiles and corresponding pet profiles in accordance with one or more embodiments.

[0012] Figure 3 A flow diagram of an exemplary embodiment of facilitating electronic trading of pet data is depicted in accordance with one or more embodiments.

[0013] Figure 4 A flow diagram is depicted of an exemplary embodiment of dynamically creating a New Pet Alert (NPA) to facilitate electronic trading of pet search data in accordance with one or more embodiments.

[0014] Figure 5 A flow diagram is depicted of an exemplary embodiment of dynamically managing electronic transactions for pet adoption data in accordance with one or more embodiments.

[0015] Figure 6 An example environment is described that can be used with the techniques described herein in accordance with one or more embodiments.

[0016] Figure 7Examples of computing devices that can perform the techniques described herein are described in accordance with one or more embodiments. DETAILED DESCRIPTION

[0017] According to certain aspects of the present disclosure, methods and systems for electronic transactional communications with external pet adoption systems are disclosed. Conventional techniques may not be applicable because conventional techniques may rely on pet owners to manually contact external services (e.g., pet shelters) to find pets for adoption. In addition, conventional techniques may not take into account existing pet data for pets abandoned at shelters. Such techniques may involve incompatible platforms, many username and password combinations, and may also involve pet owners being unaware of the existence of pet data.

[0018] The pet-keeping process may involve creating, managing, and storing a large amount of pet data. However, if the pet is abandoned at a pet shelter, the connection to the pet data may be lost. Important pet data (e.g., vaccination records, pet activity data, pet genetic data analysis, etc.) may be lost when the pet is sent to a shelter. In addition, most sources of pet data are independent of each other, which leads to multiple usernames and passwords, having to remember addresses of different sources, and misplacing pet data.

[0019] As will be discussed in more detail below, in various embodiments, systems and methods for dynamically managing electronic transactions of pet adoption data are described. The systems and methods are capable of receiving a pet selection from a user device. The systems and methods may then send a confirmation message indicating that the pet has been adopted and includes at least one user record and at least one pet record. The systems and methods may then determine whether there is at least one pet owner profile in the data store corresponding to the at least one user record. If a matching pet owner profile does not yet exist in the data store, the systems and methods may create a new pet owner profile using information in the at least one user record. The systems and methods may then determine whether there is at least one pet profile in the data store corresponding to the at least one pet record. If a matching pet profile does not yet exist in the data store, the systems and methods may create a new pet profile using information in the at least one pet record. The systems and methods may then associate the new pet profile with the new pet owner profile.

[0020] Although the terms used below are used in conjunction with the detailed description of certain specific examples of the present disclosure, these terms are to be interpreted in their broadest reasonable manner. In fact, certain terms may even be emphasized below; however, any term intended to be interpreted in any restrictive manner will be clearly and specifically defined in this detailed description. Both the foregoing general description and the following detailed description are exemplary and illustrative only and are not limiting of features.

[0021] In this disclosure, the term "based on" means "based at least in part on". The singular forms "a", "an", and "the" include plural references unless the context dictates otherwise. The term "exemplary" means "example" rather than "ideal". The terms "comprises", "comprising", "includes", "including" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, or product that includes a list of elements does not necessarily include only those elements, but may also include other elements not expressly listed or inherent to such process, method, article, or apparatus. The term "or" is used in disjunctive form, so that "at least one of A or B" includes (A), (B), (A and A), (A and B), etc. Relative terms such as "substantially" and "generally" are used to indicate that there may be a ±10% variation in the values ​​stated or understood.

[0022] As used herein, terms such as "user" and the like generally encompass a future pet owner, multiple future pet owners, a pet owner, and / or multiple pet owners. Terms such as "pet" and the like generally encompass domestic animals, such as domestic dogs, cats, rabbits, ferrets, horses, cattle, etc. In an exemplary embodiment, "pet" may refer to a canine. Exemplary Platform Environment

[0023] Figure 1 An exemplary platform environment 100 is depicted that can be used with the techniques described herein. More specifically, the environment 100 can provide an integrated hardware and software platform to improve pet digitization by centralizing pet information.

[0024] The platform 102 can communicate with one or more external systems that can collect, manage, and store different types of pet data and / or pet owner data. The platform 102 can retrieve pet data and / or pet owner data from one or more external systems via API 106. In some embodiments, the platform 102 can store pet data and / or pet owner data. For example, the platform 102 can store pet data in a pet archive 118. In addition, for example, the platform 102 can store pet owner data in a pet owner archive 120. The one or more external systems may include at least one of a health system 124, a diagnostic system 142, an adoption system 152, a content management system 164, a genetics system 170, and / or a third-party service system 182. Such external systems will be described in more detail below.

[0025] The platform 102 may also communicate with one or more external services. In some embodiments, the platform 102 may communicate with one or more external services via the API 106. The external services 122 may include, for example, one or more third parties and / or auxiliary systems that integrate and / or communicate with the platform 102 when performing various pet tasks. For example, the external services 122 may include at least one of the following: a veterinarian, a pet insurance agency, a pet service provider, etc.

[0026] The platform 102 may include a database 104 and / or cloud storage 114 that may store information corresponding to one or more pets and / or one or more pet owners. For example, the database 104 and / or cloud storage 114 may store a pet profile 118 and / or a pet owner profile 120. The database 104 and / or cloud storage 114 may be located internally or externally to the platform 102.

[0027] The platform 102 may include a personalized advertising system 108 and / or a payment system 110. The personalized advertising system 108 may create and / or display personalized advertisements to users. For example, personalized advertisements may be created based on information contained in a pet profile 118 and / or a pet owner profile 120. In some embodiments, the personalized advertising system 108 may display personalized advertisements on a user interface 112 of the platform 102. The payment system 110 may allow a user to create a financial account for a pet and / or perform financial transactions for pet services and / or pet goods (e.g., using a pet owner digital wallet 216).

[0028] The platform 102 may include a single sign-on 116. The single sign-on 116 may include a unique identifier that may correspond to a pet profile 118 and / or a pet owner profile 120. Each pet profile 118 may include information corresponding to a particular pet. A pet owner profile 120 may include information corresponding to a particular pet owner. In addition, the pet owner profile 120 and / or the pet profile 118 may each have a corresponding avatar and / or virtual presence. The avatar and / or virtual presence may include different attributes shared by the pet owner and / or the pet. The pet profile 118 and the pet owner profile 120 will be displayed in the same folder as the pet profile 118. Figure 2 Described in more detail in the description of . Health System

[0029] The health system 124 can collect, manage and / or display the health data of the pet. The health system 124 can be an internal component or an external component of the platform 102, wherein the health system 124 can communicate with the platform 102 via the API 106.

[0030] The health system 124 can collect data from one or more smart devices. The health system 124 can communicate with one or more smart devices via one or more APIs. In addition, in some embodiments, the health system can use application software 126 to facilitate communication and / or management of one or more smart devices. For example, application software 126 can communicate with one or more smart devices that can run on an external system. In addition, for example, application 126 can run on a user device, where application 126 provides a user interface to display data collected by one or more smart devices. In some embodiments, application 126 can manage one or more smart devices. The health system 124 can communicate with one or more smart devices by sending one or more requests to one or more smart devices. The request can require one or more smart devices to send the collected health data to the health system 124. In some embodiments, the one or more smart devices can automatically send health data to the health system 124. For example, the one or more smart devices can send health data to the health system 124 at regular time intervals (e.g., every 30 seconds, every hour, every day, etc.) and / or whenever new health data is collected. In some embodiments, the health system 124 can store health data in internal or external storage. For example, the health system 124 can store the health data in the database 104 and / or the cloud storage 114. Additionally or alternatively, the health system 124 can store the health data in the pet profile 118 and / or the pet owner profile 120, for example.

[0031] After receiving health data from one or more smart devices, the health index scoring system 128 can analyze the health data to determine a health score. The health index scoring system 128 can update the health score, where the update is based on the most recently received health data. In some embodiments, the health index scoring system 128 can store the health score in one or more databases (e.g., database 104) and / or cloud storage (e.g., cloud storage 114). For example, the health score can be stored in a pet profile 118 and / or a pet owner profile 120. Additionally or alternatively, the health system 124 can display the health score to the user. For example, the health system 124 can display the health score on a user interface of a user device. This can be achieved by utilizing application software 126. Additionally or alternatively, the health system 124 can display the health score on one or more smart devices.

[0032] Example smart devices may include at least one of a smart collar 130 , a smart bed 132 , a smart feeder 134 , a smart litter box 136 , a smart camera 138 , and / or other sensors 140 for collecting digital images of a pet's life.

[0033] The smart collar 130 may include a device and / or sensor that can be attached to a pet. For example, the smart collar 130 may be attached around the pet's neck. The smart collar 130 may detect the pet's activity, location, and feeding information, such as physical activity, location, feeding habits, drinking habits, etc. The smart collar 130 may collect the pet's activity, location, and feeding information and send such information to the health system 124. In some embodiments, the smart collar 130 may automatically send the activity, location, and feeding information to the health system 124 after a set time period. In some embodiments, the smart collar 130 may send the activity, location, and feeding information in response to a request from the health system 124.

[0034] The smart bed 132 may include devices and / or sensors that may be included in a pet bed. The smart bed 132 may track sleep information corresponding to the pet. The sleep information may include the amount of time the pet sleeps on the smart bed 132, how often the pet gets up from the smart bed 132, whether the pet tosses and turns while sleeping, etc. The smart bed 132 may send such information to the health system 124. In some embodiments, the smart bed 132 may automatically send the sleep information to the health system 124 after a set period of time. In some embodiments, the smart bed 132 may send the sleep information in response to a request from the health system 124.

[0035] Smart feeder 134 may include devices and / or sensors that may be included in a pet food feeder. Smart feeder 134 may track how much food is dispensed for a pet. Smart feeder 134 may send such food dispensing information to health system 124. In some embodiments, smart feeder 134 may automatically send food dispensing information to health system 124 after a set time period. In some embodiments, smart feeder 134 may send food dispensing information in response to a request from health system 124.

[0036] The smart pet litter box 136 may include a device and / or sensor that may be included in the pet litter box. The smart pet litter box 136 may track the pet litter box information of the pet. The pet litter box information may include at least one of the following: how often the pet uses the smart pet litter box 136, what the pet does in the smart pet litter box 136, etc. In some embodiments, the smart pet litter box 136 may automatically send the pet litter box information to the health system 124. In some embodiments, the smart pet litter box 136 may automatically send the pet litter box information to the health system 124 after a set time period. In some embodiments, the smart pet litter box 136 may send the pet litter box information in response to a request from the health system 124.

[0037] The smart camera 138 may include devices and / or sensors that may be included in a camera. The smart camera 138 may capture behavioral information of the pet. The behavioral information of the pet may include physical activity, eating from the pet's food dish, eating from a source other than the pet's food dish, drinking from the pet's water dish, drinking from a source other than the pet's water dish, etc. In some embodiments, the smart camera 138 may automatically send the behavioral information to the health system 124 after a set period of time. In some embodiments, the smart camera 138 may send the behavioral information in response to a request from the health system 124.

[0038] Other sensors 140 for collecting digital images of pet life may include one or more devices and / or one or more sensors that collect data of digital images of pet life. Example collected data may include information about the pet's eating behavior, sleeping behavior, drinking behavior, playing behavior, etc. In some embodiments, other sensors 140 may automatically send the collected data to the health system 124 after a set time period. In some embodiments, other sensors 140 may send the collected data in response to a request from the health system 124. Diagnostic system

[0039] Diagnostic system 142 can manage the pet's health information and provide a personalized diagnosis 144 and / or a personalized health plan 146 to the user. Diagnostic system 142 can be an internal component or an external component of platform 102, wherein diagnostic system 142 can communicate with platform 102 via API 106.

[0040] The diagnostic system 142 can manage the health information of the pet (e.g., vaccination records, medical records) by receiving the health information of the pet from one or more external services 150 (e.g., veterinarians, clinics, pet hospitals, etc.). The diagnostic system 142 can store the health information of the pet in the pet profile 118. In one embodiment, the diagnostic system 142 can transmit the health information of the pet using the API 106.

[0041] The diagnostic system can create a personalized diagnosis 144 and / or a personalized health plan 146 based on the pet's health information. The personalized diagnosis 144 may include one or more diagnoses of a pet's medical condition (e.g., ear infection, eye infection, etc.). The personalized diagnosis 144 may be based on a diagnosis made by an external service 150. In some embodiments, the personalized diagnosis 144 may be based on a diagnosis made by one or more machine learning models. The personalized health plan 146 may include one or more recommendations about feeding events, exercise events, health checks, and health visits, etc., which may be based on the pet's health information. The personalized health plan 146 may be based on recommendations made by an external service 150. The personalized health plan 146 may be based on information contained in the pet profile 118. In some embodiments, the personalized health plan may be based on one or more recommendations made by one or more machine learning models.

[0042] The health portal 148 can provide access to one or more parties who wish to retrieve the personalized diagnosis 144, the personalized health plan 146, and / or the pet's health information from the pet profile 118. The health portal 148 can be internal or external to the diagnostic system 142. In addition, the health portal 148 can include a user interface. For example, a pet groomer can access the health portal 148 to retrieve a pet's vaccination record from the diagnostic system 142.

[0043] The diagnostic system 142 can communicate with an external service 150 (e.g., a veterinarian, a clinic, a pet hospital, etc.). For example, the external service 150 (e.g., a veterinarian) can send updated vaccination records or medical records to the diagnostic system 142, which can then store such updated vaccination records or medical records in the pet profile 118. In addition, for example, the diagnostic system can update the personalized diagnosis 144 and / or the personalized health plan 146 based on the updated vaccination records or medical records.

[0044] In some embodiments, the diagnostic system 142 may include information for verifying the pet. For example, social media sites often require users to verify in order to mark the user as "verified" (e.g., a blue check mark). The diagnostic system 142 may include information corresponding to a physical examination of the pet. Such information may include verification information for the pet. For example, the verification information may include confirmation of the pet's breed, gender, image, etc. The social media site may use such verification information to verify the pet as a "verified" user. Adoption system

[0045] The adoption system 152 can match future pet owners with pets and provide additional support to future pet owners. The adoption system 152 can be an internal component or an external component of the platform 102, wherein the adoption system 152 can communicate with the platform 102 via the API 106. The adoption system 152 can also communicate with external services 162. For example, the adoption system 152 can communicate with one or more animal shelters (e.g., external services 162) to receive and / or pet information from one or more animal shelters. In addition, for example, the one or more external services may include one or more data stores, wherein the one or more data stores may include one or more pet records. The adoption system 152 can communicate with one or more external services to receive one or more pet records.

[0046] The adoption system 152 may use a personalized matching module 154 and / or a search engine 156 to match a future pet owner with a particular pet. The personalized matching module 154 may use user information (e.g., user location, user age, etc.) from the future pet owner (e.g., from the pet owner profile 120) to automatically search for one or more pets that are most suitable for the future pet owner. In some embodiments, the personalized matching module 154 may use one or more machine learning models to determine the best pet match for the future pet owner. The search engine 156 may allow the future pet owner to search for one or more pets. The search engine 156 may include different search filters (e.g., filtering by breed, age, size, weight, etc.), which may allow the user to filter the results for one or more pets.

[0047] The personalized matching module 154 and / or the search engine 156 can retrieve results from the external service 162. The external service 162 can include one or more of the following: pet adoption agencies, shelters, pet breeders, etc. When the personalized matching module 154 and / or the search engine 156 are searching for one or more pets, the personalized matching module 154 and / or the search engine 156 can send one or more requests to the external service 162 to obtain available pets that meet one or more parameters contained in the one or more requests. After receiving the one or more requests, the external service 162 can search for one or more matching pets in one or more databases. The external service 162 can send a response to the personalized matching module 154 and / or the search engine 156. The response may include one or more matching pets. Alternatively, for example, if no matching pet is found, the response may include an indicator that no matching pet is found. In some embodiments, the adoption system 152 can store one or more matching pets in a database, such as an internal database or an external database (e.g., database 104).

[0048] The adoption system 152 can display one or more matching pets to the future pet owner and provide the future pet owner with the option to adopt and / or purchase one or more matching pets. The adoption system 152 can also facilitate the adoption and / or purchase of one or more matching pets. In some embodiments, the adoption system 152 can communicate with the external service 162 to facilitate the adoption and / or purchase of one or more matching pets.

[0049] Once a future pet owner purchases and / or adopts a pet, the adoption system 152 can store and / or manage the pet's adoption / registration record 160. In some embodiments, the adoption system 152 can receive all (or part) of the pet's adoption / registration record 160 from an external service. In some embodiments, the adoption system 152 can store the pet's adoption / registration record 160 in the pet profile 118. Additionally or alternatively, the adoption system 152 can store the pet's adoption / registration record in the pet owner profile 120. In some embodiments, the adoption system 152 can store the pet's adoption / registration record 160 in an internal or external database.

[0050] The adoption system 152 can provide additional support to future pet owners by providing personalized recommendations 158 to the pet owner. The personalized recommendations 158 can be based on the characteristics of the pets purchased and / or adopted by the future pet owner. Example personalized recommendations 158 can include recommended pet foods, recommended pet providers, recommended pet supplies, etc. In some embodiments, the personalized recommendations 158 can be based on communications with one or more external services. For example, the adoption system 152 can communicate with the content management system 164 to receive personalized content 168, and then make personalized recommendations 158 based on the personalized content 168. Content Management System

[0051] The content management system 164 can provide personalized content 168 to the user. The content management system 164 can be an internal component of the platform 102 or an external component, where the content management system 164 can communicate with the platform 102 via the API 106.

[0052] The content management system 164 can retrieve personalized content 168 and display such personalized content 168 to the user. The personalized content 168 can include at least one of the following: articles, blog posts, online forums, advertisements, etc. The personalized content 168 can also include recommendations specifically for pets and / or users. The recommendations can include food recommendations, activity recommendations, product recommendations, resource recommendations (e.g., books, articles, etc.), third-party service recommendations (e.g., pet groomers, trainers, boarding), etc. The personalized content 168 can be personalized based on the pet profile 118 and / or the pet owner profile 120. The content management system 164 can display the personalized content 168 via the user interface of the user device. In some embodiments, the content management system 164 can retrieve the personalized content 168 from the external service 166. The external service 166 can include an electronic magazine, one or more databases, one or more social media posts, etc. In some embodiments, the content management system 164 can retrieve the personalized content 168 from other sources (e.g., database 104, cloud storage 114, and personalized advertising system 108). In some embodiments, content management system 164 can create personalized content 168 based on communications with other external systems (e.g., health system 124, diagnostic system 142, adoption system 152, genetics system 170, third-party service system 182, etc.). For example, content management system 164 can receive personalized health plan 146 from diagnostic system 142. Personalized content 168 can then be based on (or include) information from personalized health plan 146. Genetics system

[0053] Genetics system 170 can analyze and / or monitor the genetic data of the pet. Genetics system 170 can be an internal component of platform 102 or an external component, wherein genetics system 170 can communicate with platform 102 via API 106.

[0054] Genetics system 170 may include genetic data analysis 172, genetic data monitoring 174, and / or personalized recommendations 176. In addition, genetic data analysis 172 and / or genetic data monitoring 174 may communicate with external services 180 to assist in analyzing and / or monitoring genetic data. External services may include laboratories, clinics, veterinarians, etc.

[0055] Genetic data analysis 172 can receive genetic data belonging to a pet. In some embodiments, genetic data analysis 172 can receive genetic data from a genetic data retrieval system 178. Genetic data retrieval system 178 can retrieve and store genetic data belonging to one or more pets. In addition, genetic data analysis can receive genetic data from genetic data retrieval system 178, wherein the received genetic data is used to analyze the genetic data belonging to the pet. Genetic data analysis 172 can analyze the genetic data to determine abnormalities, potential genetic characteristics, familial relationships, etc. In some embodiments, genetic data analysis 172 can communicate with external services 180 to assist in analyzing genetic data. For example, genetic data analysis 172 can send genetic data information to a laboratory for the laboratory to perform analysis of the genetic data.

[0056] Genetic data monitoring 174 can monitor genetic data belonging to a pet to determine any changes in the genetic data. For example, genetic data monitoring 174 can receive new genetic data and compare the new genetic data to previously stored genetic data. This comparison can allow genetic data monitoring 174 to determine that there is an anomaly or improvement in the genetic data. In some embodiments, genetic data monitoring 174 can communicate with external service 180 so that external service 180 analyzes the genetic data and determines whether there are any changes.

[0057] The genetics system 170 may provide personalized recommendations 176 to the user. For example, the genetics system 170 may provide personalized recommendations 176 to the user via a user interface of a user device. In some embodiments, the personalized recommendations may be based on genetic data analysis 172 and / or genetic data monitoring 174. Personalized recommendations 176 may include pet food recommendations, exercise recommendations, pet supplies recommendations, health checks or health visits, etc. In some embodiments, personalized recommendations 176 may be based on communications with one or more external services. For example, the genetics system 170 may communicate with the diagnostic system 142. The genetics system 170 may send a request for a personalized health plan 146 to the diagnostic system 142. The request may include, for example, genetic data analysis 172 and / or genetic data monitoring 174. The diagnostic system 142 may transmit the personalized health plan 146 to the genetics system 170, wherein the personalized health plan 146 may be based on the genetic data analysis 172 and / or genetic data monitoring 174. The genetics system 170 may make personalized recommendations 176 to the user based on the personalized health plan 146.

[0058] In some embodiments, the genetics system 170 may include information for verifying a pet. For example, social media sites often require users to verify in order to mark the user as "verified" (e.g., a blue check mark). The genetics system 170 may include information corresponding to a physical examination of the pet. Such information may include verification information for the pet. For example, the verification information may include confirmation of the pet's breed, gender, image, etc. The social media site may use such verification information to verify the pet as a "verified" user. Third-party service system

[0059] The third-party service system 182 can allow users to search for and book different external services 190, such as pet groomers, trainers, veterinarians, holistic care (e.g., nutritionists, naturopaths), etc. The third-party service system 182 can be an internal component or an external component of the platform 102, wherein the third-party service system 182 can communicate with the platform 102 via the API 106.

[0060] The third-party service system 182 may include a search engine 184 , a booking engine 186 , and / or a management component 188 .

[0061] The search engine 184 may allow a user (e.g., a pet owner) to search for external services 190 to book for the user's pet. The search engine 184 may include filtering capabilities to facilitate fine-tuning the search. The filtering capabilities may include general filtering and / or service-specific filtering. For example, general filtering may include filtering external services 190 by location, price range, and / or rating. Additionally, for example, service-specific filtering may include filtering external services 190 by breed specialty, health issues, and / or behavioral needs.

[0062] The booking engine 186 may allow a user to book an external service 190. For example, after searching for an external service 190 using the search engine 184, the user may use the booking engine 186 to book a specific service of the external service 190. The booking engine 186 may present open dates and time slots, which may correspond to the selected external service 190. The user may then use the booking engine 186 to select a date and / or time from the displayed open dates and time slots. Once the booking is complete, the user may receive an instant confirmation of the booking, such as via text message or email. The user may also pay for the booked service immediately. Alternatively, the user may pay after the service is complete. The user may upload photos to the external service 190 and add annotations. For example, the user may upload a photo of the dog to the pet groomer, or note that the user's dog is limping.

[0063] The management component 188 can provide functions for managing different external services 190. For example, the management component 188 can provide functions for registering and / or unregistering external services 190 in the third-party service system 182. The management component 188 can communicate with one or more databases (e.g., database 104) and / or cloud storage (e.g., cloud storage 114) to store information corresponding to the external service 190 (e.g., name, business identity, expertise, etc.). Example Pet Owner Profile and Pet Profile

[0064] Figure 2 An exemplary environment 200 of pet owner profiles 202 and corresponding pet profiles that can be used with the techniques described herein is depicted. Notably, the exemplary platform environment 200 can be used with Figure 1 The pet owner profile 202 corresponding to the pet owner profile 120 of the exemplary platform environment 100 is supplemented. In addition, the pet profile 204, the pet profile 206 and / or the pet profile 208 may correspond to Figure 1 Pet profile 118.

[0065] The pet owner profile 202 may include at least one of the following: a pet owner name 210, a pet owner identifier 212, a pet owner address 214, a pet owner digital wallet 216, a pet owner demographic information 218, a pet owner email address 220, at least one pet profile (e.g., pet profile 204, pet profile 206, pet profile 208) and / or at least one identifier associated with at least one pet profile, and / or a pet owner history 222. The pet owner name 210 may include the name of the pet owner. The pet owner identifier 212 may include a unique identifier that may be used to locate the pet owner profile 202. In some embodiments, the pet owner identifier 212 may allow tracking of some or all of the user's activities. The pet owner address 214 may include the pet owner's physical address. The pet owner digital wallet 216 may include payment information, such as credit card information, cryptocurrency information, etc. The pet owner demographic information 218 may include specific demographic data of the pet owner. The pet owner email address 220 may include the pet owner's email address. The pet owner profile may include at least one pet profile (e.g., pet profile 204, pet profile 206, pet profile 208). In some embodiments, pet owner profiles 202 may include at least one identifier (e.g., unique pet identifier 228) associated with at least one pet profile, rather than including the entire contents of at least one pet profile. Each pet profile may correspond to a pet belonging to a pet owner. The number of pet profiles may be dynamic, where the pet profiles may be adjusted based on the number of pets belonging to the user.

[0066] The pet owner history 222 may include a payment history 224 and / or a booking history 226. The payment history 224 may include the pet owner's financial transactions. In some embodiments, the payment history 224 may correspond to the activity of the pet owner's digital wallet 216. In some embodiments, the payment history 224 may be tracked and analyzed to provide targeted advertising (e.g., personalized advertising system 108) and / or recommendations to the pet owner. The booking history 226 may include third-party services that the user has previously booked. In some embodiments, the booking history 226 may be tracked and analyzed to provide targeted advertising (e.g., personalized advertising system 108) and / or recommendations to the pet owner.

[0067] Pet profiles 204, pet profiles 206, and / or pet profiles 208 may each correspond to a different pet of the pet owner belonging to pet owner profile 202. The pet owner may have more or less than three pets. The number of pet profiles may be dynamic, with the number of pet profiles corresponding to the number of pets belonging to the pet owner. In some embodiments, the pet owner may only want a subset of the pet owner's pets to have pet profiles.

[0068] Pet profiles 204 , 206 , and / or 208 may each include at least one of: a unique pet identifier 228 , breed / DNA information 230 , veterinary history 232 , microchip information 234 , pet images 236 , vaccination records 238 , purchase history 240 , adoption / registration records 242 , activity data 244 , health score 246 , insurance policy 248 , health plan 250 , reservation history 252 , pet name 254 , medication history 256 , dietary needs 258 , and / or a pet savings account 260 .

[0069] The unique pet identifier 228 may include a unique identifier that may be used to locate a corresponding pet profile (eg, pet profiles 204, 206, and / or 208). In some embodiments, the unique pet identifier 228 may allow tracking of some or all activities corresponding to a pet.

[0070] Pet image 236 may include a photo, drawing, virtual presence, and / or avatar of a pet. Pet name 254 may include the name and / or any nicknames of the pet. Insurance policy 248 may include a pet insurance policy for the pet. Purchase history 240 may include purchases made for the pet. Pet savings account 260 may include a financial savings account for the pet. In some embodiments, pet image 236, pet name 254, purchase history 240, pet savings account 260, and / or insurance policy 248 may have been received from one or more external systems.

[0071] Breed / DNA information 230 may correspond to the breed and / or DNA information of the pet. In some embodiments, breed / DNA information 230 may have been received from one or more external systems. For example, breed / DNA information 230 may have been received from genetics system 170.

[0072] Veterinary history records 232 may include detailed information about a pet's visit to a veterinarian. Veterinary history records 232 may also include a veterinarian's record and / or possible diagnosis and treatment. Vaccination records 238 may include one or more vaccination records of vaccines administered to a pet. Medication history 256 may include detailed information about medications currently taken and / or taken in the past by a pet. Dietary needs 258 may include information about foods that a pet should eat and / or foods that a pet should avoid. Health plan 250 may correspond to a health plan for a pet. In some embodiments, health plan 250 may have been determined based on personalized health plan 146. In some embodiments, veterinary history records 232, vaccination records 238, dietary needs 258, health plan 250, and / or medication history 256 may have been received from one or more external systems. For example, veterinary history records 232, vaccination records 238, dietary needs 258, health plan 250, and / or medication history 256 may have been received from diagnostic system 142.

[0073] Microchip information 234 may include a microchip number for the pet. For example, a microchip may have been inserted into the pet to track the pet. Adoption / registration record 242 may include documentation for adopting or purchasing a pet. In some embodiments, microchip information 234 and / or adoption / registration record 242 may have been received from one or more external systems. For example, microchip information 234 and / or adoption / registration record 242 may have been received from adoption system 152.

[0074] Activity data 244 may include data corresponding to the pet's physical activity, sleep activity, and / or food activity. For example, the activity data may be collected by a smart collar 130, a smart bed 132, a smart feeder 134, a smart pet litter box 136, a smart camera 138, and / or other sensors 140 for collecting digital images of the pet's life. Health score 246 may include data corresponding to the health score generated by health index scoring system 128. In some embodiments, activity data 244 and / or health score 246 may have been received from one or more external systems. For example, activity data 244 and / or health score 246 may have been received from health system 124.

[0075] Booking history 252 may include data corresponding to one or more bookings with a third-party service (e.g., a pet groomer, trainer, etc.). In some embodiments, booking history 252 may have been received from one or more external systems. For example, booking history 252 may have been received from a third-party service system 182. Exemplary Method for Dynamically Managing New Pet Data

[0076] Figure 3 An exemplary method 300 of an exemplary embodiment for facilitating electronic trading of new pet data according to one or more embodiments is shown. Notably, the method 300 can be performed by one or more processors of a server that communicates with one or more user devices and other external systems via a network. However, it should be noted that the method 300 can be performed by any one or more of the server, one or more user devices, or other external systems.

[0077] The method may include sending, by one or more processors, a request for at least one new pet record to at least one external service (e.g., one or more external services 162), wherein the at least one new pet record may include new pet data for one or more new pets (step 302). The adoption system (e.g., adoption system 152) and / or the platform (e.g., platform 102) may send the request to the one or more external services. The new pet data may include at least one of the following: name, microchip data, photo, video, age, coat color, coat length, breed, sub-breed, adoption fee, gender, size category, current weight, species, whether the pet can be ridden, whether an experienced adopter is required, whether the pet is neutered, whether the pet is house trained, whether the pet's vaccines are up to date, whether the pet has been declawed, and / or whether the pet has special needs. In addition, in some embodiments, the one or more external services may correspond to one or more pet shelters, animal breeders, etc. Each of the one or more external services may include a unique data storage system and a unique communication protocol. The request sent to the one or more external services may be a unique request in the form of a specific communication protocol for a specific external service.

[0078] In some embodiments, the external service may include or retain at least one directory. The at least one directory may be stored in a data store of the at least one external service. In addition, the at least one directory may include at least one record, wherein at least one record may include pet information corresponding to a pet. The format of the record may be different from the format of the data store (e.g., database 104) of the platform / adoption system. The external service (e.g., external service 162) may send the pet record of the directory to the adoption system (e.g., adoption system 152). The external service may send the pet record to the adoption system in response to a change in the pet's status. For example, if the pet's status is changed to "adoptable", the corresponding pet record may be sent to the adoption system. In addition, if the pet's status is changed to any state other than "adoptable", a request may be sent to the adoption system to delete the pet record or update the pet record accordingly.

[0079] The method may include receiving, by one or more processors, at least one new pet record from at least one external service (e.g., one or more external services 162) (step 304). The new pet corresponding to the one or more new pet records may include a pet that has recently been adopted or surrendered to a shelter (e.g., external service 162). In addition, the request may be received in the form of a specific communication protocol of the external service. This may allow the adoption system to receive the new pet record from a unique data storage system of the external service.

[0080] In some embodiments, the method may include determining, by one or more processors, whether one or more new pet records contain pet data. If the new pet record does not contain pet data for at least one new pet, the method may stop. If the new pet record does contain pet data for at least one new pet, the method may continue to analyze the pet data in the new pet record.

[0081] The method may also include converting, by one or more processors, the new pet data in the received at least one new pet record (step 306). For example, the adoption system (e.g., adoption system 152) may convert the received new pet record to a standardized format. The adoption system may include functionality to convert data received via different types of communications to a standardized format in order to standardize the received data. For example, the adoption system may standardize new pet records that it receives from an external service.

[0082] The method may also include storing, by one or more processors, the converted new pet data in a corresponding pet record (step 308). For example, the adoption system (e.g., adoption system 152) may store the converted new pet record in a data store (e.g., database 104).

[0083] The method may include sending a New Pet Alert ("NPA") to a user based on stored pet records that match at least one pet search. This method is described below Figure 4 Described in the description.

[0084] although Figure 3 Example blocks of the exemplary method 300 are shown, but in some embodiments, the exemplary method 300 may include Figure 3 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the exemplary method 300. Additionally or alternatively, two or more blocks of the exemplary method 300 may be performed in parallel. Exemplary method for dynamically managing pet search data

[0085] Figure 4 An exemplary method 400 of an exemplary embodiment for dynamically creating a new pet alert (NPA) to facilitate electronic trading of pet search data according to one or more embodiments is shown. It is worth noting that the method 400 can be performed by one or more processors of a server that communicates with one or more user devices and other external systems via a network. However, it should be noted that the method 400 can be performed by any one or more of the server, one or more user devices, or other external systems.

[0086] The method may include receiving, by one or more processors, one or more pet search records (step 402). For example, the one or more pet search records may be retrieved from a data store (e.g., database 104), wherein the one or more pet search records may include parameters for the pet search. In addition, the one or more pet search records may be associated with one or more users who input the search parameters. In some embodiments, when an adoption system (e.g., adoption system 152) receives at least one new pet record, the adoption system may process the one or more pet search records. For example, the method may include continuously processing newly received pet records to determine whether any new pet records match the one or more pet search records. In some embodiments, the method may include waiting to process pet records until a threshold number of pet records are received from one or more external services (e.g., external service 162).

[0087] The method may include determining, by one or more processors, at least one pet record that matches one or more pet search records (step 404). The pet search record may include one or more parameters. For example, the one or more parameters may include breed, age, weight, etc. If at least one parameter of the pet search record matches the pet data in the pet record, the adoption system (e.g., adoption system 152) may determine that a match exists. For example, if the pet search record includes an age range (e.g., 5 to 10 years old), and the pet data indicates that the age of the pet falls within the age range of the pet search record (e.g., the pet is 7 years old), then there may be a match.

[0088] The method may include, in response to determining at least one matching pet record, determining, by one or more processors, at least one user associated with the one or more pet search records (step 406). The determination may include analyzing the one or more pet search records to obtain associated user information (e.g., user name, identifier, etc.). In some examples, the associated user information may correspond to the user performing the pet search. In some embodiments, if the search save table does not exist, the determination may also include creating a search save table associated with the user.

[0089] The method may include, in response to determining the at least one user, associating, by one or more processors, the at least one user with at least one matching pet record (step 408). In some embodiments, the associating may include the adoption system (e.g., adoption system 152) adding the pet record to a search saved list associated with the user.

[0090] The method may include sending, by one or more processors, at least one pet record to a user device corresponding to a user associated with one or more pet search records (step 410). In some embodiments, an adoption system (e.g., adoption system 152) may send the one or more pet records to a user device via one or more notifications.

[0091] In some embodiments, the method may include receiving, by one or more processors, an alert that the user disabled / deactivated the user's account. Additionally, or alternatively, the alert may indicate that the user has been added to a "do not contact" list. For example, a data store (e.g., database 104) may include a separate "do not contact" table that may include a list of users that the platform and / or adoption system should not contact. The method may include an adoption system (e.g., adoption system 152) and / or a platform (e.g., platform 102) receiving an alert from an external service (e.g., external service 162). The method may also include searching a search save table for a saved search corresponding to such a user. For example, the search save table may include one or more search records, wherein the search save table may be stored in a database (e.g., database 104). The method may also include removing the saved search corresponding to the user from an NPA search queue. The NPA search queue may include one or more search records for active searches. The NPA search queue may be stored in a database (e.g., database 104).

[0092] In some embodiments, the method may include receiving, by one or more processors, an alert that the user account is no longer disabled / deactivated. Additionally, or alternatively, the alert may indicate that the user has been removed from a "Do Not Contact" list. The method may include an adoption system (e.g., adoption system 152) and / or a platform (e.g., platform 102) receiving an alert from an external service (e.g., external service 162). The method may also include searching a search save table for saved searches corresponding to such user. The method may also include migrating searches corresponding to the user from the search save table to an NPA search queue.

[0093] In some embodiments, the method may include creating a search record based on input from a user by one or more processors. For example, a user may create a search for a specific type of pet by entering one or more parameters. For example, the parameters may include pet-specific parameters, as well as location-specific parameters. The pet-specific parameters may include at least one of the following: name, microchip data, photo, video, age, coat color, hair length, breed, sub-breed, adoption fee, gender, size category, current weight, species, whether it can be ridden, whether an experienced adopter is required, whether the pet is sterilized, whether the pet is house-trained, whether the pet's vaccines are up to date, whether the pet has been declawed, and / or whether the pet has special needs. The location-specific parameters may include a geographic point corresponding to the user and / or an external service (e.g., external service 162), a zip code, a country abbreviation, etc. In some embodiments, the method may include calculating a geographic point corresponding to the user and / or a shelter. For example, the geographic point may be calculated using earth coordinates. The specific location parameters may also include a geographic range. In some embodiments, the geographic point and geographic range may be used to calculate a bounding box representing the area covered by the search.

[0094] In some embodiments, the method may further include storing, by one or more processors, the search as a search record. For example, the search record may be stored by an adoption system (e.g., adoption system 152) in a data store (e.g., database 104). Additionally or alternatively, the search record may be stored in a search save table.

[0095] In some embodiments, the method may further include updating, by one or more processors, the NPA search queue. For example, a user may access a previously saved search and update one or more parameters of the search. Then, the adoption system and / or platform (e.g., platform 102) may update the corresponding search record in the NPA search queue. In addition, the adoption system and / or platform may update the corresponding search record in the search save table.

[0096] In some embodiments, the method may include migrating, by one or more processors, active searches from a search save table to an NPA search table. After the search records are saved in the search save table, the platform (e.g., platform 102) and / or the adoption system (e.g., adoption system 152) may migrate the active searches to the NPA search table. The NPA search table may store search records and users for active searches. For example, search records corresponding to users in a "Do Not Contact" list may not be migrated to the NPA search table.

[0097] although Figure 4 Example blocks of the exemplary method 400 are shown, but in some embodiments, the exemplary method 400 may include Figure 4Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the exemplary method 400. Additionally or alternatively, two or more blocks of the exemplary method 400 may be performed in parallel. Exemplary Method for Dynamically Managing Pet Adoption Data

[0098] Figure 5 An exemplary method 500 of an exemplary embodiment for dynamically managing electronic transactions of pet adoption data according to one or more embodiments is shown. Notably, the method 500 can be performed by one or more processors of a server that communicates with one or more user devices and other external systems via a network. However, it should be noted that the method 500 can be performed by any one or more of the server, one or more user devices, or other external systems.

[0099] The method may include performing, by one or more processors, a pet selection from a user device, the pet selection indicating that the user wants to adopt a pet (step 502). The pet selection may indicate that the user wishes to take the pet home (e.g., adopt). In some embodiments, an adoption system (e.g., adoption system 152) may display one or more prompts on one or more user interfaces of the user device. For example, the one or more prompts may require the user to provide information to complete the adoption of the pet. Example information may include payment information (e.g., credit card information), personal information (e.g., user name, date of birth, etc.), confirmation of agreement to terms and conditions, etc.

[0100] In response to the user completing the adoption of the pet, the method may include sending, by one or more processors, confirmation information indicating that the pet has been adopted (step 504). In some embodiments, the adoption system (e.g., adoption system 152) may send a confirmation message to the platform (e.g., platform 102) indicating that the user has completed the adoption process. The confirmation message may include at least one user record and at least one pet record. The at least one user record may include user information, such as some or all of the information required for a pet owner profile (e.g., pet owner profile 202). In some embodiments, the user may have created a pet owner profile before completing the pet adoption. The at least one pet record may include at least some of the information required for a pet profile (e.g., pet profile 204).

[0101] The method may include determining, by one or more processors, whether at least one pet owner profile (e.g., pet owner profile 202) corresponding to at least one user record exists in a data store (step 506). For example, the adoption system may determine whether at least one pet owner profile corresponding to at least one user record exists in a data store (e.g., database 104). For example, the platform (e.g., platform 102) and / or the adoption system (e.g., adoption system 152) may search the pet owner profile (e.g., pet owner profile 202) stored in a database (e.g., database 104) to determine whether at least one pet owner profile matches information in at least one user record. Additionally or alternatively, the confirmation information may include a pet owner identifier (e.g., pet owner identifier 212) of a pre-existing pet owner profile (e.g., pet owner profile 202). In such an embodiment, the platform and / or the adoption system may use the pet owner identifier to identify the pet owner profile.

[0102] In response to determining that at least one pet owner profile does not exist in the data store, the method may include creating, by one or more processors, a new pet owner profile based on at least one user record (step 508). For example, the adoption system and / or platform may create the new pet owner profile. In addition, the adoption system and / or platform may create the new pet owner profile using at least some information included in the at least one user record (e.g., the user's name, address, etc.).

[0103] The method may include determining, by one or more processors, whether at least one pet profile corresponding to at least one pet record exists in a data store (e.g., database 104) (step 510). For example, the platform and / or adoption system may search pet profiles (e.g., pet profiles 204) stored in a database (e.g., database 104) to determine whether at least one pet profile matches information in the at least one pet record. For example, the platform and / or adoption system may analyze pet owner profiles to determine whether any pet profiles match information in the at least one pet record. If the pet owner profile (e.g., pet owner profile 202) does not include any pet profiles that match information in the at least one pet record, the platform and / or adoption system may automatically create a new pet profile based on the at least one pet record by one or more processors (step 512). After creating the new pet profile, the method may also include associating, by one or more processors, the new pet profile with the new pet owner profile (step 514).

[0104] In some embodiments, the platform (e.g., platform 102) and / or adoption system (e.g., adoption system 152) may search all data stores, regardless of corresponding pet owner profiles, to obtain at least one pet profile that matches information in at least one pet record. In response to finding at least one matching pet profile, the platform and / or adoption system may then determine whether the matching pet profile includes a corresponding pet owner profile (or data identifying a corresponding pet owner profile). If the matching pet profile includes a corresponding pet owner profile, the platform and / or adoption system may then analyze the pet owner profile to determine whether the pet owner profile matches a new pet owner profile corresponding to at least one user record. If the pet owner profile does not match the new pet owner profile, the platform and / or adoption system may then delete any association between the pet owner profile and the pet profile. In addition, the platform and / or adoption system may then associate the pet profile with the new pet owner profile.

[0105] The method may also include interacting with one or more external systems using the data in the pet owner profile or pet profile by one or more processors (step 516). For example, the platform and / or adoption system may interact with one or more external systems (e.g., at least one of the health system 124, the diagnostic system 142, the adoption system 152, the content management system 164, the genetics system 170, and / or the third-party service system 182) using the data in the pet owner profile and / or the pet profile. In some embodiments, the platform and / or adoption system may send a request to the diagnostic system to obtain the medical history of the pet. In such an embodiment, the request may include the microchip information of the pet (e.g., microchip information 234). In response to receiving the request, the diagnostic system (e.g., diagnostic system 142) may send a request to one or more external services, such as a veterinarian (e.g., external service 162), to obtain the medical history of the pet. The request may include the microchip information of the pet. In response to receiving the request, the external service may search the veterinary records to find any veterinary records of the pet corresponding to the microchip information. The external service may then send the matching veterinary records to the diagnostic system. Upon receiving the matching veterinary records, the diagnostic system may then send the matching veterinary records to the platform, which may then store the matching veterinary records in the pet profile (eg, as the veterinary history record 232 of the pet profile 204).

[0106] although Figure 5 Example blocks of the exemplary method 500 are shown, but in some embodiments, the exemplary method 500 may include Figure 5 Additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the exemplary method 500. Additionally or alternatively, two or more blocks of the exemplary method 500 may be performed in parallel. Example Environment

[0107] Figure 6 An exemplary environment 600 is depicted that can be used with the techniques described herein. One or more user devices 602, one or more external systems 626, and one or more server systems 628 can communicate via a network 642. As will be discussed in further detail below, one or more server systems 628 can communicate with one or more other components of environment 600 via network 642. One or more user devices 602 can be associated with a user (e.g., a user associated with at least one pet).

[0108] In some embodiments, the components of environment 600 are associated with a common entity, such as a veterinarian, a clinic, an animal specialist, a research center, etc. In some embodiments, one or more components of the environment are associated with another different entity. The systems and devices of environment 600 can communicate in any arrangement. As will be discussed herein, the systems and / or devices of environment 600 can communicate to receive, send, and / or store data.

[0109] The user device 602 may be configured to enable a user to access and / or interact with other systems in the environment 600. For example, the user device 602 may be a computer system, such as a desktop computer, a mobile device, a tablet computer, etc. In some embodiments, the user device 602 may include one or more electronic applications, such as programs, plug-ins, browser extensions, etc., installed on a memory of the user device 602.

[0110] The user device 602 may include a display / user interface (UI) 604, a processor 606, a memory 610, and / or a network interface 608. The user device 602 may execute an operating system (O / S) and at least one electronic application (each stored in the memory 610) through the processor 606. The electronic application may be a desktop program, a browser program, a web client or a mobile application (which may also be a browser program in a mobile O / S), an applicant-specific program, a system control software, a system monitoring software, a software development tool, and the like. For example, the environment 600 may extend the information on the web client that may be accessed through a web browser. In some embodiments, the electronic application may be associated with one or more other components in the environment 600. The application may manage the memory 610 (e.g., a database) to transmit streaming data to the network 642. The display / UI 604 may be a touch screen or a display with other input systems (e.g., a mouse, a keyboard, etc.) so that the user may interact with the application and / or the O / S. The network interface 608 may be a TCP / IP network interface for, for example, Ethernet or wireless communication with the network 642. The processor 606 , while executing the application, may generate data and / or receive user input from the display / UI 604 and / or receive / transmit messages from / to the server system 628 , and may further perform one or more operations before providing output to the network 642 .

[0111] The external system 612 may be, for example, one or more systems that collect, manage, and / or store data corresponding to one or more pets and / or one or more pet owners. The one or more external systems may include at least one of a health system 614, a diagnostic system 616, a third-party service system 618, a genetics system 620, an adoption system 622, and / or a content management system 624. The external system 612 may communicate with other devices or systems in the environment 600 via one or more networks 642. For example, the external system 612 may communicate with the server system 628 via an API (application programming interface) access on one or more networks 642, or may communicate with the user device 602 via a web browser access on one or more networks 642.

[0112] The external service 626 may be, for example, one or more third-party and / or auxiliary systems that integrate and / or communicate with the server system 628 when performing various document information extraction tasks. The external service 626 may communicate with other devices or systems in the environment 600 via one or more networks 642. For example, the external service 626 may communicate with the server system 628 via API access on one or more networks 642, or may communicate with the user device 602 via web browser access on one or more networks 642.

[0113] In various embodiments, the network 642 may be a wide area network (WAN), a local area network (LAN), a personal area network (PAN), etc. In some embodiments, the network 642 may include the Internet, and the information and data between the systems are provided online. "Online" may mean connecting or accessing source data or information from a location of other devices or networks remotely coupled to the Internet. Alternatively, "online" may refer to connecting or accessing a network via a mobile communication network or device (wired or wireless). The Internet is a global computer network system-in which a party of a computer or other device connected to the network can obtain information from any other computer and communicate with parties of other computers or devices. The most widely used part of the Internet is the World Wide Web (usually abbreviated as "WWW" or referred to as "Web"). "Website pages" generally cover locations, data storage, etc., for example, hosted and / or operated by a computer system so as to be accessible online, and it may include data configured to enable a program (e.g., a web browser) to perform operations such as sending, receiving, or processing data, generating visual displays and / or interactive interfaces.

[0114] The server system 628 may include an electronic data system, for example, a computer-readable memory such as a hard drive, a flash drive, a disk, etc. In some embodiments, the server system 628 includes and / or interacts with an application programming interface for exchanging data with other systems (e.g., one or more of the other components of the environment).

[0115] The server system 628 may include a database 640 and a server 630. The server system 628 may be a computer, a computer system (e.g., a rack server), and / or a cloud service computer system. The server system may store or access a database 640 (e.g., hosted on a third-party server or in a memory 638). The server may include a display / UI 632, a processor 634, a memory 636, and / or a network interface 638. The display / UI 632 may be a touch screen or a display with other input systems (e.g., a mouse, a keyboard, etc.) so that an operator of the server 630 can control the functions of the server 630. The server system 628 may execute at least one instance of an operating system (O / S) and a servlet program (each stored in a memory 636) through a processor 634.

[0116] Despite Figure 6 600 as separate components, it should be understood that in some embodiments, a component or portion of a component in environment 600 may be integrated with or incorporated into one or more other components. For example, a portion of display 632 may be integrated into user device 602, etc. In some embodiments, operations or aspects of one or more components discussed above may be distributed among one or more other components. Any suitable arrangement and / or integration of the various systems and devices of environment 600 may be used.

[0117] Generally, any process or operation discussed in this disclosure is understood to be computer-implemented (e.g. Figure 3-4 The processes shown in ) can all be performed by a computer system (e.g. Figure 6 The process or process steps performed by one or more processors of any system or device in the environment 600 of the present invention may also be referred to as operations. The one or more processors may be configured to perform such processes by accessing instructions (e.g., software or computer readable code) that, when executed by the one or more processors, cause the one or more processors to perform the process. The instructions may be stored in a memory of a computer system. The processor may be a central processing unit (CPU), a graphics processing unit (GPU), or any suitable type of processing unit.

[0118] A computer system (eg, a system or device implementing the processes or operations in the above examples) may include one or more computing devices, such as, Figure 6 The computer system may include one or more systems or devices in the computer system. The one or more processors of the computer system may be included in a single computing device or distributed in multiple computing devices. The memory of the computer system may include a corresponding memory of each computing device in the multiple computing devices. Exemplary Devices

[0119] Figure 7 According to an exemplary embodiment of the present disclosure, it can be configured to perform Figure 1-5 A simplified functional block diagram of a computer 700 of an apparatus for implementing an environment and / or method of the present invention is shown. For example, the apparatus 700 may include a central processing unit (CPU) 720. The CPU 720 may be any type of processor device, including, for example, any type of dedicated or general purpose microprocessor device. As will be appreciated by those skilled in the relevant art, the CPU 720 may also be a single processor in a multi-core / multi-processor system that operates alone or in a cluster of computing devices that operate in a cluster or server farm. The CPU 720 may be connected to a data communications infrastructure 710, such as a bus, a message queue, a network, or a multi-core messaging scheme.

[0120] The device 700 may also include a main memory 740, such as a random access memory (RAM), and may also include a secondary memory 730. The secondary memory 730 (e.g., a read-only memory (ROM)) may be, for example, a hard disk drive or a removable storage drive. Such a removable storage drive may include, for example, a floppy disk drive, a tape drive, an optical disk drive, a flash memory, etc. The removable storage drive in this example reads from and / or writes to a removable storage unit in a well-known manner. The removable storage unit may include a floppy disk, a tape, an optical disk, etc., which is read and written by the removable storage drive. As will be understood by those skilled in the relevant art, such a removable storage unit typically includes a computer-usable storage medium having computer software and / or data stored therein.

[0121] In alternative embodiments, secondary storage 730 may include other similar means to allow computer programs or other instructions to be loaded into device 700. Examples of such means may include program cartridge memories and cartridge interfaces (such as those found in electronic gaming devices), removable memory chips (such as EPROM or PROM) and associated slots, and other removable storage units and interfaces that allow software and data to be transferred from a removable storage unit to device 700.

[0122] The device 700 may also include a communication interface ("COM") 760. The communication interface 760 allows software and data to be transferred between the device 700 and external devices. The communication interface 760 may include a modem, a network interface (e.g., an Ethernet card), a communication port, a PCMCIA slot and card, etc. The software and data transferred via the communication interface 760 may be in the form of signals, which may be electrical, electromagnetic, optical, or other signals capable of being received by the communication interface 760. These signals may be provided to the communication interface 760 via a communication path of the device 700, which may be implemented using, for example, wire or cable, optical fiber, a telephone line, a cellular phone link, an RF link, or other communication channel.

[0123] The hardware components, operating systems, and programming languages ​​of such devices are conventional in nature, and it is assumed that those skilled in the art are sufficiently familiar with them. The device 700 may also include an input / output port 750 to connect input / output devices such as a keyboard, a mouse, a touch screen, a monitor, a display, etc. Of course, various server functions can be implemented in a distributed manner on many similar platforms to disperse the processing load. Alternatively, the server can be implemented by appropriately programming a computer hardware platform.

[0124] The program aspects of the technology may be considered a "product" or "article of manufacture", typically in the form of executable code and / or associated data, carried on or embodied in some machine-readable medium. "Storage" type media include any or all tangible memory of a computer, processor, etc., or its associated modules, such as various semiconductor memories, tape drives, disk drives, etc., which can provide non-transitory storage for software programming at any time. All or part of the software may sometimes be communicated over the Internet or various other telecommunications networks. Such communications may, for example, enable software to be loaded from one computer or processor to another, such as from a management server or host computer of a mobile communication network to a server's computer platform and / or from a server to a mobile device. Thus, another type of medium that can carry software elements includes optical waves, radio waves, and electromagnetic waves, such as those used on physical interfaces between local devices, through wired and optical landline networks, and on various air links. Physical elements that carry such waves (e.g., wired or wireless links, optical links, etc.) may also be considered as media that carry software. As used herein, unless restricted to non-transitory, tangible "storage" media, terms such as computer or machine "readable media" refer to any medium that participates in providing instructions to a processor for execution.

[0125] A computer system (e.g., a system or device that implements the processes or operations in the above examples) may include one or more computing devices. One or more processors of the computer system may be included in a single computing device or distributed in multiple computing devices. The memory of the computer system may include a corresponding memory of each computing device in the multiple computing devices.

[0126] The computer may be configured as a device for executing the exemplary embodiments of the present disclosure. For example, the computer may be configured according to the exemplary embodiments of the present disclosure. In various embodiments, any system herein may be a computer, including, for example, a data communication interface for packet data communication. The computer may also include a central processing unit (CPU) in the form of one or more processors for executing program instructions. The computer may include an internal communication bus, and a storage unit (e.g., ROM, HDD, SDD, etc.) that can store data on a computer-readable medium, although the computer may receive programming and data via network communication. The computer may also have a memory (e.g., RAM) storing instructions for executing the techniques described herein, although these instructions may be temporarily or permanently stored in other modules of the computer (e.g., processor and / or computer-readable medium). The computer may also include an input / output port and / or a display to connect input / output devices, such as a keyboard, a mouse, a touch screen, a monitor, a display, etc. Various system functions may be implemented in a distributed manner on many similar platforms to disperse the processing load. Alternatively, the system may be implemented by appropriately programming a computer hardware platform.

[0127] In addition, although some embodiments described herein include certain features and do not include other features in other embodiments, it will be understood by those skilled in the art that combinations of features from different embodiments are intended to be within the scope of the present invention and to form different embodiments.

[0128] Therefore, although certain embodiments have been described, those skilled in the art will recognize that other and further modifications may be made thereto without departing from the spirit of the present invention, and it is intended that all such changes and modifications fall within the scope of the present invention. For example, functions may be added or deleted from the block diagram, and functional blocks may be interchangeably operated.

[0129] The subject matter disclosed above should be considered illustrative, not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments that fall within the true spirit and scope of the present disclosure. Therefore, to the maximum extent permitted by law, the scope of the present disclosure should be determined by the broadest permissible interpretation of the following claims and their equivalents, and should not be limited or restricted by the foregoing detailed description. Although various embodiments of the present disclosure have been described, it will be clear to those of ordinary skill in the art that there may be more embodiments within the scope of the present disclosure. Therefore, the present disclosure is not limited except in accordance with the appended claims and their equivalents.

Claims

1. A computer-implemented method for dynamically managing electronic transactions of pet adoption data, the method comprising: receiving, by one or more processors, a pet selection from a user device, the pet selection indicating that the user wants to adopt a pet; In response to the user completing the adoption of the pet, the one or more processors sending confirmation information indicating that the pet has been adopted, the confirmation information including at least one user record and at least one pet record; determining, by the one or more processors, whether at least one pet owner profile corresponding to the at least one user record exists in a data store; in response to determining that the at least one pet owner profile does not exist in the data store, creating, by the one or more processors, a new pet owner profile based on the at least one user record; determining, by the one or more processors, whether at least one pet profile corresponding to the at least one pet record exists in the data store; in response to determining that the at least one pet profile does not exist in the data store, creating, by the one or more processors, a new pet profile based on the at least one pet record; and The new pet profile is associated, by the one or more processors, with the new pet owner profile.

2. The computer-implemented method of claim 1 , further comprising: In response to receiving the pet selection, one or more prompts are displayed by the one or more processors on one or more user interfaces of the user device.

3. The computer-implemented method of claim 1 , wherein: The confirmation information also includes a pet owner identifier of a pre-existing pet owner profile.

4. The computer-implemented method of claim 1 , further comprising: The data in at least one of the new pet owner profile or the new pet profile is utilized by the one or more processors to interact with one or more external systems.

5. The computer-implemented method of claim 4, wherein: The one or more external systems include at least one of a health system, a diagnostic system, an adoption system, a content management system, a genetics system, or a third-party service system.

6. The computer-implemented method of claim 5, further comprising: sending, by the one or more processors, a request to the diagnostic system to obtain a medical history of the pet; receiving, by the one or more processors, at least one veterinary record matching the request; and The one or more processors store the matching at least one veterinary record in the new pet profile.

7. The computer-implemented method of claim 1 , wherein: The creating a new pet owner profile includes creating the new pet owner profile using at least a portion of the information included in the at least one user record.

8. A computer system for dynamically managing electronic transactions of pet adoption data, the computer system comprising: at least one memory storing instructions; and at least one processor configured to execute the instructions to perform operations comprising: receiving a pet selection from a user device, the pet selection indicating that the user wants to adopt a pet; In response to the user completing the adoption of the pet, sending confirmation information indicating that the pet has been adopted, the confirmation information including at least one user record and at least one pet record; determining whether at least one pet owner profile corresponding to the at least one user record exists in a data store; in response to determining that the at least one pet owner profile does not exist in the data store, creating a new pet owner profile based on the at least one user record; determining whether at least one pet profile corresponding to the at least one pet record exists in the data store; in response to determining that the at least one pet profile does not exist in the data store, creating a new pet profile based on the at least one pet record; and The new pet profile is associated with the new pet owner profile.

9. The computer system of claim 8, wherein the operations further comprise: In response to receiving the pet selection, one or more prompts are displayed on one or more user interfaces of the user device.

10. The computer system according to claim 8, wherein: The confirmation information also includes a pet owner identifier of a pre-existing pet owner profile.

11. The computer system of claim 8, wherein the operations further comprise: The data in at least one of the new pet owner profile or the new pet profile is utilized to interact with one or more external systems.

12. The computer system according to claim 11, wherein: The one or more external systems include at least one of a health system, a diagnostic system, an adoption system, a content management system, a genetics system, or a third-party service system.

13. The computer system of claim 12, wherein the operations further comprise: sending a request to the diagnostic system to obtain the pet's medical history; receiving at least one veterinary record matching the request; and The matching at least one veterinary record is stored in the new pet profile.

14. The computer system according to claim 8, wherein: The creating a new pet owner profile includes creating the new pet owner profile using at least a portion of the information included in the at least one user record.

15. A non-transitory computer-readable medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform operations for dynamically managing electronic transactions of pet adoption data, the operations comprising: receiving a pet selection from a user device, the pet selection indicating that the user wants to adopt a pet; In response to the user completing the adoption of the pet, sending confirmation information indicating that the pet has been adopted, the confirmation information including at least one user record and at least one pet record; determining whether at least one pet owner profile corresponding to the at least one user record exists in a data store; in response to determining that the at least one pet owner profile does not exist in the data store, creating a new pet owner profile based on the at least one user record; determining whether at least one pet profile corresponding to the at least one pet record exists in the data store; in response to determining that the at least one pet profile does not exist in the data store, creating a new pet profile based on the at least one pet record; and The new pet profile is associated with the new pet owner profile.

16. The non-transitory computer readable medium of claim 15, the operations further comprising: In response to receiving the pet selection, one or more prompts are displayed on one or more user interfaces of the user device.

17. The non-transitory computer readable medium of claim 15, wherein: The confirmation information also includes a pet owner identifier of a pre-existing pet owner profile.

18. The non-transitory computer readable medium of claim 15, the operations further comprising: The data in at least one of the new pet owner profile or the new pet profile is utilized to interact with one or more external systems.

19. The non-transitory computer-readable medium of claim 18, wherein the one or more external systems include at least one of a health system, a diagnostic system, an adoption system, a content management system, a genetics system, or a third-party service system.

20. The non-transitory computer readable medium of claim 19, the operations further comprising: sending a request to the diagnostic system to obtain the pet's medical history; receiving at least one veterinary record matching the request; and The matching at least one veterinary record is stored in the new pet profile.

Images