Patents by Inventor Tushar Phondge

Tushar Phondge has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).

  • Publication number: 20230028416
    Abstract: Embodiments present different password-less sign-in alternatives for selection by the user for a subsequent future login to the service provider account interface, and in response to determining that data inputs from a user satisfy associated data requests, enable the selected password-less sign-in alternative for a subsequent login of the user into the service provider account interface, wherein the subsequent login of the user into service provider account interface via the enabled selected password-less sign-in alternative does not require the user to enter the password.
    Type: Application
    Filed: July 26, 2021
    Publication date: January 26, 2023
    Inventors: James P. Mason, Gregory Fincannon, Tushar Phondge, Sonal Doshi, Neha Pahwa, Sanjoli Ahuja, Gregory Murphy
  • Patent number: 11200255
    Abstract: Synchronizing data across databases comprising generating a synchronization event in response to a change in source data in a source database. The synchronization event is published as a message in a source database internal queue. The message is then published in a message broker. Sink data in a sink database is synchronized according to the message in the message broker to match the change in source data in the source database.
    Type: Grant
    Filed: August 22, 2019
    Date of Patent: December 14, 2021
    Assignee: ADP, LLC
    Inventors: Daniel Rodrigo Da Paz Pontes, Deepak Kaushal, Zhitao Xu, Muhammad Nuri, Eliezer Madeira de Campos, Lili Zhang, Kushal Gohil, Srilatha Usike, Supraja Kanapala, Jayesh Patel, Manish Patel, Tushar Phondge, Vincent Civetta, Frank Villavicencio
  • Patent number: 11157513
    Abstract: A system and method for communicating events between applications. A first application receives event information for an event. A first action is performed by the first application in response to receiving the event information. The first application generates an event message comprising an event name and a message payload. The message payload comprises at least a portion of the event information. The first application publishes the event message by sending the event message to an event message pipeline. A second application may listen for the event message in the event message pipeline, receive the event message from the event message pipeline, and use the message payload to perform a second action, wherein the second action is different from the first action.
    Type: Grant
    Filed: August 9, 2019
    Date of Patent: October 26, 2021
    Assignee: ADP, LLC
    Inventors: Zhitao Xu, Daniel Rodrigo da Paz Pontes, Kushal Gohil, Tushar Phondge, Frank Villavicencio, Supraja Kanapala, Soham Jambhekar, Lili Zhang, Suthakar Maharajan, Manish Patel, Srilatha Usike, Muhammad Nuri, Deepak Kaushal, Vincent Civetta, Thiago Nunes Kehl
  • Publication number: 20210056124
    Abstract: Synchronizing data across databases comprising generating a synchronization event in response to a change in source data in a source database. The synchronization event is published as a message in a source database internal queue. The message is then published in a message broker. Sink data in a sink database is synchronized according to the message in the message broker to match the change in source data in the source database.
    Type: Application
    Filed: August 22, 2019
    Publication date: February 25, 2021
    Inventors: Daniel Rodrigo Da Paz Pontes, Deepak Kaushal, Zhitao Xu, Muhammad Nuri, Eliezer Madeira de Campos, Lili Zhang, Kushal Gohil, Srilatha Usike, Supraja Kanapala, Jayesh Patel, Manish Patel, Tushar Phondge, Vincent Civetta, Frank Villavicencio
  • Publication number: 20210042321
    Abstract: A system and method for communicating events between applications. A first application receives event information for an event. A first action is performed by the first application in response to receiving the event information. The first application generates an event message comprising an event name and a message payload. The message payload comprises at least a portion of the event information. The first application publishes the event message by sending the event message to an event message pipeline. A second application may listen for the event message in the event message pipeline, receive the event message from the event message pipeline, and use the message payload to perform a second action, wherein the second action is different from the first action.
    Type: Application
    Filed: August 9, 2019
    Publication date: February 11, 2021
    Inventors: Zhitao Xu, Daniel Rodrigo da Paz Pontes, Kushal Gohil, Tushar Phondge, Frank Villavicencio, Supraja Kanapala, Soham Jambhekar, Lili Zhang, Suthakar Maharajan, Manish Patel, Srilatha Usike, Muhammad Nuri, Deepak Kaushal, Vincent Civetta, Thiago Nunes Kehl