Eureka on the web
When you want the answer in the next five minutes.
The agent works the prompt against patents and technical literature, citing every source.
Run your analysis now →12 patent families and 16 records cover demand response dynamic pricing optimization algorithms, with filings spread across 8 organisations.
16 published records collapse into 12 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 2 of 16 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.
This dataset gathers records matching "demand response" AND "dynamic pricing" combined with optimization and algorithm terms across title, abstract and claims. It returns 16 published records that de-duplicate to 12 simple patent families. No date limit was set on the search, so the result spans whatever filing years the matching text happens to cover, not a defined period chosen for this page.
With only 12 families in scope, this is a small pool. Treat the page as a starting point for a further search, not as a map of the field, a handful of documents cannot establish who leads, where gaps sit, or how the space is structured.
Ordered by volume only, not by importance or claim strength. Counted in simple (DOCDB) patent families, so one invention filed in several countries counts once. Names come from Patsnap's standardised assignee field as recorded on each document; subsidiaries and group companies are not merged. The icon before each name is read from the name itself (words such as University, Institute or Ltd); the data carries no organisation-type field, so treat it as a reading aid rather than a classification. Filings held by named individuals rather than organisations are removed where they can be identified (32 here); that identification is not exhaustive, so an individually held filing can still appear below. Either way those filings stay inside the totals above. This table shows the top 8 of the 8 filers returned for this search; the data endpoint returns at most 100 entities, so even that 8 is not the complete set of filers. A single family can name more than one filer, so these counts overlap and do not add up to the total.
Pick a task. Every answer cites the patents behind it.
The chart below counts published records by earliest filing year; the technology split counts simple patent families against IPC subclass.
Records run from 2012 (3) up to a peak of 8 in 2025. The chart's 2022-onward years are still filling in as later filings publish, so no decline should be read into the most recent bars; this is a count of documents, not inventions, since one invention can publish more than once.
Counted in published records by earliest filing year, not de-duplicated into families. A filing is counted in the year it was filed, but it only becomes visible after it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. 2022 onwards are therefore still filling in and are shaded; no growth figure on this page uses them. Because this series counts documents rather than inventions, a rise can mean more inventions or the same inventions filed in more countries; this dataset cannot separate the two.
G06Q (business/admin data processing) and H02J (power supply & grid systems) each appear on 10 of the 12 families (83.3%), followed by H04L (digital information transmission) at 6 families (50.0%) and G06N (AI-based computing) at 5 (41.7%). B60L (electric vehicle propulsion) appears on 3 families (25.0%), and G05B (control & regulating systems) and G16Y (IoT data processing) each appear on 2 (16.7%). Shares add to more than 100% because a family can carry several IPC classes.
Shares are the percentage of the 12 patent families in scope. One patent family can carry several IPC classes, so the shares add up to more than 100%.
This page is one run against one query. Ask Eureka your own question about demand response dynamic pricing response optimization algorithm patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaThe present invention relates to system and method for providing near real-time DR events and price signals to the customer end-points to optimally manage the available DR resources. The system utilizes bottom up load forecasting for accurate individualized forecasts for customer loads in the presence of dynamic pricing signals. For better efficiency and reliability of grid operation the system utilizes advanced machine learning and robust optimization techniques for real-time and personalized DR-offer dispatch.This is the record returned first under the database's default ordering, not the most cited, newest or broadest filing in the set. Its abstract describes bottom-up load forecasting and machine-learning-based optimization for DR-offer dispatch; what its granted claims actually require has to be read from the claim set itself, not inferred from this summary.


Selected as the first record the search returns under the database default order, then shown in full. It is not ranked by citations, claim breadth or commercial importance, and it is not a judgement about which filing in this space matters most.
When you want the answer in the next five minutes.
The agent works the prompt against patents and technical literature, citing every source.
Run your analysis now →When it has to run inside your own pipeline.
Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.
Browse MCP servers →Three figures from the dataset, reported without ranking or inference.
The search returned 16 published records that de-duplicate to 12 simple patent families, with no date limit applied to the string. This is a small dataset; any pattern described below is a count within these 12 families, not a statement about the wider field.
Eight organisations are each named on 1 of the 12 simple patent families, including Saveetha Engineering College and AutoGrid Systems Inc. All 8 listed filers hold 2 or fewer families each; because one family can name more than one filer, these rows cannot be added together into a combined share.
G06Q (business/admin data processing) and H02J (power supply & grid systems) each appear on 10 of the 12 families. Since the two shares are identical in size, at most 10 families can carry both; the data does not show whether the same 10 families carry both classes.
Counted by where applications were filed rather than where filers are based, India accounts for 12 of the 16 published records, with 2 in the United States, 1 at the EPO and 1 via WIPO (PCT). These figures describe filing offices only and carry no information about any filer's nationality or location.
Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to demand response dynamic pricing response optimization algorithm patent landscape, with the prior art for and against each one.
This page is a starting point built from one search string. Eureka can help extend or test it.
A dataset this small is sensitive to the exact phrasing used. Broadening or varying the search string in Eureka may surface filings this specific string did not catch.
Open EurekaFamily counts and abstracts cannot establish claim scope. Pull the granted claim sets for any record of interest before drawing conclusions about what it covers.
Explore full recordsWith 2022 onward still filling in, later filings in this area will continue to publish. Set up monitoring to catch them as they appear.
Set up tracking in EurekaThis search returns 16 published records that de-duplicate to 12 simple patent families, with no date limit applied to the underlying search string. That is a small dataset, so it should be read as a starting point rather than a complete census of the field. A different phrasing of the search string could return a different count, since the result depends on the exact terms matched in title, abstract and claims.
No single filer holds the most. Eight organisations, including Saveetha Engineering College and AutoGrid Systems Inc, are each named on 1 of the 12 simple patent families, so the list is tied at the top rather than led by one entity. All 8 listed filers hold 2 or fewer families each, which is the honest description of how spread out this particular result set is. Filer rows are not rolled up to corporate group and cannot be added together, since one family can name more than one filer.
The trend counts published records by earliest filing year, running from 3 records in 2012 up to a peak of 8 in 2025. Years from 2022 onward are still filling in as later filings publish, which is a normal publication lag and not a slowdown. Because the series counts published records rather than de-duplicated inventions, a rise can also reflect the same invention being filed in more offices rather than more distinct inventions appearing.
Counted by receiving office across the 16 published records, India accounts for 12, the United States for 2, the European Patent Office for 1 and WIPO's PCT route for 1. This tells you where the applications were filed, not where any filer is headquartered or based; the dataset does not include filer nationality or location information. Receiving-office counts sum to the full record total because one invention can be filed in more than one office.
Measured against the 12 simple patent families, G06Q (business and administrative data processing) and H02J (power supply and grid systems) each appear on 10 families (83.3%), H04L (digital information transmission) on 6 (50.0%) and G06N (AI-based computing) on 5 (41.7%). B60L (electric vehicle propulsion) appears on 3 families and G05B (control and regulating systems) and G16Y (IoT data processing) each appear on 2. These shares add up to more than 100% because a single family can be classified under several IPC subclasses at once.
No. This page reports family counts, filer names and abstracts, none of which establish what a granted claim actually requires. Claim scope has to be read from the granted claim set and prosecution history of the specific patent in question, not inferred from an abstract summary or a count of related filings. Anyone evaluating freedom to operate against a specific design needs to pull and read the actual claims, ideally with counsel.
Go past this page: query the whole demand response dynamic pricing response optimization algorithm patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.
Search. Every figure on this page comes from one Patsnap search, run once and not edited afterwards. This is the exact search string:
TAC:(("demand response" AND "dynamic pricing") AND (optimization OR optimize) AND algorithm*)
Reading the field codes: TAC searches the title, abstract and claims of each record, not the full description. The search string sets no date limit, so the scope is every matching record in the database regardless of when it was filed. It is not restricted to recent years. How this string was built matters for how far the counts can be pushed. It was generated in batch from a topic list rather than hand-crafted for this page, and the result set is not manually screened. A keyword search over title, abstract and claims both over-captures (unrelated filings that happen to use the same words) and under-captures (the same invention written in different words). This page cannot measure either effect, so read every figure here as what this particular string returned, not as what exists in the field. One subclass (G06Q) carries 83.3% of the patent families, so this search returned a classification-tight set.
What is being counted. Two different units appear on this page and they are not interchangeable. The filer list and the technology split are counted in simple (DOCDB) patent families: one invention counts once however many countries it was filed in. The total, the jurisdiction split and the filing-year chart are counted in published records: the same invention counts once per publication. For this search that is 16 records and 12 families. Record counts reward filing in many jurisdictions; family counts do not. Shares are only ever taken against a denominator in the same unit, and each one names it.
Who the filers are. Names come from Patsnap's standardised assignee field, as recorded on the documents themselves. They are not rolled up to corporate group: a parent and its subsidiaries appear as separate entries, and a portfolio acquired from another company stays under the name on the document unless the assignment is reflected there. This list is meant to carry organisations, not people. Filings held by a named individual are identified by matching the assignee against the inventors on the same search, and, for names written in Chinese, Japanese or Korean characters, by the name carrying no organisational suffix; those are removed from the list (32 of them here). Neither test is exhaustive: the inventor list it matches against is itself capped, and a personal name written in Latin script with no organisational wording in it cannot be told apart from a short company name by rule. So an individually held filing can still appear in the list. Those filings stay inside every total and share on this page either way, so the listed entries can add up to less than the total. A record shown in full further down still names its assignee exactly as the patent office records it, including where that is a person: that name is how the record is identified and checked. What is left out of the ranking is people as ranked entries, not people as cited sources. The table shows the top 8 of the 8 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 8 is not every filer. One patent family can name several filers and each is counted separately, so these rows are not slices of a divided whole: adding them together over-counts, and this page deliberately publishes no combined "top five" share for that reason. See every filer, individuals included
Dates. The year chart counts by earliest filing year, not publication year. A filing only becomes visible once it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. Measured across these pages, the year four back from today still holds only about 89% of its eventual count. 2022 onwards are therefore shaded on the chart as still filling in. The data behind this page was retrieved on 2026-10-20.
Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (2 of 16). Everything else is pending, withdrawn, refused, lapsed or not determinable, and those states are not broken out here because the underlying codes do not separate them cleanly. Legal status changes continuously and is reported per document, not per family. Get the status breakdown in Eureka
Classification. The technology split uses IPC subclasses (four characters, for example H01M). A single record usually carries several, so the shares add up to more than 100% and a record can appear in more than one bar. Subclass is a coarse grouping; it describes the field a record was classified into, not what the claims cover. Break the classes down to subgroup level
Who wrote the words. The tables, charts, counts, shares and patent numbers on this page are produced directly from the search result by a program; none of them are written or estimated by a language model. The surrounding prose, headings, FAQ answers and the answers in the question panel are drafted by a language model that is given those same figures and is not permitted to introduce others. Prose can still mis-describe a correct figure, so where the two disagree, the tables and charts are the record.
Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.
Patent data carries limitations that apply to every figure above. Recent filings are under-counted, because an application is not public until roughly 18 months after filing and database loading adds further delay. The search string defines and constrains everything shown: records that use different terminology, or that sit outside the fields searched, are absent and cannot be counted. Applicant names, classification codes, legal-status codes and citation records are taken as recorded and may contain errors, duplicates, omissions or stale entries. Ordering by volume is not a measure of quality, scope, enforceability or commercial value, and a larger portfolio is not a stronger one. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.
Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, validity or infringement search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. No attorney-client relationship is created by it. Any patent, commercial, or strategic decision should be verified independently against the primary records and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.
The question panel. The answers behind the suggested questions on this page were written when the page was generated, not in response to your click. The progress steps that play before an answer appears are an animation of how that analysis was done; nothing is being searched or computed at that moment. Typing your own question instead opens Patsnap Eureka, which does run it live.
Help us improve
Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.
This page