System and method for providing a digital meeting tool
US-2016142873-A1 · May 19, 2016 · US
US9602949B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9602949-B2 |
| Application number | US-201514608417-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 29, 2015 |
| Priority date | Dec 11, 2013 |
| Publication date | Mar 21, 2017 |
| Grant date | Mar 21, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system and method that allows an applicant to select a third party to provide data to populate a plurality of fields of a web-based form, a communication interface that receives a selection of the third party to provide data to populate the plurality of fields of the web-based form and an application server, that transmits a third-party application programming interface (API) call to the at least one selected third party; transmits data indicative of an authentication request associated with the selected third party; and receives a security token in response to a validated authentication request, the security token enabling communication between application server and the third party system via the third party API, wherein the enabled communications is based on a set of permissions, each permission associated with a specific data field in the web-based form.
Opening claim text (preview).
We claim: 1. A system comprising: a database that stores a web-based form that includes a link to allow an applicant to select a third party to provide data to populate a plurality of fields of the web-based form; a communication interface that transmits the web-based form to a mobile device of a user and receive a selection of the third party to provide data to populate the plurality of fields of the web-based form; and an application server, that, in conjunction with the communication interface, in response to the selection, transmits a third-party application programming interface (API) call to the at least one selected third party; transmits data indicative of an authentication request associated with the selected third party; and receives a security token in response to a validated authentication request, the security token enabling communication between application server and the third party system via the third party API, wherein the enabled communication is based on a set of permissions, each permission of the set of permissions associated with a specific data field in the web-based form, and wherein each permission of the set of permissions is provided to the third party API in a notification. 2. The system of claim 1 , wherein the application server, in conjunction with the communication interface, receives data for a respective data field in the web-based form, associates the received data with the respective data field in the web-based form, and transmits the associated data with the respective data field in the web-based form to the mobile device thereby causing the mobile device to auto-populate respective data field and display the auto-populated data field on a user interface of the mobile device. 3. The system of claim 2 , wherein the user interface of the mobile device prompts the user to select the third party. 4. The system of claim 1 , wherein the web-based form further comprises a data field that is to be populated manually by the applicant. 5. The system of claim 1 , wherein the user interface is part of a native application executing on the mobile device. 6. The system of claim 1 , wherein the user interface is a mobile optimized web browser interface. 7. The system of claim 1 , wherein the third party comprises a third party system associated with the third party API. 8. The system of claim 7 , wherein the third party system comprises a privacy module that transmits the security token via the third party API. 9. The system of claim 7 , wherein the third party system comprises a social network. 10. The system of claim 7 , wherein the application server and the third party system each include a transfer module that enables data transfer between the application server and the third party system.
Authentication · CPC title
Form filling; Merging · CPC title
providing single-sign-on or federations · CPC title
Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII] · CPC title
by mutual authentication, e.g. between devices or programs · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.