Techniques for auto-populating form input fields of an application

{
  "publication_number": "US2019213242A1",
  "country": "US",
  "kind": "A1",
  "title": "Techniques for auto-populating form input fields of an application",
  "abstract": "Described are examples for populating input fields on an application. A form input field of a form rendered by an application can be detected by the application, or another application. A data class associated with the form input field can be determined, and an anticipatory response for populating the form input field can be determined based on the data class and input from one or more different applications. The form input field of the form can be populated, via the application, with the anticipatory response.",
  "claims": [
    "1. A computer implemented method for populating input fields on an application, comprising: storing, via the application, auto-fill data for form input fields including multiple data input used in populating one or more form input fields; detecting, via the application, a form input field of a form rendered by the application; determining that the stored auto-fill data does not include a data input for a form input field type of the form input field; determining a data class associated with the form input field; generating, based on the data class and based on determining that the stored auto-fill data does not include the data input, an anticipatory response, that includes input previously obtained by one or more different applications other than the application, for populating the form input field; and populating, via the application, the form input field of the form with the anticipatory response. 2. (canceled) 3. The computer implemented method of claim 1, wherein the one or more different applications include a productivity application. 4. The computer implemented method of claim 1, wherein the one or more different applications include a webpage rendered on a web browser application. 5. The computer implemented method of claim 1, further comprising storing the input from the one or more different applications in a repository and as associated with the data class, wherein generating the anticipatory response is based at least in part on obtaining the input from the repository based on the data class. 6. The computer implemented method of claim 5, further comprising removing the input from the repository based on one or more detected events. 7. The computer implemented method of claim 6, wherein the one or more detected events correspond to at least one of exiting the application or a detected occurrence of a date and/or time. 8. The computer implemented method of claim 6, wherein the one or more detected events are defined based at least in part on the data class. 9. The computer implemented method of claim 5, wherein storing the input from the one or more different applications comprises mining accessible webpages for possible input data for the data class. 10. A device for populating input fields on an application, comprising: a memory storing one or more parameters or instructions for generating anticipatory responses for form input fields; and at least one processor coupled to the memory, wherein the at least one processor is configured to: store, via the application, auto-fill data for form input fields including multiple data input used in populating one or more form input fields; detect, via the application, a form input field of a form rendered by the application; determine that the stored auto-fill data does not include a data input for a form input field type of the form input field; determine a data class associated with the form input field; generate, based on the data class and based on determining that the stored auto-fill data does not include the data input, an anticipatory response, that includes input previously obtained by one or more different applications other than the application, for populating the form input field; and populate, via the application, the form input field of the form with the anticipatory response. 11. (canceled) 12. The device of claim 10, wherein the one or more different applications include a productivity application. 13. The device of claim 10, wherein the one or more different applications include a webpage rendered on a web browser application. 14. The device of claim 10, wherein the at least one processor is further configured to store the input from the one or more different applications in a repository and as associated with the data class, wherein the at least one processor is configured to generate the anticipatory response based at least in part on obtaining the input from the repository based on the data class. 15. The device of claim 14, wherein the at least one processor is further configured to remove the input from the repository based on one or more detected events. 16. The device of claim 15, wherein the one or more detected events correspond to at least one of exiting the application or a detected occurrence of a date and/or time. 17. The device of claim 15, wherein the one or more detected events are defined based at least in part on the data class. 18. The device of claim 14, wherein the at least one processor is configured to store the input from the one or more different applications at least in part by mining accessible webpages for possible input data for the data class. 19. A non-transitory computer-readable medium, comprising code executable by one or more processors for populating input fields on an application, the code comprising code for: storing, via the application, auto-fill data for form input fields including multiple data input used in populating one or more form input fields; detecting, via the application, a form input field of a form rendered by the application; determining that the stored auto-fill data does not include a data input for a form input field type of the form input field; determining a data class associated with the form input field; generating, based on the data class and based on determining that the stored auto-fill data does not include the data input, an anticipatory response, that includes input previously obtained by one or more different applications other than the application, for populating the form input field; and populating, via the application, the form input field of the form with the anticipatory response. 20. (canceled) 21. The non-transitory computer-readable medium of claim 19, wherein the one or more different applications include a productivity application. 22. The non-transitory computer-readable medium of claim 19, wherein the one or more different applications include a webpage rendered on a web browser application. 23. The non-transitory computer-readable medium of claim 19, further comprising code for storing the input from the one or more different applications in a repository and as associated with the data class, wherein the code for generating the anticipatory response is based at least in part on obtaining the input from the repository based on the data class."
  ],
  "description_excerpt": "Web browsers typically include auto-fill functionality where data initially entered for form input fields on forms rendered in the web browser are stored and subsequently used to auto-fill data for form input fields on other forms generated by the web browser. The auto-fill functionality stores input for a given form input field along with a name of the field or an associated label indicated on the form. The auto-fill functionality then generates prompts on a subsequent form where a form input field on the subsequent form has a same or similar name or label as the stored form input field. In addition, some auto-fill functions also associate groups of data input on multiple form input fields (e.g., such as name, address, city, state, and zip code) so that selecting a prompt to auto-fill one form input field can result in auto-filling multiple form input fields with values for the associated groups of data.\n\nThe following presents a simplified summary of one or more implementations in order to provide a basic understanding of such implementations. This summary is not an extensive overview of all contemplated implementations, and is intended to neither identify key or critical elements of all implementations nor delineate the scope of any or all implementations. Its sole purpose is to present some concepts of one or more implementations in a simplified form as a prelude to the more detailed description that is presented later.\n\nIn an example, a method for populating input fields on an application is provided.",
  "cpc": [
    "G06F 40/174",
    "G06F 17/243",
    "G06F 17/276",
    "G06F 3/0482",
    "G06F 40/274"
  ],
  "ipc": [
    "G06F 17/24",
    "G06F 17/27"
  ],
  "assignees": [
    "Microsoft Technology Licensing LLC"
  ],
  "inventors": [
    "Rajeev Ranjan Pathak",
    "Arif Alam Siddique",
    "Akshay Jayant Prabhu",
    "Gowthami Chegu",
    "Umesh Bhardwaj",
    "Mohit",
    "Vivek Kumar",
    "Anoop Pandey",
    "Vasanth Raja",
    "Sonia Singh",
    "Ankit Kumar Agrawal"
  ],
  "filing_date": "2018-01-11",
  "publication_date": "2019-07-11",
  "priority_date": "2018-01-11",
  "application_number": "US-201815868498-A",
  "family_id": "67140799",
  "cited_by_count": 23,
  "citations": [
    "US20020057678A1",
    "US7343551B1",
    "US20080141117A1",
    "US20070240100A1",
    "US20080172598A1",
    "US20090204881A1",
    "US20140157390A1",
    "US20130246525A1",
    "US20150199541A1",
    "US20140115456A1",
    "US20140195888A1",
    "US20140372861A1",
    "US20180260085A1",
    "US20150317295A1",
    "US20150379469A1",
    "US20180181866A1"
  ]
}