Automated api code generation
US-2021279115-A1 · Sep 9, 2021 · US
US12591569B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12591569-B2 |
| Application number | US-202418758281-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 28, 2024 |
| Priority date | Mar 19, 2021 |
| Publication date | Mar 31, 2026 |
| Grant date | Mar 31, 2026 |
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.
The methods and systems for improving communication distribution. In particular, the methods and systems for improving communication distribution in environments where there is both the need for end-user specific data (e.g., customized content) and/or data storage constraints. For example, in order to address the security/privacy concerns during communication distribution, the methods and systems use a novel architecture that limits the amount of data that must be stored. Specifically, the system does not require permanent storage of communications featuring end-user specific data prior to the distribution of these communications. Accordingly, the storage requirements are greatly diminished, and privacy/security concerns are avoided.
Opening claim text (preview).
What is claimed is: 1 . A system for generating electronic communications featuring consistent data structuring and dynamically-determined data content for transmission across computer networks for end user specific data in environments with data storage constraints, the system comprising: memory configured to store: a plurality of data sources, wherein each data source of the plurality of data sources corresponds to a respective end user of a plurality of end users; a plurality of application programming interfaces (“APIs”); control circuitry configured to: receive a first selection, wherein the first selection comprises a first component for including in a set of communications, wherein the first component provides encapsulation of, and interoperability between, a first set of component elements, and wherein the first component corresponds to a first API of the plurality of APIs; receive a third selection, wherein the third selection defines a first data structure characteristic for the first component, wherein the first data structure characteristic comprises a criterion for at least one of where the first component is presented in the set of communications and how the first component appears in the set of communication, and wherein the first data structure characteristic further comprises at least one of a layout, a format, and a graphical characteristic; determine a threshold data content characteristic for the first component based on the first data structure characteristic for the first component; receive a fourth selection, wherein the fourth selection defines a first data content characteristic for the first component, wherein the first data content characteristic comprises a criterion for what data content is populated in the first component in the set of communications, wherein the first data content characteristic corresponds to the threshold data content characteristic, and wherein the threshold data content characteristic dynamically modifies presentation of data content in real-time or near real-time based on the data structure characteristic; receive a fifth selection, wherein the fifth selection requests generation of the set of communications, wherein the set of communications includes a first communication for a first end user of the plurality of end users, and a second communication for a second end user of the plurality of end users; populate, by the first API, the first component with first data content in the first communication by: determining a first data source of the plurality of data sources corresponding to the first end user; retrieving available first data content from the first data source; and filtering the available first data content based on the first data content characteristic; populate, by the first API, the first component with second data content in the second communication by: determining a second data source of the plurality of data sources corresponding to the second end user; retrieving available second data content from the second data source; and filtering the available second data content based on the first data content characteristic; input/output circuitry configured to: transmit the first communication to the first end user, wherein the first data content is generated for display, on a first device corresponding to the first end user, in the first communication at a display location based on the first data structure characteristic; and transmit the second communication to the second end user, wherein the first data content is generated for display, on a second device corresponding to the second end user, in the second communication at the display location based on the first data structure characteristic. 2 . A method of generating electronic communications featuring consistent data structuring and dynamically-determined data content for transmission across computer networks for end user specific data in environments with data storage constraints, the method comprising: receiving, by control circuitry, a first selection, wherein the first selection comprises a first component for including in a set of communications, wherein the first component provides encapsulation of, and interoperability between, a first set of component elements, and wherein the first component corresponds to a first application programming interface (“API”); receiving, by the control circuitry, a third selection, wherein the third selection defines a first data structure characteristic for the first component, wherein the first data structure characteristic comprises a criterion for at least one or where the first component is presented in the set of communications and how the first component appears in the set of communication, and wherein the first data structure characteristic further comprises at least one of a layout, a format, and a graphical characteristic; determining, by the control circuitry, a threshold data content characteristic for the first component based on the first data structure characteristic for the first component; receiving, by the control circuitry, a fourth selection, wherein the fourth selection defines a first data content characteristic for the first component, wherein the first data content characteristic comprises a criterion for what data content is populated in the first component in the set of communications, wherein the first data content characteristic corresponds to the threshold data content characteristic, and wherein the threshold data content characteristic dynamically modifies presentation of data content in real-time or near real-time based on the data structure characteristic; receiving, by the control circuitry, a fifth selection, wherein the fifth selection requests generation of the set of communications, wherein the set of communications includes a first communication for a first end user and a second communication for a second end user; populating, by the first API, the first component with first data content in the first communication by: determining a first data source corresponding to the first end user; retrieving available first data content from the first data source; and filtering the available first data content based on the first data content characteristic; populating, by the first API, the first component with second data content in the second communication by: determining a second data source of the plurality of data sources corresponding to the second end user; retrieving available second data content from the second data source; and filtering the available second data content based on the first data content characteristic; transmitting the first communication to the first end user, wherein the first data content is generated for display, on a first device corresponding to the first end user, in the first communication at a display location based on the first data structure characteristic; and transmitting the second communication to the second end user, wherein the first data content is generated for display, on a second device corresponding to the second end user, in the second communication at the display location based on the first data structure characteristic. 3 . The method of claim 2 , further comprising receiving a second selection, wherein the second selection comprises a second component for including in the set of communications, wherein the second component provides encapsulation of, and interoperability between, a second set of component elements, and wherein the second component corresponds to a second API; receiving a sixth selection, wherein the sixth selection defines a second data content characteristic for the second component, wherein the second data content characteristic comprises a criterion for what data content is populated in the second component in the set of communications; and populating, by
via adapters, e.g. between incompatible applications · CPC title
Tablespace storage structures; Management thereof · CPC title
using data annotations, e.g. user-defined metadata · CPC title
for implementing user interfaces · CPC title
Office automation; Time management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.